01-03-2018, 11:15 AM
Hello,
I assume this is up-to-date: ROCK64_Schematic_v2.0_20170704.pdf
Is it true that the following "dedicated signals" could be re-purposed as regular IO as they only go the 40-pin header?
CLK32KOUT_M1
UART2_TX
UART2_RX
Also, why does SPI_CSN0_M2 appear on this header? It is dedicated as a chip select on SPI flash IC U1 (the GD25Q128CS).
Any use of this pin as either SPI or GPIO will cause U1 to drive the MISO pin (pin 21 on the 40 pin header).
Also, the graphic that shows the 40-pin header (ROCK64_Pi-2 _and_Pi_P5+_Bus.pdf) states the the SDMMC0_xxxx pins can be used as GPIO as long as no MicroSD is used.
How do these pins operate during boot? If they are intended to be used as GPIO by an application, the boot process may inadvertently cause a daughterboard to react because the application hasn't booted yet.
Any guidance would be appreciated.
I assume this is up-to-date: ROCK64_Schematic_v2.0_20170704.pdf
Is it true that the following "dedicated signals" could be re-purposed as regular IO as they only go the 40-pin header?
CLK32KOUT_M1
UART2_TX
UART2_RX
Also, why does SPI_CSN0_M2 appear on this header? It is dedicated as a chip select on SPI flash IC U1 (the GD25Q128CS).
Any use of this pin as either SPI or GPIO will cause U1 to drive the MISO pin (pin 21 on the 40 pin header).
Also, the graphic that shows the 40-pin header (ROCK64_Pi-2 _and_Pi_P5+_Bus.pdf) states the the SDMMC0_xxxx pins can be used as GPIO as long as no MicroSD is used.
How do these pins operate during boot? If they are intended to be used as GPIO by an application, the boot process may inadvertently cause a daughterboard to react because the application hasn't booted yet.
Any guidance would be appreciated.