Hi,

when I am connected to a target and debugging in Ozone via J-Link Pro, and then the target is shut down or the connection is lost for some other reason, Ozone is stuck and cannot be used anymore.

- Debug.Stop(); has no effect
- trying to quit the whole application results in a dialog box asking whether the session should be closed. Both choices offered, Yes and No do not have any effect. I can only ask Windows 10 to terminate the application. Is this a known problem?

Thanks and regards

Hi,

I am running Ozone V3.10 (which is the most recent one) on Windows 10 Pro and this happened to me with a custom board (stm32f412ce) as well as with the blue pill (stm32f103c8t6).

Both boards have an exteral power supply and if that goes away, Ozone gets stuck in the way I described.

Well, I just tried to reproduce this and failed when:
- disconnecting the power supply from the board
- sending the PC to sleep while the debugging session was active

In both cases, Ozone behaved correctly. ... But I can observe the other behaviour regularily; I am just not sure how to reproduce it properly.

In one case I got the message that the J-Link was started in bootloader mode and needed its firmware to be re-flashed. ... Weird, but that's another issue.

Kind regards

Hi,

thanks for trying. Yes, I found the V3.10c shortly after writing and saw the issue with it as well. Surprised me that a one month old installation was outdated by several versions already.

I have problems reproducing the behaviour quickly but leaving the setup in a debugging session running over night by just Locking the screen (and Windows going to hibernate later) gives me a good chance of seeing this.

However, this might be a very rare (and not advisable) thing to do, so I will just try to avoid it.

If I find a way to reproduce this more easily, I will report back.

Cheers

Hi,

now using 3.10d I just had this happeing to me right in the middle of a debugging session.
No lost connection, no Windows hibernate.
Ozone just stopped sampling data and now I can neither stop debugging nor quit the application.

There is no output on the Console when it stops sampling.

I'll add a screen shot of the status bar, maybe it's helpful.

Best regards

Hi Nino,

there is a watchdog but it did not hit. And we do not use any low-power modes.

it does not happen regularly enough to answer if it happens around the same sampling number. I will check next time.

The Data Limit configured is 16000

Best regards

Hi,

I just observed that after around 420 000 samples the Timeline view and the status bar (when Data Sampling or Timeline are selected) become rather slow and even stuck. The Data Sampling view is showing data just normal.

I am running at a sampling frequenzy of 10kHz just for provoking this behaviour and have 15 expressions in the Data Sampling table, some of which are updated quite often (probably close to the 10kHz).

Seems the Timeline feature is at its limits here and maybe this leads to the observes behaviour of not being able to close the application (althou I am currently not running into this).

Best regards

Hi,

a few more observations.

It is easiest to trigger the stuck timeline at 10kHz. When reaching around 420 000 samples, it becomes stuck here.

If I then set the Sampling Freq to 100Hz, the graph moves again.

If I set the Sampling Freq to 500Hz however, the graph starts to move in the wrong direction. The time also counts backwards at that point.

Set back to 100Hz the graph moves again but it does not show current values but values from the past. I can drag the graph forward and see more values but it snaps back to the wrong position in time as soon as I release the mouse button.

Best regards

Hi,

this still hits me several times a week in Ozone v3.20a.

I do not know how to cleanly reproduce but it always happens when a debugging session runs for an hour or two.



Maybe you are able to check your code for the case when the debugging session is not stoppable anymore.


Edit: It happened again, this time with a different Sampling Frequency. In the video I had set it to 1kHz and now at 100Hz.
Both times it foze at around 400 000ms



Cheers

Hi,

since I can only debug this at work and I am usually busy doing other stuff, I find it hard to create a minimal example project.

Would it be possible for you to send me some debug version of Ozone which writes some log file?

This still happens to me two to four times a day, which is quite inconvenient.

Cheers