Hi
After updating to latest nRF Connect for VS Code i have an issue debugging my project with Ozone using the "Debug with Ozone"
With previous version the generated jdebug file simply loaded the elf file, but with the new version the code is loaded with Target.LoadMemory which is intended for uses with binary files.
My project is a little bit special in the sense that I have disabled the partition manager and is using device tree definition to control my flash layout. (Custom firmware update framework)
As a result my application is linked to a specific area in flash and not at the default 0x0.
The Target.LoadMemory however is setting download address to 0x0, resulting in my hex file being programmed at address 0x0 rather than the offset specified in the hex file itself.
It would be preferable of you could fetch the "download address" from the hex file rather then hardcoding to 0x0 as it currently seems to do or maybe use other command like Exec.Download(*.hex)
void TargetDownload (void) {
Util.Log ("Downloading Program: d:\xxx\build\zephyr\zephyr.hex");
Target.LoadMemory ("d:\xxx\build\zephyr\zephyr.hex", 0);
}
Best regards
Anders
