Thursday, September 21st 2017, 8:47am UTC+2

You are not logged in.

  • Login
  • Register

Search results

Search results 1-4 of 4.

Wednesday, June 14th 2017, 2:24am

Author: danngreen

Is this a bug of OZone? [bit field handling ]

Quoted from "SEGGER - Niklas" Quoted Ozone treats a int32_t array inside a struct as an array of 8-byte integers (long long), but it should be 4-byte integers. This makes the variable display of structs incorrect. This will be fixed in the next version of Ozone. I will update this thread once the new version is available. Best regards, Niklas Excellent, this test code now works in v2.40c. Thank you for fixing this so quickly! Masa, I apologize for hi-jacking your thread! I hope a fix for the bi...

Friday, June 9th 2017, 7:35pm

Author: danngreen

Is this a bug of OZone? [bit field handling ]

I can confirm this as well, and in addition, I found a related bug. Ozone treats a int32_t array inside a struct as an array of 8-byte integers (long long), but it should be 4-byte integers. This makes the variable display of structs incorrect. It does not seem to happen to uint32_t arrays inside structs. I am compiling with arm-none-eabi-gcc. I saw this in Ozone 2.32 and it persists in 2.40b In the attached screenshot, you can clearly see the error: In the variable watch window, the elements de...

Wednesday, June 22nd 2016, 7:23pm

Author: danngreen

[Solved] Ozone is assigning TRACE pins when resuming from breakpoints

Ah yes, closing the Code Profile window prevents Ozone from initiating Trace when it resumes from a breakpoint. Thank you, it's working well now. And I appreciate the distinction between Trade and SWO modes. Cheers, Dan

Wednesday, June 22nd 2016, 12:14am

Author: danngreen

[Solved] Ozone is assigning TRACE pins when resuming from breakpoints

I'm using the J-Trace for Cortex-M with Ozone on Mac OSX, debugging an STM32F427 over SWD. This setup has worked well for me for many months (when the software was called J-Link Debugger, as well). However I decided to enable SWO in Ozone, which is causing problems and now I can't get Ozone to disable SWO. The issue is that the TRACECK pin (PE2) is tied to a critical component in my hardware design. It seems that once SWO has been enabled on a J-TRACE unit, Ozone enables the TRACECK pin when it ...