Hello,
I've noticed that PINE64 plan to provide in a couple of month a board based on the rock chip RK3399. Could you post the pins assignment of the 40 pins connector? I'm particularly interested by I2S0 interface signals (ideally I2S0-SDI0, I2S0-SDO0..3, and clocks), I2C and/or SPI.
Thx
(02-14-2018, 01:31 PM)philw38 Wrote: Hello,
I've noticed that PINE64 plan to provide in a couple of month a board based on the rock chip RK3399. Could you post the pins assignment of the 40 pins connector? I'm particularly interested by I2S0 interface signals (ideally I2S0-SDI0, I2S0-SDO0..3, and clocks), I2C and/or SPI.
Thx
We will release the 40 pins GPIO map on end of this month after second rev PCB released. In general, for i2s, i2c, spi, and uart, we try to follow back RPi 40pin definition position.
(02-14-2018, 05:11 PM)tllim Wrote: (02-14-2018, 01:31 PM)philw38 Wrote: Hello,
I've noticed that PINE64 plan to provide in a couple of month a board based on the rock chip RK3399. Could you post the pins assignment of the 40 pins connector? I'm particularly interested by I2S0 interface signals (ideally I2S0-SDI0, I2S0-SDO0..3, and clocks), I2C and/or SPI.
Thx
We will release the 40 pins GPIO map on end of this month after second rev PCB released. In general, for i2s, i2c, spi, and uart, we try to follow back RPi 40pin definition position.
Thank you for your answer,
However the RPi does not provide a standard pinning which includes I2S. The "standard" audio is managed as an "on board" PWM stream if I understand correctly. Some manufacturers provide audio card etensions. Wolfson (Cirrus Logic) provides a board with 1 stereo input stream and 1 output stereo stream. The HifiBerry has only 1 output stereo stream. My needs are 1 I2S input and at least 1 I2S output, but ideally I would like 4 I2S output (which is what you can get with the I2S #0 RK3399 interface).
Hope you can take into account these needs.
Thx
(02-15-2018, 02:21 AM)philw38 Wrote: (02-14-2018, 05:11 PM)tllim Wrote: (02-14-2018, 01:31 PM)philw38 Wrote: Hello,
I've noticed that PINE64 plan to provide in a couple of month a board based on the rock chip RK3399. Could you post the pins assignment of the 40 pins connector? I'm particularly interested by I2S0 interface signals (ideally I2S0-SDI0, I2S0-SDO0..3, and clocks), I2C and/or SPI.
Thx
We will release the 40 pins GPIO map on end of this month after second rev PCB released. In general, for i2s, i2c, spi, and uart, we try to follow back RPi 40pin definition position.
Thank you for your answer,
However the RPi does not provide a standard pinning which includes I2S. The "standard" audio is managed as an "on board" PWM stream if I understand correctly. Some manufacturers provide audio card etensions. Wolfson (Cirrus Logic) provides a board with 1 stereo input stream and 1 output stereo stream. The HifiBerry has only 1 output stereo stream. My needs are 1 I2S input and at least 1 I2S output, but ideally I would like 4 I2S output (which is what you can get with the I2S #0 RK3399 interface).
Hope you can take into account these needs.
Thx 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.
(02-15-2018, 07:30 PM)tllim Wrote: (02-15-2018, 02:21 AM)philw38 Wrote: (02-14-2018, 05:11 PM)tllim Wrote: (02-14-2018, 01:31 PM)philw38 Wrote: Hello,
I've noticed that PINE64 plan to provide in a couple of month a board based on the rock chip RK3399. Could you post the pins assignment of the 40 pins connector? I'm particularly interested by I2S0 interface signals (ideally I2S0-SDI0, I2S0-SDO0..3, and clocks), I2C and/or SPI.
Thx
We will release the 40 pins GPIO map on end of this month after second rev PCB released. In general, for i2s, i2c, spi, and uart, we try to follow back RPi 40pin definition position.
Thank you for your answer,
However the RPi does not provide a standard pinning which includes I2S. The "standard" audio is managed as an "on board" PWM stream if I understand correctly. Some manufacturers provide audio card etensions. Wolfson (Cirrus Logic) provides a board with 1 stereo input stream and 1 output stereo stream. The HifiBerry has only 1 output stereo stream. My needs are 1 I2S input and at least 1 I2S output, but ideally I would like 4 I2S output (which is what you can get with the I2S #0 RK3399 interface).
Hope you can take into account these needs.
Thx 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
(02-16-2018, 03:55 AM)philw38 Wrote: (02-15-2018, 07:30 PM)tllim Wrote: (02-15-2018, 02:21 AM)philw38 Wrote: (02-14-2018, 05:11 PM)tllim Wrote: (02-14-2018, 01:31 PM)philw38 Wrote: Hello,
I've noticed that PINE64 plan to provide in a couple of month a board based on the rock chip RK3399. Could you post the pins assignment of the 40 pins connector? I'm particularly interested by I2S0 interface signals (ideally I2S0-SDI0, I2S0-SDO0..3, and clocks), I2C and/or SPI.
Thx
We will release the 40 pins GPIO map on end of this month after second rev PCB released. In general, for i2s, i2c, spi, and uart, we try to follow back RPi 40pin definition position.
Thank you for your answer,
However the RPi does not provide a standard pinning which includes I2S. The "standard" audio is managed as an "on board" PWM stream if I understand correctly. Some manufacturers provide audio card etensions. Wolfson (Cirrus Logic) provides a board with 1 stereo input stream and 1 output stereo stream. The HifiBerry has only 1 output stereo stream. My needs are 1 I2S input and at least 1 I2S output, but ideally I would like 4 I2S output (which is what you can get with the I2S #0 RK3399 interface).
Hope you can take into account these needs.
Thx 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
I2S #1 pins have multiplex with other functions. There is another concern is the 1v8 vs 3v0 IO voltage tolerance.
(02-16-2018, 03:55 AM)philw38 Wrote: (02-15-2018, 07:30 PM)tllim Wrote: (02-15-2018, 02:21 AM)philw38 Wrote: (02-14-2018, 05:11 PM)tllim Wrote: (02-14-2018, 01:31 PM)philw38 Wrote: Hello,
I've noticed that PINE64 plan to provide in a couple of month a board based on the rock chip RK3399. Could you post the pins assignment of the 40 pins connector? I'm particularly interested by I2S0 interface signals (ideally I2S0-SDI0, I2S0-SDO0..3, and clocks), I2C and/or SPI.
Thx
We will release the 40 pins GPIO map on end of this month after second rev PCB released. In general, for i2s, i2c, spi, and uart, we try to follow back RPi 40pin definition position.
Thank you for your answer,
However the RPi does not provide a standard pinning which includes I2S. The "standard" audio is managed as an "on board" PWM stream if I understand correctly. Some manufacturers provide audio card etensions. Wolfson (Cirrus Logic) provides a board with 1 stereo input stream and 1 output stereo stream. The HifiBerry has only 1 output stereo stream. My needs are 1 I2S input and at least 1 I2S output, but ideally I would like 4 I2S output (which is what you can get with the I2S #0 RK3399 interface).
Hope you can take into account these needs.
Thx 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 We will expose all four I2S0 data 0-3 pins with clock pins on Rockpro64's Pi2 bus.
(02-20-2018, 09:31 PM)tllim Wrote: (02-16-2018, 03:55 AM)philw38 Wrote: (02-15-2018, 07:30 PM)tllim Wrote: (02-15-2018, 02:21 AM)philw38 Wrote: (02-14-2018, 05:11 PM)tllim Wrote: We will release the 40 pins GPIO map on end of this month after second rev PCB released. In general, for i2s, i2c, spi, and uart, we try to follow back RPi 40pin definition position.
Thank you for your answer,
However the RPi does not provide a standard pinning which includes I2S. The "standard" audio is managed as an "on board" PWM stream if I understand correctly. Some manufacturers provide audio card etensions. Wolfson (Cirrus Logic) provides a board with 1 stereo input stream and 1 output stereo stream. The HifiBerry has only 1 output stereo stream. My needs are 1 I2S input and at least 1 I2S output, but ideally I would like 4 I2S output (which is what you can get with the I2S #0 RK3399 interface).
Hope you can take into account these needs.
Thx 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 We will expose all four I2S0 data 0-3 pins with clock pins on Rockpro64's Pi2 bus.
Just to be clear. Here are the GPIOs for I2S0:
- 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
Do you mean you will expose those 8 signals? If yes that would be perfect 
Thx
(02-21-2018, 02:39 AM)philw38 Wrote: (02-20-2018, 09:31 PM)tllim Wrote: (02-16-2018, 03:55 AM)philw38 Wrote: (02-15-2018, 07:30 PM)tllim Wrote: (02-15-2018, 02:21 AM)philw38 Wrote: Thank you for your answer,
However the RPi does not provide a standard pinning which includes I2S. The "standard" audio is managed as an "on board" PWM stream if I understand correctly. Some manufacturers provide audio card etensions. Wolfson (Cirrus Logic) provides a board with 1 stereo input stream and 1 output stereo stream. The HifiBerry has only 1 output stereo stream. My needs are 1 I2S input and at least 1 I2S output, but ideally I would like 4 I2S output (which is what you can get with the I2S #0 RK3399 interface).
Hope you can take into account these needs.
Thx 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 We will expose all four I2S0 data 0-3 pins with clock pins on Rockpro64's Pi2 bus.
Just to be clear. Here are the GPIOs for I2S0:
- 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
Do you mean you will expose those 8 signals? If yes that would be perfect
Thx
Correct.
(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: (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 We will expose all four I2S0 data 0-3 pins with clock pins on Rockpro64's Pi2 bus.
Just to be clear. Here are the GPIOs for I2S0:
- 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
Do you mean you will expose those 8 signals? If yes that would be perfect
Thx
Correct.
Good news, thank you.
|
