satau

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Problem: ESP32 Wroom with OpenOCD #11410
    satau
    Participant

    I can confirm that everything is working fine after flashing a program that enables dual core mode. Thankyou ASH74!

    Mods – It may be worth noting the following:

    1. If ESP32 is running in single core mode, cpu1 will fail to halt when attempting to program/debug via JTAG using VisualGDB.
    2. The TIAO/TUMPA JTAG interface appears to be working fine using the VisualGDB bundled drivers – flashes ok and is hitting breakpoints when running code.
    in reply to: Problem: ESP32 Wroom with OpenOCD #11409
    satau
    Participant

    ASH74: I was able to flash one of the examples to the board that did not have “Run FreeRTOS only on first core” set and then I was able to debug my code in VisualGDB.

    Awesome. I’ll give that a try and see if it helps. Thanks for sharing!

    in reply to: Problem: ESP32 Wroom with OpenOCD #11407
    satau
    Participant

    Thanks for the reply. I have switched out the ESP32 DevKitC board for a brand new one – I’m seeing the same issue. Unfortunately I don’t have another JTAG interface, and it could be a costly exercise to purchase and try multiple interfaces until it (hopefully) works. Can you link me a list of supported models?

    The original poster is using an Olimex interface and seeing a similar error –  ‘cpu1 not halted’. So although this doesn’t rule out a TIAO TUMPA specific issue, I’m hoping that someone who has seen this problem before can jump in and help out.

    More detailed logs from the OpenOCD window are below:

    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.cpu0: Core was reset (pwrstat=0x1F, after clear 0x0F).\n"
    @"esp32.cpu0: Target halted, pc=0x40000400\n"
    @"esp32.cpu1: target not halted\n"
    @"in procedure 'reset' \n"
    @"in procedure 'ocd_bouncer' \n"
    @"in procedure 'ocd_process_reset' \n"
    @"in procedure 'ocd_process_reset_inner' called at file \"embedded:startup.tcl\", line 248\n"
    @"in procedure 'esp32.cpu0' called at file \"embedded:startup.tcl\", line 349\n"
    @"in procedure 'ocd_bouncer'\n"
    @"\n"
    @"esp32.cpu0: target state: halted\n"
    ^done
    restore C:/SysGCC/esp32/esp32-bsp/sysprogs/flashprog/ESP32FlashProg.bin binary 0x40090000 0 0xe14
    &"restore C:/SysGCC/esp32/esp32-bsp/sysprogs/flashprog/ESP32FlashProg.bin binary 0x40090000 0 0xe14\n"
    ~"Restoring binary file C:/SysGCC/esp32/esp32-bsp/sysprogs/flashprog/ESP32FlashProg.bin into memory (0x40090000 to 0x40090e14)\n"
    ^done
    mon esp108 run_alg 0x400902d0 0x40090df8 20000 a1=0x3ffd0404 a10=0 a11=4096 a12=0 a0 pc
    &"mon esp108 run_alg 0x400902d0 0x40090df8 20000 a1=0x3ffd0404 a10=0 a11=4096 a12=0 a0 pc\n"
    @"Target did not halt within 20000 msec\n"
    @"\n"
    @"esp32.cpu0: Target halted, pc=0x40090DF8\n"
    @"esp32.cpu0: target state: halted\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.cpu0: Core was reset (pwrstat=0x1F, after clear 0x0F).\n"
    @"esp32.cpu0: Target halted, pc=0x40000400\n"
    @"esp32.cpu1: target not halted\n"
    @"in procedure 'reset' \n"
    @"in procedure 'ocd_bouncer' \n"
    @"in procedure 'ocd_process_reset' \n"
    @"in procedure 'ocd_process_reset_inner' called at file \"embedded:startup.tcl\", line 248\n"
    @"in procedure 'esp32.cpu0' called at file \"embedded:startup.tcl\", line 349\n"
    @"in procedure 'ocd_bouncer'\n"
    @"\n"
    @"esp32.cpu0: target state: halted\n"
    ^done
    restore C:/SysGCC/esp32/esp32-bsp/sysprogs/flashprog/ESP32FlashProg.bin binary 0x40090000 0 0xe14
    &"restore C:/SysGCC/esp32/esp32-bsp/sysprogs/flashprog/ESP32FlashProg.bin binary 0x40090000 0 0xe14\n"
    ~"Restoring binary file C:/SysGCC/esp32/esp32-bsp/sysprogs/flashprog/ESP32FlashProg.bin into memory (0x40090000 to 0x40090e14)\n"
    ^done
    mon esp108 run_alg 0x400902d0 0x40090df8 20000 a1=0x3ffd0404 a10=0 a11=4096 a12=0 a0 pc
    &"mon esp108 run_alg 0x400902d0 0x40090df8 20000 a1=0x3ffd0404 a10=0 a11=4096 a12=0 a0 pc\n"
    @"Target did not halt within 20000 msec\n"
    @"\n"
    @"esp32.cpu0: Target halted, pc=0x40090DF8\n"
    @"esp32.cpu0: target state: halted\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.cpu0: Core was reset (pwrstat=0x1F, after clear 0x0F).\n"
    @"esp32.cpu0: Target halted, pc=0x40000400\n"
    @"esp32.cpu1: target not halted\n"
    @"in procedure 'reset' \n"
    @"in procedure 'ocd_bouncer' \n"
    @"in procedure 'ocd_process_reset' \n"
    @"in procedure 'ocd_process_reset_inner' called at file \"embedded:startup.tcl\", line 248\n"
    @"in procedure 'esp32.cpu0' called at file \"embedded:startup.tcl\", line 349\n"
    @"in procedure 'ocd_bouncer'\n"
    @"\n"
    @"esp32.cpu0: target state: halted\n"
    ^done
    restore C:/SysGCC/esp32/esp32-bsp/sysprogs/flashprog/ESP32FlashProg.bin binary 0x40090000 0 0xe14
    &"restore C:/SysGCC/esp32/esp32-bsp/sysprogs/flashprog/ESP32FlashProg.bin binary 0x40090000 0 0xe14\n"
    ~"Restoring binary file C:/SysGCC/esp32/esp32-bsp/sysprogs/flashprog/ESP32FlashProg.bin into memory (0x40090000 to 0x40090e14)\n"
    ^done
    mon esp108 run_alg 0x400902d0 0x40090df8 20000 a1=0x3ffd0404 a10=0 a11=4096 a12=0 a0 pc
    &"mon esp108 run_alg 0x400902d0 0x40090df8 20000 a1=0x3ffd0404 a10=0 a11=4096 a12=0 a0 pc\n"
    @"Target did not halt within 20000 msec\n"
    @"\n"
    @"esp32.cpu0: Target halted, pc=0x40090DF8\n"
    @"esp32.cpu0: target state: halted\n"
    ^done
    • This reply was modified 7 years, 5 months ago by satau.
    in reply to: Problem: ESP32 Wroom with OpenOCD #11398
    satau
    Participant

    I’m having what appears to be the same problem. I have not succeeded in flashing the ESP32 at all. VisualGDB-5.2r9. I have manually installed the esp32-gcc5.2.0.exe toolchain and recompiled the project, this did not help. I’m using the TUMPA JTAG interface. Any suggestions?

    Open On-Chip Debugger 0.9.0 (2017-05-09)
    Licensed under GNU GPL v2
    For bug reports, read http://openocd.org/doc/doxygen/bugs.html
    none separate
    Info : auto-selecting first available session transport "jtag". To override use 'transport select <tra
    nsport>'.
    adapter speed: 3000 kHz
    Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
    Info : clock speed 3000 kHz
    Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0
    x1)
    Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0
    x1)
    Info : esp32.cpu0: Target halted, pc=0x40090DF8
    Error: The 'mww' command must be used after 'init'.
    in procedure 'init' 
    in procedure 'ocd_bouncer' 
    in procedure 'flash' 
    in procedure 'ocd_bouncer'
    
    Info : accepting 'gdb' connection on tcp/3333
    Interrupt suppression during single-stepping is now enabled
    Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0
    x1)
    Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0
    x1)
    Info : esp32.cpu0: Core was reset (pwrstat=0x1F, after clear 0x0F).
    Info : esp32.cpu0: Target halted, pc=0x40000400
    Warn : esp32.cpu1: target not halted
    in procedure 'reset' 
    in procedure 'ocd_bouncer' 
    in procedure 'ocd_process_reset' 
    in procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 248
    in procedure 'esp32.cpu0' called at file "embedded:startup.tcl", line 349
    in procedure 'ocd_bouncer'
    
    esp32.cpu0: target state: halted
    Target did not halt within 5000 msec
    in reply to: OpenOCD Config Help #11335
    satau
    Participant

    Ok I think it’s a USB hardware passthrough issue related to the VM that I’m running in. On bare metal I’m now seeing the following output with nothing connected to the JTAG pins:

    Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
    adapter speed: 3000 kHz
    Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
    Info : clock speed 3000 kHz
    Error: JTAG scan chain interrogation failed: all ones
    Error: Check JTAG interface, timings, target power, etc.
    Error: Trying to use configured scan chain anyway...
    Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
    Warn : Bypassing JTAG setup events due to errors
    Info : esp32.cpu0: Debug controller was reset (pwrstat=0xFF, after clear 0xFF).
    Info : esp32.cpu0: Core was reset (pwrstat=0xFF, after clear 0xFF).
    Info : esp32.cpu1: Debug controller was reset (pwrstat=0xFF, after clear 0xFF).
    Info : esp32.cpu1: Core was reset (pwrstat=0xFF, after clear 0xFF).
    Info : accepting 'telnet' connection on tcp/4444
    shutdown command invoked
    Info : dropped 'telnet' connection

    Does this look like it’s working now? Ie is this the expected output when we don’t have anything connected to the JTAG pins?

    • This reply was modified 7 years, 6 months ago by satau.
    in reply to: OpenOCD Config Help #11332
    satau
    Participant

    Oh dear… just realized that the config file is in fact already listed in the dropdown as ‘tumpa’

    So I’ve selected that, and hit ‘Test’, and I get the following output:

    Info : auto-selecting first available session transport “jtag”. To override use ‘transport select <transport>’.
    adapter speed: 3000 kHz
    Error: no device found
    Error: unable to open ftdi device with vid 0403, pid 8a98, description ‘*’, serial ‘*’ at bus location ‘*’

    • This reply was modified 7 years, 6 months ago by satau.
Viewing 6 posts - 1 through 6 (of 6 total)