Search Results

Hi Sckare, thank you. Please provide infos on which steps exactly I need to perform to reproduce the issue. I assume I shall open the Ozone project, bring the "Global Data" window to the front and then double-click on any of the variables listed there. Correct? Best regards -- AlexD

Hi Sckare, thanks for providing the additional information. On which eval board did you perform your tests? Best regards -- AlexD

Hi Gustavo and happy new year! good to hear you are up and running again. Best regards -- AlexD

Hi sckare and happy new year! now I'm a bit confused. In your initial post you stated that "show definition" and "show declaration" do not work at all. In your last post you state that this works for functions that reside in the same source file. So in your AXF there are symbols where everything works well and other symbols where the "show definition" and "show declaration" do not work? Did you check the functions window working well for symbols where "show definition" and "show declaration" do …

Hi Gustavo, you are referring to a section in the user manual which is treating the Linux installation. The Windows installation is described in section 2.1.1. Uninstalling Ozone under Windows is described in section 2.1.2. Could you please check if your issue with the missing progress indicator persists if you replace the J-Link DLL with the most recent one? You can download the J-Link Installer here: segger.com/downloads/jlink/ When executing the installer you are presented an option to change…

Hi sckare, it appears to be the case that for some symbols Ozone is not capable of identifying the location in the source code. But it appears to be able to find the place where that symbol resides in the target (i.e. the memory address or register), because Ozone is capable of displaying the correct value of that symbol. So... If you right-click onto a function invocation in the source window and select "Show Definition" the expected behavior is that Ozone opens the source file where that calle…

Hi ToBoMi, it might well be the case that the break unit in your target hardware does not trigger on accesses on peripherals. Could you please check the specifications of your device whether data break points on peripheral registers are supported? Best regards -- AlexD

Hi GlebPlekhotko, we are not aware of such issues with the terminal window. Are you able to reproduce the issue on an eval board and provide a reproducer? The reproducer should encompass the ELF file, the Ozone project file and, of course, the information on which eval board this can be reproduced and a step-by-step description of how to reproduce the issue. If you are able to provide that information, please open a ticket in our support ticket system. Best regards -- AlexD

Hi chrishock, we need to be able to reproduce the issue locally for a proper analysis. So a video might not be too helpful here: It would show things on your machine but still not give us information allowing an analysis. During my investigations in particular I looked into the timeline window. I've seen the cursors following the mouse cursor smoothly, and the context menu opening with a delay comparable to the delay when opening a context menu in the finder. Best regards -- AlexD

Hi GlebPlekhotko, thank you for your post. We are aware of that and will provide a fix in one of the next Ozone releases. Best regards -- AlexD

Hi chrishock & akohlsmith, I just tried to reproduce the issue on... ...a MacBookPro (2016), macOS Monterey 12.7.2 ...a MacBookPro (lat 2013), macOS Big Sur 11.7.10 I observe a delay when opening a context menu in Ozone which is in the same range as when opening a context menu on the desktop. So I cannot confirm that such an issue exists. Could you please provide details on how to reproduce? Best regards -- AlexD

Hi! Good to see you're up and running again. Best regards -- AlexD

Hi bpantal, there is no such API call. Best regards -- AlexD

Hi Ewout, you may use the "source files" window (see section 4.19 in the Ozone User's Manual) to locate your file more rapidly, as the contents of that window can be sorted by clicking onto the respective table header as desired. You may also make use of the "quick find" widget (see section 3.11.16 in the Ozone User's Manual) that you can open via [ctrl]-[k]. By typing the first letters of the desired files you can easily reduce the size of that list, allowing you to rapidly narrow down the sear…

Hi Ewout, thank you for your suggestion. Sorting that list is not yet possible. I will add that to our internal list of future improvements. Best regards-- AlexD

Hi tzan, good to hear you are up and running again. Best regards -- AlexD

Hi Tzan, could you please check if the issue persists with the latest version of Ozone? Did you take heed of the suggestions you already received in the old thread you referenced? Probably your device has a boot loader. For debugging devices with a boot loader, please have a look at this WIKI page: wiki.segger.com/Debug_on_a_Target_with_Bootloader. Since you are also intending to debug RAM code, please also have a look at this WIKI page: wiki.segger.com/Ozone_Debug_and_Trace_with_RAM_Functions. …

Hi skam, actually, this should work. I guess, reason you did not see it working, might be that I specified "/" as a separator. Instead it should be ".", as you can see in the documentation of that command, which can be found in section 7.9.17.3 in the Ozone user's manual. Best regards -- AlexD

Hi skam, could you please provide an Ozone log and a J-Link log for the case that the memory window is not updated while the debug session is active? It might be the case the window is actually updated but if the memory content does not change, there will be no change in the display. Creating an Ozone log is described in section 8 of the Ozone user's manual, creating a J-Link log is described here: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Please note that both logs should be recorded in…

Hi skam, for an overview on the different trace types, please also have a look at this WIKI page: wiki.segger.com/General_information_about_tracing In case your chip does not support ETB, this feature is not available to you. Which device are you working on? It is quite likely that ETM is supported by your device, this would allow you to make use of pin tracing, but also requires you to utilize a J-Trace probe. Best regards -- AlexD