You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could result in some funny behaviour if the user expect to loop back a GPIO into a peripheral, but the signal is not going through the GPIO matrix.
(For example, bitbanging SPI clock for slave loopback may not be output if the loopback pin is FSPICLK)
The text was updated successfully, but these errors were encountered:
If I remember correctly you don't need the GPIO matrix for loopback/interconnect.
It should be fine for the output to go via io_mux and input to go via matrix, so long as the GPIO pad has both input and output enabled. (Which you have to do in the right order based on the current GPIO code)
You kinda do (need the matrix), because you can't select two alternate functions for the same pin. I spent more time on this today than I'd like to admit.
This could result in some funny behaviour if the user expect to loop back a GPIO into a peripheral, but the signal is not going through the GPIO matrix.
(For example, bitbanging SPI clock for slave loopback may not be output if the loopback pin is FSPICLK)
The text was updated successfully, but these errors were encountered: