Debugging using Jlink official driver

[Stat_headcrabed]

I found that segger has just added Xtensa LX6/LX7 core support.https://www.segger.com/downloads/jlink/ ... JLink.html
So would esp32 series officially support segger tools?

[ESP_Sprite]

Added native debug support for Cadence Xtensa LX architecture via Cadence xt-gdb client (Xtensa Xplorer IDE).

This makes it looks like the LX6/LX7 support only works with the closed-source, NDA'ed Cadence tools. Given the fact that the ESP32/ESP8266 ecosystem doesn't use this at all (we use gcc, openocd and gdb even internally) I doubt that there's any good support for our chips there.

[Stat_headcrabed]

Added native debug support for Cadence Xtensa LX architecture via Cadence xt-gdb client (Xtensa Xplorer IDE).

This makes it looks like the LX6/LX7 support only works with the closed-source, NDA'ed Cadence tools. Given the fact that the ESP32/ESP8266 ecosystem doesn't use this at all (we use gcc, openocd and gdb even internally) I doubt that there's any good support for our chips there.

This still seems promising. As far as I know, segger 's gdb server is using standard protocol to communicate with gdb client. And using segger 's driver could avoid changing driver frequently in circumstances like debugging another chip at the same time. Could you guys write a jlink script for esp32 to test?
https://wiki.segger.com/J-Link_Xtensa_specifics

[ESP_Sprite]

I've asked our tool group to take a look at it. No guarantees on when/if they get around to it, though, and if we'll make something official out of it; keeping stuff compatible with multiple toolchains adds to the maintenance load.

[ESP_igrr]

One thing to note is that some features supported in OpenOCD may be hard to support with Jlink, for example:
- Flashing over JTAG
- Breakpoints in flash
- Chip reset (not just CPU reset)
- Disabling SoC level memory protection (for esp32-s2 and esp32-s3) when debugging
It is possible to do some basic debugging without these features, but the experience will probably not be very good.
Anyway, as ESP_Sprite said, we will give it a try.

[Stat_headcrabed]

One thing to note is that some features supported in OpenOCD may be hard to support with Jlink, for example:
- Flashing over JTAG
- Breakpoints in flash
- Chip reset (not just CPU reset)
- Disabling SoC level memory protection (for esp32-s2 and esp32-s3) when debugging
It is possible to do some basic debugging without these features, but the experience will probably not be very good.
Anyway, as ESP_Sprite said, we will give it a try.

Thank you guys. Looking forward to hear more about this. Btw seems that J-Flash already have download algorithm for esp32 series. Maybe contacting segger could help?

[Stat_headcrabed]

One thing to note is that some features supported in OpenOCD may be hard to support with Jlink, for example:
- Flashing over JTAG
- Breakpoints in flash
- Chip reset (not just CPU reset)
- Disabling SoC level memory protection (for esp32-s2 and esp32-s3) when debugging
It is possible to do some basic debugging without these features, but the experience will probably not be very good.
Anyway, as ESP_Sprite said, we will give it a try.

@ESP_igrr Any news about it?

[ESP_igrr]

Not yet, I'm afraid. We haven't started working on this.

[Darko_T]

Not yet, I'm afraid. We haven't started working on this.

Hi,
Any news?
Would be nice to use Ozone & JLink on ESP32 S3 and others.

Darko