PINE64

Full Version: ROCK64 STEREO AUDIO DAC ADD-ON BOARD
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Which pins does the DAC board use? It looks like it uses the 20 pin. Does this mean that it leaves the 40 pin GPIO pins free to use?
(02-06-2018, 10:01 AM)angelscream09 Wrote: [ -> ]Which pins does the DAC board use? It looks like it uses the 20 pin. Does this mean that it leaves the 40 pin GPIO pins free to use?

yes, the 40 pin GPIO pins are free to use. For more Pi2 and Pi5+ bus, DAC board schematic, you can refer to PINE64 wiki page: http://wiki.pine64.org/index.php/ROCK64_...ifications
(02-09-2018, 09:49 PM)tllim Wrote: [ -> ]
(02-06-2018, 10:01 AM)angelscream09 Wrote: [ -> ]Which pins does the DAC board use? It looks like it uses the 20 pin. Does this mean that it leaves the 40 pin GPIO pins free to use?

yes, the 40 pin GPIO pins are free to use. For more Pi2 and Pi5+ bus, DAC board schematic, you can refer to PINE64 wiki page: http://wiki.pine64.org/index.php/ROCK64_...ifications

I'm struggling to find which pins is connects to ... Could someone post a pic with the dac mounted?

Thanks in advance!
What image is better for use with the DAC? Will it work only with Volumo or other images will work too?
bin4ry, have you succeeded?
The DAC runs not synchronous to the I2s clock form the SoC/Rock64.
Which means DAC's have to drop and/or duplicate audio samples.
So do not expect quality sound, regardless which distro used.
See Thread "I2S1_MCLK".
, see jumper J3, http://files.pine64.org/doc/rock64/ROCK6..._Board.pdf

Isn't that what you want?
(11-17-2018, 09:15 AM)antonv Wrote: [ -> ], see jumper J3, http://files.pine64.org/doc/rock64/ROCK6..._Board.pdf

Isn't that what you want?

J3 1-3 => asynchronous to SoC.
J3 2-3 useless so far as no MCLK on Pin 3.
Wow, indeed, I only have sound in one position of the J3 jumper, and silence in the other position (they are not labeled, but I guess the working one is 1-3).

According to the schema, MCLK should be there...

Maybe we do something wrong? Or some workaround?