[ABANDONED] Reloading and programming in the background

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [ABANDONED] Reloading and programming in the background

    Hello,

    Some issues are prone to require (a lot of) trial and error to fix. Such cases typically follows the flow:

    Change code -> compile -> program elf file in Ozone

    To program the elf file one needs to bring Ozone to the foreground for the dialog with the text "The program has been modified by another application. Do you want to reload it?" to show. In many cases I check "do not show again" to avoid the dialog.

    Is there any way to let the reloading (and programming) happen in the background avoiding alt+tab'ing to the Ozone Window? This would speed up the development flow. A tool like Autohotkey might be usable, but not ideal (I would like to avoid having too many dependencies in the toolchain).

    Windows 10 / Ozone 3.34 / stm32u585 / J-Trace

    Best regards,

    Rune
  • Hi Rune,

    Ozone does not provide such a functionality and we do not see a big benefit in implementing such a feature. Ozone is a debugger and if you switch to Ozone it can be assumed that you intend debugging the firmware. For that use case Ozone behaves well.

    If you just want to download the ELF file into the flash and start the application stand-alone, I am sure that you can use your J-Trace and the tools coming with it plus some scripting to achieve that. In that case please open a new thread in the J-Link forum.

    Does that answer your question?

    Best regards
    -- AlexD
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hi AlexD,

    I agree that the functionality doesn't really fit well with Ozone either. I was hoping that the all-knowing Ozone user base might provide some insights to alternative solutions.

    For me at least, I grow impatient while waiting for the Ozone flash programming to complete (typically 20 secs on our target). I would rather spend the time in my IDE and let the programming happen in the background after a build is complete.

    Hopefully, I will think of something during the summer holiday :)

    Best regards,

    Rune
  • Hi rals,
    what about writing a little script that does the flashing by means of the tooling you received with your J-Link/J-Trace and invoke that script from within your IDE? Assuming your IDE supports customizable buttons you the flashing will be triggered by a single mouse click.
    Best regards
    -- AlexD
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.