Search Results

Hi skam, thank you for your suggestion to add support for scaling in the range less than 1. I'll bring that up in our next internal meeting. I cannot tell if or when this will be implemented, though. Best regards -- AlexD

Hi skam, this is intended. Hex numbers are normally interpreted as unsigned, however in the graph window numbers are considered being signed. Best regards -- AlexD

Hi Skam, often there are multiple ways to achieve a desired effect. Since your peripheral registers are memory mapped they may be accessed like memory. That's why reading the memory location works as well. The script you create is less portable, though. While the same register may exist in another MCU it might reside at a different address. By using the path name in Target.GetReg() allows your script to execute fine on another MCU, while accessing the memory address may cause tedious update of c…

Hi skam, the memory window does not update its content while the target is halted. This is intended. Automatic update only takes place when the CPU is running. Best regards -- AlexD

Hi skam, ETB is a hardware feature. The respective trace buffer is a buffer that is written by HW only. It is also a dedicated buffer and you cannot use another buffer, e.g. a RAM area, such as the RTT buffer. RTT is a software feature. You can do some software tracing, but not on instruction level. Systemview makes sophisticated use of that feature. General information on tracing, including descriptions of multiple trace types, can be found here: wiki.segger.com/J-Trace#General_information_abou…

Hi Skam, please be a bit more specific. At which occasion do you expect the refresh to occur? Best regards -- AlexD

Hi Skam, nope, that's not possible. However, you might try the scaling feature: Right click into the legend, onto the respective graph, and chose a suitable scaling factor. Maybe that's close to what you intended? Best regards -- AlexD

Hi Skam, I guess, Target.GetReg() should also work for peripheral registers. It might be that you need to specify the full "path" for your register, though, i.e. something like "Peripherals/GPIO/GPIOA/MODER". Could you please check if that works for you? Best regards -- AlexD

Hi skam, as long as the peripheral register is memory mapped and accessible, you can add a term such as *(unsigned int*)(0x080000000) to your Data Sampling window. Of course, you need to replace 0x080000000 with the address of your peripheral register. This should do the trick. Best regards -- AlexD

Hi Rahul, you already opened a ticket in our ticket system with the same question. Your request in the ticket system has already been answered. Please use only a single channel for communicating with us. Best regards -- AlexD

Hi Eggplant886, right now, Ozone does not support loading multiple ELF files. This is on our internal wish-list but I cannot comment on when this will be released. Best regards -- AlexD

Hi Siwei, normally it should be sufficient to rename the XML file to SVD. SVD file format is explained here: keil.com/pack/doc/CMSIS/SVD/html/svd_Format_pg.html. If the file NXP provided doe not adhere to that format you may... ...create a tool translating the NXP format to the SVD format ...create your own SVD file, taking one of the SVD files for peripherals coming with Ozone as a template. Does that answer your question? Best regards -- AlexD P.S.: In future, please do not use multiple channe…

Hi Jan_vi, when testing Ozone on Ubuntu I use the following commands: Source Code (2 lines) On a blank machine J-Link software should be installed before the 1st debug session is started with Ozone. If this is not the case the J-Link/J-Trace may not be found. Does that answer your question? Best regards -- AlexD

Hi rflmota, right now we are aware of very few customers reporting a poor performance on MacOS, however we are not able to reproduce that in our labs. The overlapping text display in the context menu appears to be caused by MacOS having become incompatible with the QT version we are using and so far we did not find a way to work around that. We expect that being resolved once we moved to a later QT version. Unfortunately at this point in time we cannot comment on when this will be released. Does…

Hi pbl, here is an excerpt of section 1.1 of the Ozone user's manual: Quote: “Ozone is a source-level debugger for embedded software applications written in C/C++ and running on embedded targets. ” As you can see, rust is not yet intended to be supported by Ozone. We have adding rust support on our internal wish list but at this point in time I cannot comment on when this will be available. Does that answer your question? Best regards -- AlexD

Hi rsg, for processing your request for support additional information is required. Could you please share your Ozone project file with us? Best regards-- AlexD

Hi juliengros. the folder containing the RTOS plugins is part of the Ozone application package. It can be found in Contents/MacOS/Plugins/OS. The view menu does not show an entry for the RTOS until an RTOS plug-in is loaded (see section 6.3.2 of the Ozone user's manual). Does that answer your question? Best regards -- AlexD

Hi LXW, V3.22 is rather old. Please try again with Ozone V3.28e. In case the problem persists, please provide a screenshot so we can easier understand your question. Best regards -- AlexD

Hi Fraengers, 22: This is not a feature we assume as being widely requested in the community of our customers. Therefore we will not pursue this idea any further. Apparently you are in particular interested in quite a few non-mainstream features and feel aware on how they could be implemented. Therefore you may be interested in the J-Link SDK: This allows you to integrate J-Link into your own application. For a 1st impression please refer to this site: segger.com/products/debug-prob…nk/technolog…

Hi Hugo, Good to see that you're up and running again. this is actually documented in the user's manual, admittedly not too clearly. The option is described in the section for the memory window's context menu. We'll add a note to the section describing the toolbar. Best regards -- AlexD