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
M_TDI and M_TDO are swapped between the default config and the example schematic.
The example schematic shows:
M_TDO: GPIO 3 on ESP32-S2 and GPIO 15 on target ESP32
M_TDI: GPIO 9 on ESP32-S2 and GPIO 12 on target ESP32
The default settings for sdkconfig, however, has GPIO 3 for M_TDI and GPIO 9 for M_TDO. Using those pins as in the sdkconfig results in:
Error: JTAG scan chain interrogation failed: all zeroes
Swapping them in the code (since I'd already wired up a board using the schematic) allows it to work fine.
I beat my head on the wall for quite some time and checked and re-checked wiring, etc until I decided to try swapping them (I finally realized the schematic had M_RXD connected to ESP32 TXD0 and M_TXD to ESP32 RXD0, which makes sense as you swap the TX and RX, so I swapped the TDI and TDO and it works fine.)
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Schematic has wrong pins, resulting in Error: JTAG scan chain interrogation failed: all zeroes
Schematic has wrong pins, resulting in Error: JTAG scan chain interrogation failed: all zeroes (EUB-59)
Nov 26, 2023
M_TDI and M_TDO are swapped between the default config and the example schematic.
The example schematic shows:
The default settings for sdkconfig, however, has GPIO 3 for M_TDI and GPIO 9 for M_TDO. Using those pins as in the sdkconfig results in:
Swapping them in the code (since I'd already wired up a board using the schematic) allows it to work fine.
I beat my head on the wall for quite some time and checked and re-checked wiring, etc until I decided to try swapping them (I finally realized the schematic had M_RXD connected to ESP32 TXD0 and M_TXD to ESP32 RXD0, which makes sense as you swap the TX and RX, so I swapped the TDI and TDO and it works fine.)
The text was updated successfully, but these errors were encountered: