[SOLVED] saving list of watches with the project

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

  • [SOLVED] saving list of watches with the project

    am i missing something or is there no way for the list of watches to be remembered with the project file?

    it's a PITA if you have a lot of watches setup and then you close the machine, ozone crashes or you restart it , re-open the project and all the watches are gone

  • Hello,

    Thank you for your inquiry.
    Ozone does save them, but only on close. If a crash happens this can of course not e done.
    A crash should not happen though. So the solution would be to find out why your setup is crashing.

    What version of Ozone are you using exactly?
    Do you see the same behaviour with the latest version?
    If yes, is the crash reproducible 100%? If yes, how?

    Best regards,
    Nino
    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.

  • Hello,

    Do you see the same behaviour with the latest version?
    If yes, is the crash reproducible 100%? If yes, how?

    Best regards,
    Nino
    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.

  • The philosophy behind this aspect of Ozone is project orientation. Watches, among other settings which include the ELF file to be used, are part of a project, which is stored on a hard drive in the .jdebug and .user file. The proposed work flow is creating an Ozone project for debugging your application. Applying changes to your code and performing a recompile causes a change in the ELF file which will be noticed by Ozone so Ozone will allow you to download the new ELF file content into the target. This takes place within the context of the project currently open in Ozone and therefore this will not alter any of your project settings, including watches.
    If you open an ELF file directly, e.g. via the file menu, Ozone implicitly creates a new project file, thus replacing the one created beforehand. This is likely the reason why you see changes in your project configuration.
    Does that answer your question?
    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.

  • it answers the question , however it doesn't mean it is an entirely sensible philosophy

    its not uncommon to have different elf files for the same project that you would want to switch between without the rest of the environment changing as it is still the same "thing" just different version of code

    given it takes a split second to delete watches and significantly longer to add them back in I would much rather you didnt try and be clever and guess what the user is trying to do by changing the object file as you will invariably guess wrong.

    even if it is a system preference to not destroy the user environment if the data file changes that would be something