Search Results

Hi Vlad, we are able to reproduce the issue. A fix will be provided in a future Ozone release. Thanks for notifying us! Best regards -- AlexD

Hi, thank you for providing the details. It appears to be the case that Ozone somehow swallows the upper 32 bits of the registers D16..D31. We will need to have a closer look for reproducing the issue locally. Best regards -- AlexD

Hi Namklak, please use the he context menu of the terminal window for deselect the respective options and close the terminal window. Further details can be found in the description of the terminal window in the Ozone user's manual. Best regards -- AlexD

Hi Vlad, thanks for letting us know. We are not aware of such an issue. Which SVD file are you using? Is it `Cortex-A7.svd` that is coming with Ozone? Are you able to reproduce the issue on an eval board? If so: which one? Could you please provide a J-Link log recorded during a debug session where the issue is reproduced? The register window should show, a in your screenshot, both some registers where the display is correct (i.e. D0..D15) as well as registers where the display is incorrect (i.e.…

Hi AndyR, on which device, exactly do you observe that behavior? We shall try to reproduce locally. Best regards -- AlexD

H Namklak, Ozone does not support sending such control characters to the target. Best regards -- AlexD

Hi AndyR, could you please provide a J-Link log and an Ozone log, both recorded during the same session where the issue is reproduced? How to create an Ozone log is described in chapter 8 of the Ozone user's manual. Creating a J-Link log file is described here: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Best regards -- AlexD

Hi AndyR, please refer to the Ozone user' manual, section 4.6.1, where the hardware requirements for the data sampling window are listed. There you can see that you can control background memory access emulation via the system variable VAR_ALLOW_BMA_EMULATION. Setting this variable correctly should resolve the issue you see. In general, if you see the data sampling window populating with data, you should be able to see that content in the data pane of the time line window. If the data sampling w…

Hi fraengers, thank you. We will try to reproduce and come back to you. This might take a while since all engineers are currently fully booked. Best regards -- AlexD

Hi AndyR, I'm sorry but I am not able to comprehend the point of your inquiry. Could you please describe more clearly what exactly you would like to know or understand? Best regards -- AlexD

Hi Hi Charles_1, good to see you are up and running again. We will consider this thread as closed now. Thanks for sharing this with us and best regards -- AlexD

Hi fraengers, we were able to reproduce the issues from bullet point #1 and #2. We will provide fixes in a future release of Ozone. Best regards -- AlexD

Hi Charles_1 your inquiry is no longer Ozone specific. You are facing general connection issues, which cannot be handled by Ozone team but need to be handled by the J-Link team. If my understanding is correct, you are now able to attach to your device. Is that correct? If not, please open a thread in the J-Link section of this forum. Best regards -- AlexD

Hi Charles_1, just a guess: Does your RTOS enter a power-saving mode when entering the idle thread? In that case, please have a look here: wiki.segger.com/J-Link_Low-power_mode_debugging Best regards -- AlexD

Hi apullin, thanks for your inquiry. Ozone does not provide such a feature. Best regards -- AlexD

Hi keijan2000, as stated before, due to the strong interlinking of Ozone and the ELF file, a snapshot cannot operate properly without the original ELF file. So I kindly suggest to archive the respective ELF file together with the snapshot, allowing you to restore a snapshot also later. An alternative might be you to export the data sampling window contents into a file and use external tooling for the graphing. The resulting text file can easily be used in other tools which can do the graphics di…

Hi Keijan, we are able to reproduce the issue, thanks to your reproducer. Deeper analysis is required which we cannot do right now. A fix, once available, will be provided in a future Ozone version. Best regards -- AlexD

Hi kejian2000, Thanks for your suggestion. Please refer to the user's manual, section 3.11.11.1 Load Snapshot: "In particular, the program file must binary-match the program file at the time the snapshot was saved." The scenario you describe is intentionally not supported. Everything Ozone does is heavily linked to the information in the ELF file. Changing the ELF file w/o letting Ozone know may lead to unpredictable behavior. Best regards -- AlexD

Hi kejian2000, we will try to reproduce and report back here later. Best regards -- AlexD

Hi Keijan2000, thanks for the explanation. I will close this thread now. Best regards -- AlexD