I'm owner of a J-Link-Edu v8.0
Most of the time it collects dust in the drawer because I am accustomed to using the ST-Link.
A few weeks ago I was forced to debug 2 boards at the same time (using Crossworks with CTL (Rtos) / Linux Debian); so my J-Link was resurrected to life again.
I upgraded the firmware but to my astonishment I had to realize, that with J-Link I was not able to run the program correctly.
After few steps, when I was going to switch the task, the Debug-Cursor didn't move.
I downloaded Ozone and with this I had no problem to run and debug my program correctly.
My suspicion is, that Crossworks is using the wrong driver (my current setting is /opt/SEGGER/JLink/libjlinkarm.so).
Because Ozone was an unfamiliar environment for me, I solved my problem by replacing J-Link with a ST-Link v2.
However, I would be interested to know why this did not work with J-Link. Thanks in advance.
Most of the time it collects dust in the drawer because I am accustomed to using the ST-Link.
A few weeks ago I was forced to debug 2 boards at the same time (using Crossworks with CTL (Rtos) / Linux Debian); so my J-Link was resurrected to life again.
I upgraded the firmware but to my astonishment I had to realize, that with J-Link I was not able to run the program correctly.
After few steps, when I was going to switch the task, the Debug-Cursor didn't move.
I downloaded Ozone and with this I had no problem to run and debug my program correctly.
My suspicion is, that Crossworks is using the wrong driver (my current setting is /opt/SEGGER/JLink/libjlinkarm.so).
Because Ozone was an unfamiliar environment for me, I solved my problem by replacing J-Link with a ST-Link v2.
However, I would be interested to know why this did not work with J-Link. Thanks in advance.