Hello,
I'm trying to debug ESP32 (ESP32-WROOM-32D) with my J-Link Ultra with Eclipse (2020-03). I actually can connect, flash and start debugging but when I want to step into a function, Eclipse hangs. I have no error message and I need to shutdown Eclipse and start over.
I've tested with different speed from 500 kHz to 20000 kHz but I still get the problem. Actually, it's even worst with low speed, the debugger connects but when eclipse is loading the different views in the debug perspective, it hangs so I can't even start debugging.
I've tried with WinUSB drivers and LibusbK but it doesn't change anything.
Has anyone succeeded debugging with J-Link Ultra ?
Thanks,
Hugo
Debug ESP32 with J-Link Ultra and Eclipse
-
- Posts: 73
- Joined: Mon Mar 09, 2020 7:36 pm
Re: Debug ESP32 with J-Link Ultra and Eclipse
I am using a JLINK Plus Compact, and I found that I had to update to the most recent openOCD in order to get cosole gdb to work.
You might want to try that. The system does not seem to update the tools in use automatically.
You might want to try that. The system does not seem to update the tools in use automatically.
-
- Posts: 73
- Joined: Mon Mar 09, 2020 7:36 pm
Re: Debug ESP32 with J-Link Ultra and Eclipse
I also found issues with OCD, and have updated to v0.10.0-esp32-20200420.
Console GDB works, but the Eclipse integration fails. I am trying to figure out the cause.
Anyone else updating the version of ICD will also have to update the tools.json file to indicate the preferred version or build will not work
Console GDB works, but the Eclipse integration fails. I am trying to figure out the cause.
Anyone else updating the version of ICD will also have to update the tools.json file to indicate the preferred version or build will not work
Re: Debug ESP32 with J-Link Ultra and Eclipse
Sorry for late answer, I have been working on another project.
Thanks for your answer, I'm already on openocd version v0.10.0-esp32-20200420 and tools.json is pointing to this version as well.
I agree, the problem seems to be coming from Eclipse integration. When I look at openocd console, I see that everything seems to work, the program breaks at main bug Eclipse is freezed... I'm using Eclipse 2020-03 because 2020-06 was not working with ESP IDF.
Hugo
Thanks for your answer, I'm already on openocd version v0.10.0-esp32-20200420 and tools.json is pointing to this version as well.
I agree, the problem seems to be coming from Eclipse integration. When I look at openocd console, I see that everything seems to work, the program breaks at main bug Eclipse is freezed... I'm using Eclipse 2020-03 because 2020-06 was not working with ESP IDF.
Hugo
Re: Debug ESP32 with J-Link Ultra and Eclipse
hbouchard ,
At the risk of complicating the problem description, I am successful in using Eclipse 2020-06 (4.16.0), build id: 20200615-1200 with ESP IDF v4.2-dev-2243-gcf056a7d0 on Ubuntu Linux 20.04 LTS / Gnome 3.36.3. I have not tried using JTAG with or without Eclipse (since I don't have JTAG equipment).
You say that you are using Eclipse 2020-03 because 2020-06 "was not working with ESP IDF." What problem(s) did you encounter using 2020-06?
At the risk of complicating the problem description, I am successful in using Eclipse 2020-06 (4.16.0), build id: 20200615-1200 with ESP IDF v4.2-dev-2243-gcf056a7d0 on Ubuntu Linux 20.04 LTS / Gnome 3.36.3. I have not tried using JTAG with or without Eclipse (since I don't have JTAG equipment).
You say that you are using Eclipse 2020-03 because 2020-06 "was not working with ESP IDF." What problem(s) did you encounter using 2020-06?
Re: Debug ESP32 with J-Link Ultra and Eclipse
Hi Halfnium,
I manage to successfully use Eclipse 2020-06. The problem I had was for installing the ESP32 IDF plugin. I only had java JRE 8 installed. the workaround described here (https://github.com/espressif/idf-eclips ... n/releases) which tells you to disable "Verify provisioning operation is compatible with currently running JRE" in Eclipse preferences doesn't work at all (at least on Windows 10). I couldn't open my Eclipse workspace any more.
What one needs to do is install latest Java SDK (which is v14 as I write), reinstall Eclipse and pick this last Java version in the first installation step.
With this Eclipse version and latest ESP32 IDF pluging installed, I can now use my JLink Ultra+ debugger. Wooohoooo! Finally!!
I'm using Eclipse 2020-06 (4.16.0), build id: 20200615-1200 with ESP IDF v4.3-dev-472-gcf056a7d0 (latest tag on master as I write) with Windows 10.
Thanks for pointing out that Eclipse 2020-06 could be used.
Hugo
I manage to successfully use Eclipse 2020-06. The problem I had was for installing the ESP32 IDF plugin. I only had java JRE 8 installed. the workaround described here (https://github.com/espressif/idf-eclips ... n/releases) which tells you to disable "Verify provisioning operation is compatible with currently running JRE" in Eclipse preferences doesn't work at all (at least on Windows 10). I couldn't open my Eclipse workspace any more.
What one needs to do is install latest Java SDK (which is v14 as I write), reinstall Eclipse and pick this last Java version in the first installation step.
With this Eclipse version and latest ESP32 IDF pluging installed, I can now use my JLink Ultra+ debugger. Wooohoooo! Finally!!
I'm using Eclipse 2020-06 (4.16.0), build id: 20200615-1200 with ESP IDF v4.3-dev-472-gcf056a7d0 (latest tag on master as I write) with Windows 10.
Thanks for pointing out that Eclipse 2020-06 could be used.
Hugo
Re: Debug ESP32 with J-Link Ultra and Eclipse
Hugo,
Not quite sure, but it seems I jogged you toward finding your solution. If so, I'm glad.
On my Ubuntu system, 'java --version' yields
I went for this according to the Java SE 11 (LTS) recommendation in the ESP-IDF Eclipse Plugin 'README.md.' Does what you've said imply upgrade to Java SE 14.0.2 (the latest release according to the Java web site) in order to get JTAG going?
ESP32 is my first foray into cross-platform development. I feel blind trying to desk-check debug, without visibility on the hardware's actual state. All the more so with FreeRTOS in the mix. Could I impose on you for guidance toward a hobbyist-class JTAG setup?
Not quite sure, but it seems I jogged you toward finding your solution. If so, I'm glad.
On my Ubuntu system, 'java --version' yields
Code: Select all
openjdk 11.0.7 2020-04-14
OpenJDK Runtime Environment (build 11.0.7+10-post-Ubuntu-3ubuntu1)
OpenJDK 64-Bit Server VM (build 11.0.7+10-post-Ubuntu-3ubuntu1, mixed mode, sharing)
ESP32 is my first foray into cross-platform development. I feel blind trying to desk-check debug, without visibility on the hardware's actual state. All the more so with FreeRTOS in the mix. Could I impose on you for guidance toward a hobbyist-class JTAG setup?
Re: Debug ESP32 with J-Link Ultra and Eclipse
Halfnium,
No java SE 14 is not required. What is required is Java SE 11 or later so I installed the latest but it should work with the version you have.
If you need help for JTAG-setup, feel free to ask but be aware that I don't have any Linux installed on my computer and sometimes setup might be a little different. Send me private messages unless it could be useful for the community.
Hugo
No java SE 14 is not required. What is required is Java SE 11 or later so I installed the latest but it should work with the version you have.
If you need help for JTAG-setup, feel free to ask but be aware that I don't have any Linux installed on my computer and sometimes setup might be a little different. Send me private messages unless it could be useful for the community.
Hugo
Who is online
Users browsing this forum: Kniroxe and 82 guests