Search Results

Fabian, Thanks for your response. I suppose I could have phrased my request a bit better, but yes, my intent was the option of a manual reset that was mutually exclusive with the existing automatic reset of counters. I agree, though, that maintaining the counters on a debug session basis would fulfill the end result I was hoping for. Thanks for adding it to the list.

Hello, I'd like to request the option of a manual reset of the execution counters for the source and code profile windows. Per the manual, the counters reset automatically when the probe detects a reset (which is generally fine). However, I'm developing and testing a bootloader where resets are a normal part of the process and the execution counters are lost periodically when I'm trying to analyze the code coverage. I would like to be able to have the counters clear when Ozone writes the flash (…

Nino, I'm glad to hear that its already on the to-do list. Thanks!

Nino, Thanks for your response and the excellent explanation though I can see where saying the instruction coverage is "0/1" is counter-intuitive since it seems to imply that the instruction was not executed at all. The source counter indication of the split green/yellow makes perfect sense since both paths haven't been taken, but in the case of the instruction coverage I feel like you be would safe saying "1/1" since the instructions that follow (in the event that the branch occurred) still hav…

Nino, I checked around to other branching operations and it seems to happen in other compare/branching operations. See in the attached image where the Source Window seems to correctly indicate that execution has branched to 0x00400F08, and so does the Code Profiler with the exception of the branch instruction itself which it claims to not have executed. The same code and disassembly is shown in the Code Profile as in the Source window (and sorted in the same order this time). Thanks.

Hello, Are there any plans to provide a dark theme for Ozone? I've very much enjoying using it from a functional standpoint, but, for me personally, it's a struggle to look at for extended periods of time. Either the option to select background colors and text colors in a dialog (like "Preferences..." or just an *.ini file that gets read at start up, etc. would be appreciated. I apologize if this has been requested already, but I did search the forum prior to asking. Thanks.

Nino, I'm using a Atmel/Microchip ATSAMV71Q21B with the Cortex-M J-Trace Pro. I'd have to check the other conditional branches, but I did check to see if there were other IT blocks with a similar behavior and I did find at least one more (see attachments). Thanks for your help.

Hello, I'm new to Ozone and am working through a code coverage exercise on a project. I noticed what seems like conflicting indication of instruction execution between the Code Profile window and the source/disassembly window (see attachments). Based on my reading of the manual, the fetch/execution counts, and the green/orange execution profile color code it would seem to indicate that the instruction at 0x402432 is ALWAYS fetched and executed in the Source window, but the Code Profile window in…