[SOLVED] How to set VAR_BREAK_AT_THIS_SYMBOL in the jdebug

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

  • [SOLVED] How to set VAR_BREAK_AT_THIS_SYMBOL in the jdebug

    I have the same basic question as found in this thread:

    forum.segger.com/index.php/Thr…S-SYMBOL-value-by-script/

    How should I set VAR_BREAK_AT_THIS_SYMBOL in the jdebug project file?

    When I have started up the debugging process, the following works in the console.

    Edit.SysVar (VAR_BREAK_AT_THIS_SYMBOL, main_dev);



    The old jlink script spec says that the type of the symbol should be an integer.

    I have tried setting the variable with hopes that it would be overwritten.

    unsigned int main_dev = 0;

    Then I get:

    String argument expected in command "EditSysVar": 0x0 (0)

    I would really appreciate better documentation :). There is not a string type specified anywhere.

    When define the variable as requested, I get the following.

    char* main_dev = "main_dev";

    Error (77): Script interpretation failure: expected a base type at line 23, column 27.

    The base types as documented include 'char'.

    Please instruct me on how to set VAR_BREAK_AT_THIS_SYMBOL in the jdebug-file.

    Thank you for the help!
  • Hello,

    Thank you for your inquiry.
    Which Ozone version are you currently using?
    In Ozone V3.10c there was a fix related to the break symbol.
    Could you give V3.10c a try and see if the behaviour improves?

    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.
  • From my understanding, when OnProjectLoad is run, the following should work after File.Load, because the symbols should be loaded.

    Edit.SysVar (VAR_BREAK_AT_THIS_SYMBOL, main_dev);


    What am I missing?
  • Hello,

    Your approach is correct. It appears that the bug in Ozone was not fixed for all cases. This should be the case with the next Ozone release V3.10d.
    Sorry for any inconveniences caused.

    To stay up to date with Ozone releases you can subscribe here:
    segger.com/notification/subscribe.php?prodid=178,7

    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 Brian,

    Great to hear that you are up and running again.
    We will consider this thread as solved now.

    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.