Segger Ozone causes a soft device error when trying to debug or reset during debugging

RE: Segger Ozone causes a soft device error when trying to debug or reset during debugging

Andrew — Thu, 11 Feb 2021 16:38:26 GMT

I found that I also needed to adjust PC = Elf.GetEntryPointPC(); to PC = Target.ReadU32(VectorTableAddr + 4);

This thread plus this wiki entry on Segger site helped solved the problem properly for me.

wiki.segger.com/Ozone_detects_wrong_application_entry_point

RE: Segger Ozone causes a soft device error when trying to debug or reset during debugging

Bertram — Thu, 08 Aug 2019 14:39:21 GMT

Thanks for that answer.. solved the problem for me.

I am using FreeRTOS and it hardfaulted shortly into the SVC handler triggered by FreeRTOS function vPortStartFirstTask() during RTOS startup. Until i applied this solution.

Just for those not fluent in Ozone (like me who had to research where and what the line "VectorTableAddr = Elf.GetBaseAddr()" is about), its the ozone project .jdebug file. It contains a C like script program, it is a bunch of functions that is run on different events in Ozone.

Search replace "VectorTableAddr = Elf.GetBaseAddr();" to "VectorTableAddr = 0;" - restart Ozone and you should be good to go.

RE: Segger Ozone causes a soft device error when trying to debug or reset during debugging

Amanda Hsieh — Mon, 20 May 2019 07:06:04 GMT

Hi,

It is great to hear the root cause is found.

Cheers,

Amanda

RE: Segger Ozone causes a soft device error when trying to debug or reset during debugging

dlip — Sat, 18 May 2019 23:44:56 GMT

Root issue is that ozone is starting execution at the reset_handler of the app rather than the looking to the vector table at the base of flash and running whatever it points to (i.e. reset code for sd). Simplest fix is to change the line VectorTableAddr = Elf.GetBaseAddr() to VectorTableAddr = 0 in both AfterTargetReset and AfterTargetLoad.