Short Story (Steps to reproduce):
- Open blinky example for RP2040-Pico in Segger-Embedded-Studio.
- Build the project
- Click "Debug/Debug With Ozone (Alt F5)"
- When Ozone opens, start debug session
- Get a Hardfault at 0x00000000 (screenshot is attached)

This is all done using standard Raspberry Pi Pico Dev-Board, no custom hardware is used yet.

Long Story (Background):
After many years of development with STM32 micros (using Eclipse and Ozone/J-Link as my toolchain), I need to start a project with Raspberry Pi RP2040.
For a quick start, I used Visual Studio Code with the integrated debugger, the Pico-SDK and the Pico-Debug-Probe.
This worked well, besides the limited functionality of the debugger, compared to Ozone.

So after the initial development I wanted to switch to Ozone and J-Link.
But after connecting the J-Link to the Pi-Pico (as shown in the Segger Knowledgebase: SWCLK, SWDIO, GND, Vtarget) and loading the elf file into Ozone a Hardfault occured immediatly after starting debugging.
Side note: The file which was flashed by Ozone just runs fine, after disconnecting.

To verify the hardware and make sure there is nothing wrong with my software, I downloaded the Eval version of Segger Embedded Studio.
The provided blinky example worked out of the box.
I could build the project and debug it inside Segger Embedded Studio, so all used hardware must be fine.
But as soon as I clicked on Debug with Ozone and started the debug session the Hardfault occured.

So it seems, that debugging works with SES, but not with Ozone.

Used software versions are:
Ozone 3.38d
J-Link 8.20
SES 8.22a

I also tried this on two different PC's, they behaved exactly the same.
I can not see what could be wrong on my side.
Any hints on this would be really appreciated.

Best regards,
Martin

Hi Alex

Thanks for the reply.

No, there is no bootloader involved.
As i wrote at the beginning of my first post, i stripped the problem down to the Blinky example delivered with SES.

If the Ozone project is not set-up correctly, then how do i get a correct set-up?

SES does not seem to produce a correct Ozone setup, as mentioned.

Doing the set-up with the Ozone project wizard also does not produce a correct setup.

As mentioned, there is currently no user specific code involved, it is all just the blinky example delivered with SES.

Is there a known good Ozone project configuration which does not depend on SES?

I meanwhile was able to try debugging using the J-Trace Pro of my customer, also the same problem.
So i really think we can rule out the hardware.


Best regards,
Martin

Hi Alex,

sorry, i had a brain block.
When you mentioned a bootloader i only thought of a custom one, not of a builtin ROM-Bootloader.

Of course you were right. In the knowledge base article you linked the "secret" is mentioned at the very bottom.

For reference, if anybody will stumble about this in the future, i will repeat the important sentence here:

Simply leave the functions AfterTargetDownload() and AfterTargetReset() empty (but not commented out!).

This did the trick for me.


Why the Ozone project wizard does not add this important part does escape me.


Thanks for the help.
Best regards,
Martin