Issue with ESP-IDF project and flash burning

Sysprogs forums Forums VisualGDB Issue with ESP-IDF project and flash burning

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #21345
    dedvalson
    Participant

    Hi,

    I have an annoyance that I wonder if there is a way around. When I try to start a new debug session, the flash burn fails every other try (exactly every other one).

    What is interesting though is that I do not have this issue when I set “Debug Using” to “ESP32 DevKit”

    I do have this issue when using my hardware. In this case I choose “OpenOCD, and interface/ftdi/tumpa.cfg”

    But what is interesting is that my hardware (when connected to the tumpa card) is identical to what is in the ESP32 DevKit. But of course the chip in the devkit has a different USB ID.

    Is there a way for me to use the method that works with the ESP32 DevKit on what should be identical hardware with the tumpa board?

    Thanks,

    Don

     

    #21347
    support
    Keymaster

    Hi,

    If the problem only occurs on your board, but not on the reference board, it is likely caused by wiring issues (e.g. cross-talk, wrong reset connection, etc.). Generally if the problem cannot be reliably reproduced on any of the boards mentioned in our tutorials, we won’t be able to offer much help as a part of our regular product support. That said, feel free to attach the error log you are getting from OpenOCD. If this is something we have seen before, we might be able to at least suggest the direction for further investigation.

    #21354
    dedvalson
    Participant

    Hi,

    I get the same error on the reference board if I use OpenOCD and interface/ftdi/devkitj_f1. But I don’t get it if I choose USB Devices and ESP32 DevKit.

    I have attached two screen shots (I can’t see how to make them display inline. One shows the configuration that works on the reference board, the other shows the configuration that fails every other time on the reference board.

    The text of the error is as follows:

    VisualGDB is licensed to Don Edvalson at CoralVue Industries
    -gdb-version
    =thread-group-added,id="i1"
    ~"GNU gdb (GDB) 7.10\n"
    ~"Copyright (C) 2015 Free Software Foundation, Inc.\n"
    ~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \"show copying\"\nand \"show warranty\" for details.\n"
    License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law. Type "show copying"
    and "show warranty" for details.
    ~"This GDB was configured as \"--host=i686-pc-mingw32 --target=xtensa-esp32-elf\".\nType \"show configuration\" for configuration details."
    This GDB was configured as "--host=i686-pc-mingw32 --target=xtensa-esp32-elf".
    Type "show configuration" for configuration details.
    ~"\nFor bug reporting instructions, please see:\n"
    ~"<http://www.gnu.org/software/gdb/bugs/>.\n"
    ~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/>.\n"
    Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.
    ~"For help, type \"help\".\n"
    ~"Type \"apropos word\" to search for commands related to \"word\"...\n"
    ~"Reading symbols from c:/Users/Don/source/CoralVue/Atlas/Debug/Atlas.elf..."
    ~"done.\n"
    ~"GNU gdb (GDB) 7.10\n"
    ~"Copyright (C) 2015 Free Software Foundation, Inc.\n"
    ~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \"show copying\"\nand \"show warranty\" for details.\n"
    License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law. Type "show copying"
    and "show warranty" for details.
    ~"This GDB was configured as \"--host=i686-pc-mingw32 --target=xtensa-esp32-elf\".\nType \"show configuration\" for configuration details."
    This GDB was configured as "--host=i686-pc-mingw32 --target=xtensa-esp32-elf".
    Type "show configuration" for configuration details.
    ~"\nFor bug reporting instructions, please see:\n"
    ~"<http://www.gnu.org/software/gdb/bugs/>.\n"
    ~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/>.\n"
    Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.
    ~"For help, type \"help\".\n"
    ~"Type \"apropos word\" to search for commands related to \"word\".\n"
    ^done
    -list-features
    ^done,features=["frozen-varobjs","pending-breakpoints","thread-info","data-read-memory-bytes","breakpoint-notifications","ada-task-info","language-option","info-gdb-mi-command","undefined-command-error-code","exec-run-start-option"]
    -gdb-set disassembly-flavor intel
    ^error,msg="No symbol \"disassembly\" in current context."
    -gdb-set print demangle off
    ^done
    set remotetimeout 60
    &"set remotetimeout 60\n"
    =cmd-param-changed,param="remotetimeout",value="60"
    ^done
    target remote :52349
    &"target remote :52349\n"
    ~"Remote debugging using :52349\n"
    =thread-group-started,id="i1",pid="42000"
    =thread-created,id="1",group-id="i1"
    ~"invoke_abort () at /esp-idf/master/components/esp32/panic.c:137\n"
    &"137\t/esp-idf/master/components/esp32/panic.c: No such file or directory.\n"
    *stopped,frame={addr="0x4008f10f",func="invoke_abort",args=[],file="/esp-idf/master/components/esp32/panic.c",fullname="/esp-idf/master/components/esp32/panic.c",line="137"},thread-id="1",stopped-threads="all"
    ^done
    info shared
    &"info shared\n"
    ~"No shared libraries loaded at this time.\n"
    ^done
    mon reset halt
    &"mon reset halt\n"
    @"JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)\n"
    @"JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)\n"
    @"esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).\n"
    @"esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).\n"
    @"Target halted. PRO_CPU: PC=0x5000004B (active) APP_CPU: PC=0x00000000 \n"
    @"esp32: target state: halted\n"
    @"esp32: Core was reset (pwrstat=0x1F, after clear 0x0F).\n"
    @"Target halted. PRO_CPU: PC=0x40000400 (active) APP_CPU: PC=0x40000400 \n"
    @"esp32: target state: halted\n"
    ^done
    mon program_esp32 "c:/Users/Don/source/CoralVue/Atlas/Debug/bootloader/bootloader.bin" 0x1000
    &"mon program_esp32 \"c:/Users/Don/source/CoralVue/Atlas/Debug/bootloader/bootloader.bin\" 0x1000\n"
    @"JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)\n"
    @"JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)\n"
    @"esp32: Debug controller was reset (pwrstat=0x5F, after clear 0x0F).\n"
    @"esp32: Core was reset (pwrstat=0x5F, after clear 0x0F).\n"
    @"Target halted. PRO_CPU: PC=0x5000004B (active) APP_CPU: PC=0x00000000 \n"
    @"esp32: target state: halted\n"
    @"esp32: Core was reset (pwrstat=0x1F, after clear 0x0F).\n"
    @"Target halted. PRO_CPU: PC=0x40000400 (active) APP_CPU: PC=0x40000400 \n"
    @"esp32: target state: halted\n"
    @"** Programming Started **\n"
    @"auto erase enabled\n"
    @"no flash bank found for address 1000\n"
    @"wrote 0 bytes from file c:/Users/Don/source/CoralVue/Atlas/Debug/bootloader/bootloader.bin in 0.000000s (nan KiB/s)\n"
    @"** Programming Finished **\n"
    ^done
    -target-disconnect
    =thread-group-exited,id="i1"
    ^done
    -gdb-exit
    ^exit

     

    Attachments:
    You must be logged in to view attached files.
    #21359
    support
    Keymaster

    Hi,

    Thanks for clarifying this. Please try clicking the “test connection” button in both cases, copy the OpenOCD command line shown in the test window and then compare the working command line with non-working one. Then please try running OpenOCD manually to determine a specific flag that causes the issue.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.