Search Results
Search results 1-20 of 170.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
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 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 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 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 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 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