[SOLVED] Ozone Memory View Refresh

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

  • [SOLVED] Ozone Memory View Refresh

    Hi,

    in Ozone v3.10j, when I watch a memory location in the memory view and write to it, the value is only changed on switching to another view once and switch back to the memory view. This is also the case when using Periodic Refresh.

    I have a small video showing the behaviour but connot upload it here because videos are not allowed.

    Can you reproduce this? Do I misunderstand the feature of the memory view with its periodic refresh?

    Cheefs
  • Hi,

    Thank you for your inquiry.
    Do you see the same behaviour in the latest Ozoen version?
    If yes could you provide the footage showing the issue?

    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 you can contact us via our support system: segger.com/ticket/

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

    Thank you for confirmation.

    SEGGER - Nino wrote:

    If yes could you provide the footage showing the issue?
    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 you can contact us via our support system: segger.com/ticket/

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

    sure simply use the ticket form below and reference that ticket to this thread.
    Alternatively any video/image hosting website link works for us too.

    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 you can contact us via our support system: segger.com/ticket/

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

    Thank you for providing the video.
    That you are watching Flash memory here is a crucial hint,
    J-Link caches the Flash content after a download. See here for more information:
    wiki.segger.com/Debugging_self-modifying_code_in_flash
    This leads to the effect you see here, as for the J-Link the Flash memory area was untouched by J-Link so the cache stayed untouched, so no need to update. When you "reopen" the memory window J-Link will do a readback.

    To avoid the caching you can disabled it either completely or for certain memory areas with Command Strings. How to is explained in the J-Link user manual.
    You can either use ExcludeFlashCacheRange or SetAllowFlashCache.


    After the Flash cache is disabled the memory window for the uncached Flash area will also auto update.


    If you do not want to disable the cache to keep the speed benefits while debugging we recommend to use a pointer that you place in RAM that points to the variable in Flash.

    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 you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.