Search Results

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

Hi Keijam2000, thank you for letting us know. We are able to reproduce and will provide a fix in a future release. Just out of curiosity: Why do you save the same snapshot multiple times? Best regards -- AlexD

Hi fraengers, as stated before, we need to be able to reproduce the issue locally. Could you please provide a reproducer, as described in my previous post? Best regards -- AlexD

Hi kejian2000, Could you please provide a reproducer on an eval board? We'd require the ELF file, the Ozone project, and detailed instructions on what to do to reproduce the issue on that very board. Best regards -- AlexD

Hi Ewout, performance issues on Mac architecture machines are not known to us. On our test machines Ozone executes smoothly. Since you state that loading an ELF file is slow, can you provide an ELF file where that issue is seen and the respective Ozone project file? So I can measure the time consumed for loading the ELF file locally and perform a comparison across our test machines? Best regards -- AlexD

Hi grb212, Do you use the latest version of Ozone? Are you able to reproduce the issue on Ozone V3.36? If so, could you please provide a reproducer on an eval board? We'd require the ELF file, the Ozone project, and detailed instructions on what to do to reproduce the issue on that very board. Best regards -- AlexD

Hi, Not sure why SystemView should be too much overhead. In general it is recommended the tools that fit a given task best. In the case you describe, SystemView appears to be a very good solution. I just tried: Zooming on the Y-axis of the code pane works as a charm using shift-mouse wheel. I cannot reproduce the issue you observe, but I also cannot see that you are doing zooming in the Y-axis in your screen recording. Power sampling is disabled in the power sampling window. Disabling the power …

Hi Fraengers, in the code pane of the timeline window ISRs are displayed in special way, so they can be identified quite easily (different color, rounded corner). In a long trace, however, the view is likely to be too compressed for directly seeing all ISRs at the same time. Of course, searching the trace window might also help in navigating the instruction trace. What additional live information would you expect to see? Best regards -- AlexD

Hi Fraengers, currently this is not possible. Increasing the the size of the trace buffer in PC memory and thus increasing the amount of trace information available in Ozone is already on our to-do list. The code pane in timeline window will still only be updated once the target is halted, even with this change being available. I cannot comment on when this feature will be released. Does that answer your question? Best regards -- AlexD

Hi Fraengers, those questions are related to J-Link, not Ozone. Therefore I move this thread to the J-Link forum. Best regards -- AlexD

Hi, please raise a ticket in our support ticket system. The link can be found in my signature below. Best regards -- AlexD

Hi rals, what about writing a little script that does the flashing by means of the tooling you received with your J-Link/J-Trace and invoke that script from within your IDE? Assuming your IDE supports customizable buttons you the flashing will be triggered by a single mouse click. Best regards -- AlexD

Hi SyamK, Which Semihosting service do you use? I assume, this is ReadC(). Is that correct? ReadC() returns a character. If you configure Ozone such that a dialog opens to enter a character, you need to enter a character and then click on the "OK" button. As a result, the character will be sent to the target. If you do not enter a character but click onto the "OK" button directly, an error is raised. I assume that this error results in a NULL character arriving on the target. Hitting the enter k…

Hi Rune, Ozone does not provide such a functionality and we do not see a big benefit in implementing such a feature. Ozone is a debugger and if you switch to Ozone it can be assumed that you intend debugging the firmware. For that use case Ozone behaves well. If you just want to download the ELF file into the flash and start the application stand-alone, I am sure that you can use your J-Trace and the tools coming with it plus some scripting to achieve that. In that case please open a new thread …

Hi Sam, the FreeRTOS plugin for Cortex M33 was not tested on the Cortex M4. So we cannot promise that everything will work as expected and intended. But feel free to share your experience here. Best regards -- AlexD

Hi Glenn, this is a general setup issue which is not related to Ozone. Therefore I will move this thread to the J-Link section in this forum. The colleagues should be able to provide further support. @J-Link team: Could you please investigate what is going on here? Best regards -- AlexD