Forum Replies Created
June 2, 2022 at 07:23 in reply to: openocd settings for JTAG debugging ESP32-WROOM-32 on custom board #32724
thank you very much, debugging and halting works now. Since this was done on a throwaway project and I started an actual project (with default settings) where I don’t see this error, i consider this solved.May 30, 2022 at 02:04 in reply to: openocd settings for JTAG debugging ESP32-WROOM-32 on custom board #32708
thank you, with the above I was able to launch debug session and halting on breakpoint. It throws an error message before i can run but i am able to reach the entry point and start/run the program,
i attached a screenshot of the error message that pops up before I start running. Could you perhaps elaborate on it? Could it be an indication of things set up wrong?
If i have to guess, it looks like something expects the stack to grow down in the address range ? but detects that in this case it is not? I dont have much familiarity with the chip yet at that level of detail and I try to leave the datasheet closed as long as possible =D
have a nice day, so far I like the tool and hope I can continue with it.
Attachments:You must be logged in to view attached files.May 24, 2022 at 02:57 in reply to: openocd settings for JTAG debugging ESP32-WROOM-32 on custom board #32676
i really dont understand this process,
first, early debug session (that i did not correctly capture with the logs) succesfully uploaded the firmware image to the target, and the blink project made my gpio pin blink correctly. Doing break all gave me the following error:
Frame not in module
The current stack frame was not found in a loaded module. Source cannot be shown for this location.
I instrumented that gdb log after that and since then i cannot succesfully get the blink project to run. The upload itself seems fine but when i reset the target, it goes to an undefined area in the chip, i guess. I attached that specific log, maybe there is already indication what i do wrong?
FYI, i upload via jtag as well, for that i have to boot into the programmer mode (with the BOOT/RESET combo).
Attachments:You must be logged in to view attached files.