Hi,
.jdebug files are created with an entry containing an absolute path in it.
Project.AddSvdFile ("C:/Program Files/SEGGER/Ozone V3.10j/Config/CPU/Cortex-M4F.svd");
When I now install Ozone v3.20a and remove v3.10j and then open the .jdebug file in the newer Ozone, the path is invalid but I do not get an error message.
When I then save the file with File -> Save project as... the path is not updated, so it remains invalid.
Maybe it is better to use a runtime variable to determine the position of the ozone executable and go from there.
Using paths relative to the .jdebug file when it comes to the debugee exe file, might also be a good idea. That way, a debugging project file could work on different computers.
Cheers
.jdebug files are created with an entry containing an absolute path in it.
Project.AddSvdFile ("C:/Program Files/SEGGER/Ozone V3.10j/Config/CPU/Cortex-M4F.svd");
When I now install Ozone v3.20a and remove v3.10j and then open the .jdebug file in the newer Ozone, the path is invalid but I do not get an error message.
When I then save the file with File -> Save project as... the path is not updated, so it remains invalid.
Maybe it is better to use a runtime variable to determine the position of the ozone executable and go from there.
Using paths relative to the .jdebug file when it comes to the debugee exe file, might also be a good idea. That way, a debugging project file could work on different computers.
Cheers