[ABANDONED] Ozone: Target.WriteU32 bug

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

  • [ABANDONED] Ozone: Target.WriteU32 bug

    Hi
    I have a strange bug in Ozone (2.56s). I do this:

    Target.WriteU32(0x506000e4,0x90000);

    The console shows:

    Target.WriteU32 (-2147483648, 0x00090000);

    Anyone has an idea what is wrong?

    Addendum:

    Target.WriteU32(0x506000e0,0x90000);
    => Console
    Target.WriteU32 (506000, 0x00090000);

    This is bizar as 0x506000c0 works!

    Same with decimal:
    Target.SetReg("R0",1348468964);
    Target.WriteU32(1348468964,0x90000);
    =>
    Target.SetReg ("R0", 0x506000E4);
    Target.WriteU32 (-2147483648, 0x00090000);

    The post was edited 1 time, last by 42BS ().

  • It seems the last address byte is somehow "ignoreded":


    Target.WriteU32(0xdc,0x90000);
    Target.WriteU32(0xe0,0x90000);
    Target.WriteU32(0xe4,0x90000);
    Target.WriteU32(0xe8,0x90000);
    Target.WriteU32(0xec,0x90000);

    => Console
    Target.WriteU32 (000000DC, 0x00090000);
    Target.WriteU32 (0, 0x00090000);
    Target.WriteU32 (0, 0x00090000);
    Target.WriteU32 (0, 0x00090000);
    Target.WriteU32 (000000EC, 0x00090000);


    But I just see: It is only a "console" problem. The data is (at least for the above addresses) written to the memory.
  • Hello,

    Thank you for your inquiry.
    Such an issue is not known to us.
    We tried to reproduce it with the 64-bit version on Win 7 but everything was working as expected.
    What OS are you running Ozone on?
    Does this issue happen with only that target device?
    Does it happen only with one specific debug project?
    Could you create a generic project for your target device and see if the behavior changes?

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support system can be used as well: segger.com/ticket/
  • Hello,

    Quick update. We were able to reproduce the issue when calling the API function in the Ozone Projekt file.
    Under certain circumstances the reported issue could happen. It will be fixed with the next Ozone release.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support system can be used as well: segger.com/ticket/
  • Hello,

    Great to hear that you are up and running again.

    42BS wrote:

    Another notes or feature requests:
    - Access to environmet variables
    - #include-ing parts of a script
    Could you elaborate on these two points?
    Which environment variables are you referring to and where do you want to access them from?
    What do you mean with #including and what do you mean by "parts" of a script?

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support system can be used as well: segger.com/ticket/