I am using a Sparkfun Thing board ( https://cdn.sparkfun.com/datasheets/Wir ... _Thing.pdf ), and writing code from within MS Visual Studio + GDB, debug method via XtensaOCD or OpenOCD.
I attached a Segger J-Link ( https://www.segger.com/jlink-debug-probes.html ) to the Sparkfun Thing board, but can't detect the CPU core.
JTAG signal TMS ==> ESP8266 pin 14
JTAG signal TDI ==> ESP8266 pin 12
JTAG signal TCK ==> ESP8266 pin 13
JTAG signal TDO ==> ESP8266 pin 15 (after removing R17 pull-down on SparkFun Thing board)
JTAG signal RST ==> ESP8266 pin RST (DTR line on SparkFun Thing board)
Btw, why is GPIO15/MTDO pulled down on the SparkFun Thing board?
I would appreciate any guidance on this topic.
which is powerful tool or method for esp8266 debugging?
for esp32 there's no issue as xtesnsa addr2line tool is tracing back with great accuracy for reset cause from dump file but this isn't the case with my esp8266 WROOM2 module. sometimes i get the cause and most of the time i left unanswered while going for this tool for esp8266.
but finding rootcause of board reset is my prime requirement.
i'm not sure whether i should go for GDBSTUB or openOCD for hardware debugging. is any of this going to help me anyway?
that would be great for me and plenty of others if you share your suggestions on this.
i'm totally a newbie to this debugging thing.
Who is online
Users browsing this forum: No registered users and 1 guest
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
We also have a RTOS version and a MESH version too!
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!