Search Results

Hi sckare, as stated beforehand: We do not support the 3rd party tool chain. However, so far we did not receive any inquiries by our customers that this quite commonly used feature does not work with Keil/Armcc. So we can assume that this tool chain in general is capable of generating ELF files that contain the required information. The root cause is likely to be found inside your build environment. Therefore I strongly recommend to get in touch with your tool chain vendor (or a build manager in…

Hi fefu, you can add a call-back function to the break point that is executed each time the break point is taken. Inside that function you can issue the export command. Triggering a command on a timer base is not possible. Does than answer your question? Best regards -- AlexD

Hi sckare, please find attached a sample project for our Embedded Studio IDE. With this project you can see that Ozone is capable of navigating to the place where an enum is declared. Kindly understand that SEGGER cannot provide support for 3rd party tools. In case of questions concerning your tool-chain please contact the respective vendor. Does that answer your questions? Best regards -- AlexD

Hi Sckare, Finally I found the time to look into this topic. Ozone relies on the debug information provided by the build tool chain in the ELF file. This debug information tells Ozone where exactly a symbol is declared. Here's that information for a symbol from a project where everything is fine: Source Code (8 lines)And here's the corresponding debug information from the ELF file you provided: Source Code (4 lines)As you can see, the information specifying where to find a symbol is missing (i.e…

Hi daubsi, J-Link EDU mini is not supposed to be used for commercial purposes. Therefor the message you observe is displayed. Since you are using Ozone and J-Link EDU mini only for private purposes, this is OK. If your register window is empty your Ozone project most likely does not load the respective SVD file. For details please refer to the section 4.17 in the Ozone user's manual. Does that answer your questions? Best regards -- AlexD

Hi refu, good to see that you already found the answer to your question in the Ozone user's manual. That's what we made the documentation for. Since your single remaining open point is not related to Ozone, please consider posting that inquiry in the J-Link forum. We will consider this thread here as closed now. Best regards and happy debugging -- AlexD

Hi Sckare, thanks! Will any variable do or do I need to use some special variable for that? Regards -- AlexD

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