Search Results

Thanks Nino, removing the underscore from the environment variable name (i.e. changing "export NORDIC_SDK" to export "NORDICSDK") has solved the problem.

Thanks Nino; unfortunately I am still having the original problem, even after removing $HOME. Perhaps I am doing something wrong; is it possible you could please detail a simple working example? Perhaps I am setting the environment variable in the wrong place (user ".profile" file).

Hi Nino, Please note, I have upgraded to Ozone 2.60l and the problem appears to persist: * The Ozone console says "File not found: $(NORDIC_SDK)/modules/nrfx/mdk/nrf52840.svd" * Opening a Linux console and executing "echo $NORDIC_SDK" prints the expected path. * Manually replacing the $(NORDIC_SDK) in the .jdebug file with the full path works as expected. (The release notes for 2.60l say the problem was fixed in this release.)

Thank you!

Hello, I am having trouble getting environment variable substitution working in my .jdebug file, when trying to substitute into a file path (Lubuntu 18.04, Ozone 2.60k). Perhaps my syntax is incorrect? According to the User Guide, "$(<varname>)" should be correct for Linux and Windows. My .jdebug file has the following line in OnProjectLoad(): Project.AddSvdFile ("$(NORDIC_SDK)/modules/nrfx/mdk/nrf52840.svd"); NORDIC_SDK is an environment variable defined in my user ".profile" file as: export NO…

Thanks Nino, problem appears resolved.

Hi Nino, Thanks for your reply, I will investigate Project.AddPathSubstitute(). Please note I still believe this to be a bug, as I can make the problem recur or go away just by upgrading/downgrading Ozone, between versions v2.54b and v2.56b, loading the same .jdebug file each time.

Hello, When using Ozone v2.56b on Lubuntu, Ozone can't find any source files referenced from the .elf file; looking at the "Source" pane, file paths are missing the root forward-slash. Root forward-slash was displayed in v2.54b, and source files were found correctly. Screenshot attached.

Hi Nino, Solved! -- thanks again for your help. Please note the problem seemed to recur after target reset, so I have copied the same code into AfterTargetReset(); can now reset target and run again successfully through the call to sd_softdevice_enable(). Bluetooth (i.e. SoftDevice) works normally.

Hi Nino, Thanks again; unfortunately I am still having trouble with v2.56b. As I understand it, the Nordic SoftDevice is loaded below the application (link ). If I modify the .jdebug file as described (with SP=0x00000000 and PC=0x00000004), either the CPU halts immediately after "download & reset" at PC=0x000008C8 (no matching source), or if I "reset and run to symbol" and step from beginning of main(), the CPU halts as before at sd_softdevice_enable(). C Source Code (10 lines)

Thank you -- would the fixed Ozone version be v2.56b ?

Hi Nino, Thanks for your reply. Have attached .elf file ("ble_app_blinky" example, Nordic SDK 14.2.0), compiled with SES for ARM v3.34 on Windows.

Using Ozone with a Nordic Semi nRF52840-PDK development board, after updating Ozone from v2.54.2 to v2.56 I am no longer able to debug any Bluetooth examples (S140 SoftDevice). An unexpected "CPU halt" occurs during the call to sd_softdevice_enable(), in the "ble_app_blinky" example supplied as part of SDK 14.2.0: * on either Windows or Linux (Lubuntu) * with either the J-Link built into on the nRF5284-PDK board, or when using a J-Link Plus as an external debugger. The debugging session proceeds…