02-22-2018, 03:11 AM
(02-21-2018, 11:56 PM)tllim Wrote:(02-21-2018, 02:39 AM)philw38 Wrote:(02-20-2018, 09:31 PM)tllim Wrote:(02-16-2018, 03:55 AM)philw38 Wrote:We will expose all four I2S0 data 0-3 pins with clock pins on Rockpro64's Pi2 bus.(02-15-2018, 07:30 PM)tllim Wrote: The RK3399 looks like a lot of pins but able assign for GPIO pins are not many. RK3399 don't have internal audio dac and the i2S0 has been assigned fro on board audio codec. I will take your request into account but not promise able to accommodate.
Thank you for your answer.
What's doable is to use I2S #1 interface for onboard audio codec (I2S #1 has "only" 1 IN and 1 OUT), and to allow access to the more featured I2S #0 thru the GPIO connectors. This is what Firefly is doing with their RK3399 boards.
Thx
Just to be clear. Here are the GPIOs for I2S0:
Do you mean you will expose those 8 signals? If yes that would be perfect
- Y7 : GPIO3_D3/I2S0_SDI0
- AA6 : GPIO3_D5/I2S0_SDI2SDO2
- AG3 : GPIO3_D0/I2S0_SCLK
- AH1 : GPIO3_D7/I2S0_SDO0
- AE5 : GPIO3_D4/I2S0_SDI1SDO3
- AF4 : GPIO3_D1/I2S0_LRCK_RX
- AH2 : GPIO3_D6/I2S0_SDI3SDO1
- AJ2 : GPIO3_D2/I2S0_LRCK_TX
Thx
Correct.
Good news, thank you.