Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic ESP32-WRover-Kit 4.1 hardware debugging crash (Read 1775 times)
vilu
Newbies
*
Offline


Posts: 3
Location: Italy
Joined: Jan 30th, 2022
ESP32-WRover-Kit 4.1 hardware debugging crash
Jan 30th, 2022 at 5:35pm
Print Post  
Hi Visual micro
I’m using Esp32 Wrover kit 4.1 board and I would like debugging it with hardware debugger on the board and with external J-Link, but I can’t due to GDB error
I’m using Visual Studio 2022 with Visual Micro ver2021.1105.2213 on Windows10 64 bit running on VMWare

I premise that I have done the following:
- install WinUSB driver for dualRS232 Interface0 (Interface1 use FTDI driver as default)
- install WinUSB driver for Jlink debugger (see attached image)
- I can succesfully program the board (vMicro>Uploader>Hardware Programmer) both with “F2232H Dual RS232” and with J-Link, so no doubt about J-Link connections and board functionalities
- succesfully debugging the board with VSCode+PIO using only the board (no J-Link)
(see attached image)
Jumper configuration when using “F2232H Dual RS232” mode
(see attached image)

Connection when using J-Link debugger (USB cable connected during testing!)
(see attached image)

I selected this configuration
(see attached image)

after programming the board (using the serial (interface1) or the hardware debugger) the code starts: led blinking correctly
so I try start debugging with Debug>Attach to process but GDB crash

trying with “F2232H Dual RS232” --> GDB error: unable to connect (see attached image)
attached build log e debugger log files

trying with J-LINK --> GDB error: exit code 1 (see attached image)
attached build log e debugger log files

Thanks in advance
Luca




  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2441
Joined: Feb 13th, 2019
Re: ESP32-WRover-Kit 4.1 hardware debugging crash
Reply #1 - Jan 31st, 2022 at 12:10pm
Print Post  
Thanks for the report and all of the detail.

If you try the ESP32 DEVKIT debug option for the on-board debugger this may help when using the onboard debugger.

If this does not help, we are currently working on updates to ensure the WROVER-E modules are correctly supported with a newer version of OpenOCD.

We will update when the newer version is available.

  
Back to top
IP Logged
 
vilu
Newbies
*
Offline


Posts: 3
Location: Italy
Joined: Jan 30th, 2022
Re: ESP32-WRover-Kit 4.1 hardware debugging crash
Reply #2 - Feb 2nd, 2022 at 8:42pm
Print Post  
thanks Simon for the quick reply.

Unfortunately I tried using the ESP32 DEVKIT debug option but got the same error. Undecided

I would like to ask you for more details:
1) is the issue related only to visual studio 2022?
2) is the issue related to the PSRAM presence in the WROVER-E module ?
3) in your answer you did not mention anything about using j-link
   Should actual version of the OpenOCD work with J-Link and Wrover-E module ?
4) today how can I debug the ESP-Wrover-Kit 4.1 board with hardware debugger and Visual Micro ?
   Maybe using a ESP-WROOM module as hardware debugger ?
   https://www.visualmicro.com/pics/ESP32DEVKIT_To_Board_Wiring_Diagram.png

Thanks in advance
Luca
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2441
Joined: Feb 13th, 2019
Re: ESP32-WRover-Kit 4.1 hardware debugging crash
Reply #3 - Feb 2nd, 2022 at 9:02pm
Print Post  
Thanks for the update.

We are still trying to resolve issues with the WROVER-E chips, which are now fitted to these boards (as shown in your photos).

The ESP wiring diagram you have mentioned is using the WROVER-KIT board as the debugger for an external ESP-WROOM module, so the opposite of what you need.

You can try the latest release (21.11.08-19) available at the top of the board below, and you will need to add the options mentioned on the post in a local board.txt to try the changes:
https://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES

If this does not resolve the issue, we hope to have another update available in the coming days to resolve this.
  
Back to top
IP Logged
 
vilu
Newbies
*
Offline


Posts: 3
Location: Italy
Joined: Jan 30th, 2022
Re: ESP32-WRover-Kit 4.1 hardware debugging crash
Reply #4 - Feb 4th, 2022 at 9:06am
Print Post  
Great !
with last VM update hardware debugging is working on ESP-Wrover-Kit using both external J-Link and and internal "F2232H Dual RS232" mode

Anyway some things still need to be fixed:
- press the pause button freeze VS2022: I need to kill OpenOCD process to un-freeze the IDE
- breakpoint stepping (F10, F11, ...) is quite slow

Good job Simon, thank you very much
I'm waiting for new updates
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint