krhodes@netboxsc.com

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: how to get exception information on esp8266 when crashes? #9431

    I understand you cannot breakpoint in flash. When a program is running, I want to run “Debug / Break All”, but it rarely works.

     

    The jtag won’t work for me because I need the SPI channel for something else.

     

    Doesn’t the exception information get dumped to the UART?

     

    Thanks…

    in reply to: odd behavior with debugging on V5.2 and esp8266 #9415

    I found my problem. The function declaration in the source file didn’t have the ICACHE_FLASH_ATTR macro, but the prototype definition in the header file did (and the header was included in the c file).

    The prototype in the header must’ve caused the compiler to put it into ROM. What is strange (and I’d submit is a bug) is that no warning was generated when the two differed. This will make it a bit of a challenge to ensure that the function prototypes match, as I will be moving functions between ROM and RAM a great deal.

    …Keith

    in reply to: odd behavior with debugging on V5.2 and esp8266 #9414

    There wasn’t anything listed that I didn’t set, but I did find that the function that I set a breakpoint in was in ROM, not RAM. I am using the ICACHE_FLASH_ATTR macro to put functions into ROM and I didn’t specify  the macro for this function.

    My compile flags are:

    -ggdb -ffunction-sections -O0  -nostdlib -mlongcalls -mtext-section-literals -nostdlib -mlongcalls -mtext-section-literals  -DDEBUG=1 -D__ets__ -DGDBSTUB_REDIRECT_CONSOLE_OUTPUT=1 -DICACHE_FLASH -DESP8266_GDBSTUB -DGDBSTUB_BREAK_ON_INIT=1 -DGDBSTUB_FREERTOS=0

    Is there another way to control the placement into RAM?

    Thanks..Keith

Viewing 3 posts - 1 through 3 (of 3 total)