A software interrupt ends on its own when viewing on trace...any explanation?

RE: A software interrupt ends on its own when viewing on trace...any explanation?

cpeng — Wed, 09 Dec 2020 18:21:40 GMT

Thanks for the tip jmr! I will give it a try if i have a chance.

RE: A software interrupt ends on its own when viewing on trace...any explanation?

jmr — Fri, 20 Nov 2020 09:44:35 GMT

Hej cpeng,
I have been successful using the OS.AddContextSwitchSymbol().
You can experiment with it easily by calling the function in the Ozone Console at the very beginning of your debugging session (e.g. halt at main)
If you are comfortable with the results, you may want to add the calls to your .jdebug file.

Happy debugging! :-)

RE: A software interrupt ends on its own when viewing on trace...any explanation?

cpeng — Thu, 19 Nov 2020 18:59:13 GMT

Hi jmr:

Unfortunately I haven't found the root cause of the problem, my intuition tells me that ozone doesn't really know how to handle hardware interrupts.

RE: A software interrupt ends on its own when viewing on trace...any explanation?

jmr — Thu, 19 Nov 2020 10:17:58 GMT

Hej cpeng, have you found a solution to this?

I'm facing a similar issue but with softDevice enabled. I found that Ozone provides a User Action called OS.AddContextSwitchSymbol() which AFAICS can be used to make Ozon aware of a context switch. However, until now Ozone seems to be unhappy with it as it stalls and I have to kill the application.

RE: A software interrupt ends on its own when viewing on trace...any explanation?

cpeng — Mon, 31 Aug 2020 15:08:50 GMT

Hi no the code runs fine on nRF52833. We don't use any RTOS or SoftDevice, we do use ESB library.

So it's most likely a display bug in Ozone. Thanks for helping.

RE: A software interrupt ends on its own when viewing on trace...any explanation?

haakonsh — Mon, 31 Aug 2020 11:07:55 GMT

That's probably a bug in Ozone. I suggest you ask Segger for help as well.

If it's not a bug in the debugger tool then it indicates a stack corruption which should cause the system to behave erratically, do you observe such symptoms, other than the "extra" main thread?

Are you running any RTOS, SoftDevice, or similar, or are you just running the ESB library?