Acquiring a Code Profile with Ozone

[brolive]

Dear all,

I'm new to Ozone and hope that you will forgive the simplicity of my question.

I'm trying to acquire a simple trace (Code Profile) of the blinky example with Ozone. To this purpose I have followed this document: J-Link User Guide and some other tutorials. I used the Ozone Project Wizard to setup it up, selecting the corresponding .elf file of this example under C:\Storage\nRF5_SDK_15.3.0\examples\periphera\blinky\pca10040\s132\ses\Output\Release\Exe\blinky_pca10040_s132.elf. Trouble is, Ozone can't find my main file and I therefore am not able to run the example. I get the following message:

Project warning (2071): file not found: C:\Storage\nRF5_SDK_15.3.0\examples\periphera\blinky\pca10040\s132\ses\Output\Release\Exe\blinky_pca10040_s132.elf.

I am using the following setup:

• nrf52832 DevKit with PCA10040
• J-Link EDU
• NRF5 SDK 15.3.0
• SES 4.16

1. What do I need to change in order to be able to display and run this example in Ozone?
2. Where should my .jdebug file be relative to the .elf file?
3. How should my .jdebug look like?

Thank you for your help.

Oliver

[bjorn-spockeli]

Hi Oliver, 

I do not know if its a copy-paste error, but it looks like the path to the .elf file is incorrect 

brolive said:

C:\Storage\nRF5_SDK_15.3.0\examples\periphera\blinky\pca10040\s132\ses\Output\Release\Exe\blinky_pca10040_s132.elf.

it should be peripheral and not periphera. 

Could you check if this is the cause of the error?

Best regards

Bjørn

[brolive]

Hi Bjørn

I just double-checked it. The spelling mistake is just a copy-paste thing here on the forum. The actual path is with:

.../examples/peripheral/blinky/...

This unfortunately didn't solve it.

Cheers,
Oliver

[bjorn-spockeli]

Ok, just wanted to check. 

I did the same thing as you, i.e. used the Ozone Project Wizard to select the .elf file in the

nRF5_SDK\nRF5_SDK_15.3.0_59ac345\examples\peripheral\blinky\pca10040\s132\ses\Output\Release\Exe

folder and this should work just fine. 

Are you sure that this isnt a path issue? I assume that you have verified that the .elf file is located in the folder you're pointing to?

Best regards

Bjørn

[brolive]

Alright I got a fesh SDK, unpacked it on my local drive instead of on the server-drive and this time it worked. It looks like it is in deed a path issue. Since my system runs in on a server, running ozone on that cluster storage didn't work.

Now it is all good. Thank you for your help!

Best

Oliver