VSCODE: purchased Wrover-kit, serial flashing does not work and JTAG flash/debug does not work
Posted: Mon Mar 08, 2021 1:11 pm
After many attempts to get JTAG debugging working with a Lyra-T board, I bought a Wrover-kit, which has on board JTAG. This to rule out any hardware issues which might exist in my Lyra-T setup. Unfortunately again issues. When attempting to flash the 'blink' application serially from VSCODE:
"Failed to flash the device (JTag), please try again [got response: 'invalid command name "program_esp_bins"', expecting: '0']
After deleting my 'blink' project from disk and doing a new "create project from blink example" I was able to serially flash it.
Then pressed F5 it started the debugger, stopped at a breakpoint and I could single step.
I was, hoever not able to stop the debugger and needed to exit VScode. Tried again.. behaviour seems inconsistent, sometimes I ams able to start debugging, sometimes I am able to flash. And often I see the serial flash error as listen above.
It seems to recover from that state is to power off the board and exit VScode.
Unable to et JTAG flashing working and today it happened again. Updated my settings.json for a new openOCD version and 15 minutes later it as changed back again. Is the IDF extension doing this ?
I really do appreciate the efffort the Espressif guys put into it, but sometimes I really wonder of anything has been tested
on a 'clean' Windows system.
When attempting to flash using JTAG (lastest OpenOcd)$ H:\.espressif\python_env\idf4.2_py3.9_env\Scripts\python.exe
esptool.py v3.0
Serial port COM22
Connecting....
Detecting chip type... ESP32
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: a8:03:2a:ec:00:30
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
Compressed 3072 bytes to 103...
A fatal error occurred: Timed out waiting for packet content
The terminal process terminated with exit code: 2.
"Failed to flash the device (JTag), please try again [got response: 'invalid command name "program_esp_bins"', expecting: '0']
After deleting my 'blink' project from disk and doing a new "create project from blink example" I was able to serially flash it.
Then pressed F5 it started the debugger, stopped at a breakpoint and I could single step.
I was, hoever not able to stop the debugger and needed to exit VScode. Tried again.. behaviour seems inconsistent, sometimes I ams able to start debugging, sometimes I am able to flash. And often I see the serial flash error as listen above.
It seems to recover from that state is to power off the board and exit VScode.
Unable to et JTAG flashing working and today it happened again. Updated my settings.json for a new openOCD version and 15 minutes later it as changed back again. Is the IDF extension doing this ?
I really do appreciate the efffort the Espressif guys put into it, but sometimes I really wonder of anything has been tested
on a 'clean' Windows system.