Search Results

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

If I get you right, the growing into the negative range is reproducible on your desk. Could you please provide a reproducer project on an eval board for that? We'd require the ELF file, the Ozone project and whatever else is required to run the reproducer plus a step-by-step instruction on how to reproduce the behavior. You may open a support ticket for providing the reproducer. The link for opening a ticket can be found below. 22. If you modify an expression at runtime Ozone needs to dump the d…

Hi Tzan, please refer to the following WIKI articles: - wiki.segger.com/Debug_on_a_Target_with_Bootloader - wiki.segger.com/Ozone_detects_wrong_application_entry_point - wiki.segger.com/i.MXRT117x (please have a closer look at the section "Reset" in that article) It is rather likely that IAR IDE does some magic your Ozone project does not yet do. Probably PC/SP are set differently. Does that solve your issue? Best regards -- AlexD

As stated before: The wrong calculation of float expressions will be fixed in a subsequent release. As stated before: We will not add aliases for the legend since Ozone is designed to display what is there. As stated before: Y-axis zoom is on the list of future improvements. If I get it right this will solve quite a few of the things you observe with Y-Axis ranging. What's wrong with Y-Axis adapting to values growing into the negative? This is intended. Same goes for the connection between data …

We won't implement aliases for expressions. Ozone is intended to display what is there, and if there are long expressions they will be displayed. You may instrument your code to provide the content of a long expression in a short-named symbol, and then use that symbol in Ozone. Value boxes may overlap time markers, that is correct. With Auto Fit Height you usually have sufficient margin on the top for displaying the markers where no value box is displayed. I know that you'd love to see a Y-axis …

Hi fraengers, please have a look at the latest release (V3.28e) which offers a few improvements in the area of the timeline window. Best regards -- AlexD

No. Ozone is intended to be used with SEGGER probes. Currently we are investigating a GDB server support but I cannot comment on if at all and if yes when this might become available.

Hi Fraengers, thank you for your suggestions. Please understand that I will not comment on the topics that were already discussed in the other threads. 14. Thank you for notifying us. This will be fixed. 15. I was able to reproduce that. This will be fixed in a future release. 16. When handling devices with low power mode enabled, special care must be taken. Please refer to this WIKI article: wiki.segger.com/UM08001_J-Link…Guide#Low_Power_Debugging 17. This is already addressed and will be impro…

Hi Julien, you're very welcome. Best regards -- AlexD

Hi Julien please switch to the current version of Ozone, i.e. 3.28d. A fix targeting potential flaws in call stack reconstruction was released lately, please refer to the release notes for details. In general we recommend always using the latest Ozone version in order to make benefit of the improvements and corrections SEGGER provides. Does that solve your problem? Best regards -- AlexD

Hi Ouble, your screenshot shows only a short part of the console window. So at this point in time you can expect only guesswork to be done. Did you load an ELF file in your Ozone project? Does your ELF file contain debug information? What happens if you attempt to break the target? Best regards -- AlexD

You're very welcome. I'll close this thread now.

Hi Vadim B, you're not really doing anything wrong. However, your usage of the Target.LoadMemoryMap() command in the if/else construct is beyond mainstream usage. This construct leads to Target.LoadMemoryMap() being present twice in your OnProjectLoad() function. And this is what the routine, that finally leads to the warning "Project command specified twice" being printed, actually checks for: The presence of multiple such statements. In particular, the routine does not check whether the comman…

Hi Vadim B, thanks for notifying us. We will provide a fix with a future Ozone version. Best regards -- AlexD

Hi relepage, it looks like your device suffered a severe crash. The hardfault screen does not show register content. So it might even be the case that the connection J-Link<->Target was lost due to that crash. In general, the trace should reflect the code execution that led to the exception. However, if due to the crash, trace data was lost, this might not be the case. We do not know the reason for the crash. It might be the case that the crash is caused by a stack corruption. In that case the c…