Search Results

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…

Hi Fraengers, since you opened a ticket in the ticket system your request will be handled there. This thread here will be closed now. Best regards -- AlexD

Hi Fraengers 11: We are not able to reproduce the issue locally. I believe you that what you describe happens in your environment, but since we are not able to reproduce the issue locally there is not much we can do about it. 13: I tried expressions of the form "(<var1> + <var2>) * <number>" locally and they worked like a charm. if you are able to provide a reproducer on an eval board, please open a ticket in our support ticket system. The link can be found in the footer of this message. Best re…

This thread will be closed now as we received your inquiry in parallel via our support system. For future inquiries please do not use multiple channels at once to avoid loss of information between them.

Done

Hi Frank, 10. This is already known and will be fixed in a future release. Best regards -- AlexD

Hi Blunce, since you state that it works after adding the delay loop in the boot loader I assume you are using a low power mode in your system. Could you please disable all low power modes and check again? Background information: Some devices have a built-in debugger awareness which disables features that may interfere with debugging. Low power mode is one of those features. If the debugger is attached before that awareness check takes place, the features will be disabled. If the debugger is att…

Hi again, ekengr, The FreeRTOS topic is not related to the connection topic. For details on how to include the FreeRTOS plug-in please refer to section 7.9.14.10 in the Ozone user's manual. You should not rename the .js-file but adapt the statement in your Ozone project file so it matches the MCU architecture you use. Best regards -- AlexD

Hi Ekengr, please open a support ticket against J-Link in our ticket system. For doing so, please follow the link in my the footer of my post. Best regards -- AlexD

2. I've added that idea to our internal wish list for future improvements. 11. I was still not able to reproduce the issue. I could not find any graph jumping when moving the mouse after zooming via the mouse wheel. It appears to be the case that even in your environment this is not always reproducible. Once you are able to provide a stable reproducer please share that with us.

Hi DavidHC_96, are you able to reproduce the issue with the current release of Ozone, V3.28c? As you describe the issue it might just be the case that your target, once being unleashed, simply runs into a condition that triggers a restart. Eventually you application leaves the code range covered by your break points within the blink of an eye and then restarts. Your system might also simply make use of a watchdog which, after some time, triggers a reset. Of course, this is pure guesswork. With t…

Hi JCP, thanks for coming back to us and glad to see that you are now able to proceed in your work using Ozone. We are not planning to implement such a disassembly based stack unwinding feature. Providing the unwinding information as DWARF information in the ELF file is default for virtually all development tools, GHS being the rare exception. You may contact GHS support and ask for providing that information in a more standardized fashion, though. Best regards -- AlexD

Hi Julian, thank you for your suggestion. I added that to our internal wish-list for future enhancements. Best regards -- AlexD

1. We do not see added value in such a start/stop button. Therefore the feature will not be implemented. 7. The web site for the J-Link Plus (segger.com/products/debug-probes/j-link/models/j-link-plus/) contains a section that advertises that Ozone can be used with that device. This section also contains a small excerpt of Ozone's overall functionality, which includes power graph and instruction trace. Ozone does support all those features, but only with the J-Links that do support them as well.…

Hi Blunce, let me summarize what I took from your description: Ozone is connected to the target, target is running, watched data window is open and populated with a few variables, refresh rate is set to a value other than "Off". Ozone reflects the changes in those variables but sometimes a strange value is displayed which does not fit to the expected values. You see this only under the condition that Ozone connects to the target after the boot loader has executed. If Ozone connects in your delay…

Hi JCP, at first glance I see Warning (107): The program file does not contain DWARF debug information. So apparently your ELF file does not contain debug information. Such debug information is required for stack unwinding. So could you please check if you can create an ELF file which actually contains debug information? Best regards -- AlexD

Hi Fraengers, 7. J-Link EDU does not support the power profiling. This is the feature a J-Link needs to possess in order to work with Ozone's power sampling window. For that a J-Link ultra plus or better is required. I assume that this leads to your power sampling window not being populated with power measurements. If the list is empty the window does not offer scrolling. This would also explain why you do not see the power plot in the Timeline window: No data - nothing to graph. 8. This is inte…

Hi JCP, unfortunately we do not have the eval board you described on stock. since the application is quite simple, can you reproduce that behavior on a different evaluation board or hardware platform? Could you provide an Ozone log you recorded during your debug session? How to create an Ozone log is described in section 8 of the Ozone user's manual. Best regards -- AlexD

Hi JulianR, in case this phenomenon re-appears, feel free to contact us again. Best regards -- AlexD

Hi Blunce, to me the intention of your post is still a bit unclear. Could you please elaborate on what you do, what behavior you expect to see, what behavior you do actually see and where you are looking? Best regards -- AlexD