Preliminary openocd JTAG debugger support for Xtensa/esp8266

Discuss here different C compiler set ups, and compiling executables for the ESP8266
 Reply

User avatar

Re: Preliminary openocd JTAG debugger support for Xtensa/esp

By cal
- Wed May 20, 2015 5:46 am #17947 I think I have applied your patch. (I applied it to crosstool-ng in a dirty way and it seems it survived..)

Did improve a little bit:
Some bogus entry vanished from the bt but still I get an endless loop.

Code: Select all(gdb) bt
#0  gdb_breakpoint () at arch_esp8266.c:19
#1  0x402367e0 in nodemcu_init () at user_main.c:225
#2  0x402367e0 in nodemcu_init () at user_main.c:225
#3  0x402367e0 in nodemcu_init () at user_main.c:225
...

I have to understand more on that ...

Cal
User avatar

Re: Preliminary openocd JTAG debugger support for Xtensa/esp

By cal
- Wed May 20, 2015 8:25 am #17955 You didn't mislead me!

I got a small improvement, you lead me to the code thats responsible and maybe I will understand
the stack stuff ...

BTW: I found out that the function in question is (speaken in java terms) an "method" of the "object"
frame_unwind which has some documentation in its own heder file about the purpose of the "method".

I consider that "documenting the interface" which reduces the need for documenting
the purpose of explicit method implementations for me.

Can you do me a favor?
As far as I understand the OCD/JTAG/whatever stuff the gdb communitates with some JTAG speaking
gdbserver.
Do you have access to the logs of such a communication between gdb and gdb server from the startup to
some single stepping and continue?
I would like to clarify how some gdb stuff is used on a bare metal target.

Thanks in advance and I got the strong feeling there is more gdb communication to come ...

There seem to be only a few people interested in using a debugger to debug. Strange.

Cal
 Reply
Return to Compiler Chat