Unable to program ESP32-SOLO-1

ajaykk
Posts: 4
Joined: Fri Oct 05, 2018 2:34 pm
Location: India

Unable to program ESP32-SOLO-1

Postby ajaykk » Fri Oct 05, 2018 3:24 pm

I am unable to program ESP32-SOLO-1 using JTAG on the ESP-WROVER-KIT v3.

JTAG Connections:-
conn.jpg
conn.jpg (15.83 KiB) Viewed 190 times


also, I enabled single core mode in menuconfig.

openocd output:-

Code: Select all

$ ~/esp/openocd-esp32/bin/openocd -s ~/esp/openocd-esp32/share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg -c "program_esp32 build/hello-world.bin 0x10000 verify exit"

output:-
Open On-Chip Debugger 0.10.0-dev (2018-09-20-12:52)
Licensed under GNU GPL v2
For bug reports, read
   http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
esp32 interrupt mask on
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"
Info : clock speed 20000 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: Debug controller was reset (pwrstat=0xFF, after clear 0xFF).
Info : esp32: Core was reset (pwrstat=0xFF, after clear 0xFF).
Error: cpu0: esp32_fetch_all_regs (line 225): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 225): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 225): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: cpu0: esp32_fetch_all_regs (line 255): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 255): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 255): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: Exception reading pc!

Info : Target halted. PRO_CPU: PC=0x00000000 (active)    APP_CPU: PC=0x00000000
Error: cpu0: xtensa_write_memory (line 759): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 759): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 759): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 4 bytes at address 0x3FF5F064, data - a1, 3a, d8, 50, a1, 3a, d8, 50
embedded:startup.tcl:21: Error:
in procedure 'program_esp32'
in procedure 'init' called at file "/home/ajay/esp/openocd-esp32/share/openocd/scripts/target/esp32.cfg", line 119
in procedure 'ocd_bouncer'
in procedure 'esp_smp_break_config'
in procedure 'esp32' called at file "/home/ajay/esp/openocd-esp32/share/openocd/scripts/target/esp32.cfg", line 54
in procedure 'ocd_bouncer'
in procedure 'esp_core_halt'
in procedure 'esp32' called at file "/home/ajay/esp/openocd-esp32/share/openocd/scripts/target/esp32.cfg", line 44
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21

Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : cpu0: Failed reading 4 bytes at address 0x3FF00030
Error: Failed to read target memory (-4)!
cpu0: Current bits set: BreakIn BreakOut RunStallIn DebugModeOut
cpu1: Current bits set: BreakIn BreakOut RunStallIn DebugModeOut
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
cpu0: Current bits set: BreakIn BreakOut RunStallIn DebugModeOut
cpu1: Current bits set: BreakIn BreakOut RunStallIn DebugModeOut
Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_read_memory (line 652): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : cpu0: Failed reading 76 bytes at address 0x50000000
Error: esp32_soc_reset 523 err=-4
in procedure 'program_esp32'
in procedure 'reset' called at file "/home/ajay/esp/openocd-esp32/share/openocd/scripts/target/esp32.cfg", line 124
in procedure 'ocd_bouncer'

** Unable to reset target **
shutdown command invoked


BTW i am able to program the ESP32-DEVKIT-C-V4 using the same method without any problems. The issue is only with SOLO.

ESP_Sprite
Posts: 1941
Joined: Thu Nov 26, 2015 4:08 am

Re: Unable to program ESP32-SOLO-1

Postby ESP_Sprite » Sat Oct 06, 2018 4:53 am

Fwiw: 'Error: JTAG scan chain interrogation failed: all ones' usually means there's something wrong on a very low level: the JTAG adapter physically cannot talk to the JTAG hardware. Are you sure the SOLO-1 does not have a program in it that reconfigures the JTAG pins for something else?

ajaykk
Posts: 4
Joined: Fri Oct 05, 2018 2:34 pm
Location: India

Re: Unable to program ESP32-SOLO-1

Postby ajaykk » Sat Oct 06, 2018 5:51 am

This is a fresh module and first time programming it.

can you give us proper connection details and configurations for this module?

User avatar
beegee1962
Posts: 7
Joined: Fri Oct 13, 2017 8:42 am
Location: Philippines
Contact:

Re: Unable to program ESP32-SOLO-1

Postby beegee1962 » Tue Oct 09, 2018 3:13 am

EDIT:
Below shown problem is solved by keeping the BOOT button pressed while the firmware is downloaded.
I read about similar problems with cheap Chinese dev boards, but this board is an original Espressif DevKitC-S1.
Was not expecting a bad HW design from Espressif.

-------------- SOLVED --------------
Similar problem here. ESP32-SOLO is showing on serial port, I can get debug output when starting the module.
Get as well the

Code: Select all

rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
waiting for download

when pushing EN and BOOT.
But when I try to flash the module I get only

Code: Select all

$ make flash
Toolchain path: /opt/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
Toolchain version: crosstool-ng-1.22.0-80-g6c4433a5
Compiler version: 5.2.0
Python requirements from B:/msys32/home/BeeGee/esp/esp-idf/requirements.txt are satisfied.
Flashing binaries to serial port COM21 (app at offset 0x10000)...
esptool.py v2.5.1
Serial port COM21
Connecting........_____....._____....._____....._____....._____....._____....._____

A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
make: *** [/home/BeeGee/esp/esp-idf/components/esptool_py/Makefile.projbuild:63: flash] Error 2


Where did you find single core mode in menuconfig? I cannot find this setting.
Do I need different toolchain or have to clone a different ESP-IDF version to flash the SOLO?
Or do I need extra settings in make?

ajaykk
Posts: 4
Joined: Fri Oct 05, 2018 2:34 pm
Location: India

Re: Unable to program ESP32-SOLO-1

Postby ajaykk » Tue Oct 09, 2018 12:08 pm

My esp-solo module was faulty. I tried with another solo module, was able to flash program using serial bootloader but when trying with JTAG, I am getting this message:-

Code: Select all

$~/esp/openocd-esp32/bin/openocd -s ~/esp/openocd-esp32/share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg -c "program_esp32 build/app-template.bin 0x10000 verify exit"

Open On-Chip Debugger 0.10.0-dev (2018-09-20-12:52)Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
esp32 interrupt mask on
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"
Info : clock speed 20000 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0xffffffff (mfg: 0x7ff (<invalid>), part: 0xffff, ver: 0xf)
Warn : JTAG tap: esp32.cpu1       UNEXPECTED: 0xffffffff (mfg: 0x7ff (<invalid>), part: 0xffff, ver: 0xf)
Error: JTAG tap: esp32.cpu1  expected 1 of 1: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu1: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
cpu0: Current bits set: none
cpu1: Current bits set: BreakIn
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0xffffffff (mfg: 0x7ff (<invalid>), part: 0xffff, ver: 0xf)
Warn : JTAG tap: esp32.cpu1       UNEXPECTED: 0xffffffff (mfg: 0x7ff (<invalid>), part: 0xffff, ver: 0xf)
Error: JTAG tap: esp32.cpu1  expected 1 of 1: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu1: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
cpu0: Current bits set: none
cpu1: Current bits set: BreakIn
Error: timed out while waiting for target halted / 1 - 2
Error: timed out while waiting for target halted / 1 - 2
Error: timed out while waiting for target halted / 1 - 2


beegee1962 wrote:Where did you find single core mode in menuconfig? I cannot find this setting.
Do I need different toolchain or have to clone a different ESP-IDF version to flash the SOLO?
Or do I need extra settings in make?

You don't need anything extra, this setting is under > Component config > FreeRTOS

User avatar
beegee1962
Posts: 7
Joined: Fri Oct 13, 2017 8:42 am
Location: Philippines
Contact:

Re: Unable to program ESP32-SOLO-1

Postby beegee1962 » Wed Oct 10, 2018 2:40 am

Thanks for your feedback.
I found the settings in menuconfig already.
But still have the problem that I need to push BOOT button while flashing over USB.
Don't have a JTAG adapter (yet), so I cannot test flashing over JTAG.

Who is online

Users browsing this forum: No registered users and 13 guests