[SOLVED] [bug] Ozone 3.10g: display format of the variable

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

  • [SOLVED] [bug] Ozone 3.10g: display format of the variable

    Hello,

    The display format of a variable named 'value' can not be changed, at least in Local Data window.

    Steps to reproduce:

    1. Add the following function to your project, add a call to the function.

    Source Code

    1. #include <stdint.h>
    2. uint32_t f (uint32_t const * const p)
    3. {
    4. uint32_t value = *p;
    5. return value;
    6. }

    2. Compile, run on an ARM target.

    3. Step into the function.

    4. In Local Data window:

    -- select variable 'value', press 2, 3, 4
    -- right click -> Display As -> Hex, Decimal, Binary

    Expected behaviour:

    display format of the variable 'value' should change accordingly.

    Actual behaviour:

    display format of the variable 'value' does not change.


    Host: xubuntu 18.something
    Target: nRF52 DK
    Compiler: arm-none-eabi-gcc 9.2.1
    Compiler options: -O0 -g3
    Ozone: V3.10g


    Kind regards
    Vadim
  • Hello,

    Thank you for your inquiry.
    We tried to reproduce the reported behaviour with the code snipped but the value display changed as expected.
    The test was conducted on a STM32F4 and Ubuntu 18 LTS.

    Could you provide an example project with which the behaviour is reproducible with?
    Do you see the same behaviour on other Linux distributions?

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

    Please understand that without a reproducer we can't investigate this. Could you provide an example project? It does not have to be exactly your project that is your protected IP. Any example project with which this behaviour is reproducible with would work for us.

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

    I can reproduce it with NordicSemi SDK v16 on nRF52 DK board. It has on-board Segger J-Link.


    The project I used is nRF5_SDK_16.0.0/examples/ble_peripheral/ble_app_blinky

    Makefile: nRF5_SDK_16.0.0/examples/ble_peripheral/ble_app_blinky/pca10040/s132/armgcc/Makefile

    I've changed the optimisation flags there to OPT = -O0 -g3 and ran make from the directory where the Makefile is.

    I have also noticed that value is not the only affected variable. If a variable is named pc, or lr, or r0, it is also not possible to change the variable's display format, see attached picture. The variable p can be displayed in any format (binary, decimal, hex), the variable value is defaulted to decimal, and the variable pc is hex.

    Kind regards,
    Vadim
    Images
    • ozone-value.png

      88.97 kB, 1,685×464, viewed 388 times
  • Hello Vadim,

    Thank you for providing an example.
    The behaviour is reproducible for us with the pc, lr and r0 variable which will be fixed.
    But variable value is working as expected in locals view.

    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.
  • Hi Vadim,

    Great to hear that you are up and running again.
    This thread will be treated 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.