Hi

I'm seeing something odd in Ozone...

If I create a new project (without specifying JLINK settings )and load an elf file, Ozone is happy to download that to my target, provided the connected JLINK has already been configured for the target.

If I then add those JLINK target settings to the project (see below), downloading to the target immediately produces a HardFault exception. What could be the reason for this?

Target setitngs:
Project.SetDevice ("MK60FN1M0xxx15");
Project.SetHostIF ("USB", "");
Project.SetTargetIF ("SWD");
Project.SetTIFSpeed ("200 kHz");

HardException details
The target stopped in HardFault exception state.


Reason: Undefined instruction executed at 0x000001B0.


The initial UsageFault exception was escalated to HardFault, because its handler was not enabled or a fault occurred within the handler.




Many thanks
David

Hi Fabian -thanks for responding so quickly!

Yes, in fact it is the bootloader elf that I am debugging.

I've applied the recommended tweak to the setting of PC and SP as per wiki.segger.com/Debug_on_a_Target_with_Bootloader and it's now working, so thank you!

I notice that the difference that this tweak has made has only been to set the PC to a different value than is obtained by the 'default' method (i.e. by fetching PC and SP locations from the elf file vector table). It appears to be that the default 'vector table' method is obtaining PC value for 'main', whereas the bootloader needs to run the startup asm beforehand. I assume this is the reason why this 'manual' adjustment of PC on reset is necessary in the case of bootloader code- is this right?

Many thanks

David