Recent Activities

Hello! There is strange behaviour observed when debugging Cortex-A7 IMX6ULL processor. Application loading and debugging fine, but only until i opened Generic Timer peripheral from CP15 menu. After that debugging practically breaks, user no longer able…

Hello, Alex. Yes, indeed i'am using .svd file from Ozone installation: C:/Program Files/SEGGER/Ozone V3.38a/Config/CPU/Cortex-A7.svd Board i'am working with is MYS-6ULX Single Board Computer from MYIR, i don't have any evaluation board, sorry. .log…

Hi Vlad, thanks for letting us know. We are not aware of such an issue. Which SVD file are you using? Is it `Cortex-A7.svd` that is coming with Ozone? Are you able to reproduce the issue on an eval board? If so: which one? Could you please provide a…

Ugh. Wow. So I guess I need to use J-Link RTT Viewer - how do I disable the Ozone Terminal?

Hello While debugging MIMX9352_A55_0 it works fine while trying to get into debug mode for MIMX9352_A55_1 i get failed to Connect to target message I have attached the image of the error message clearly

Hello! Using latest Ozone (v3.38a) debugging .elf application for IMX6ULL (Cortex-A7), the second part of double precision registers (D16 to D31) are displayed incorrectly: forum.segger.com/index.php/Att…bff747d984e3c26e91941d8bf It seems only lower 32…

you can see that in the image of the project file startup script

Hi AndyR, on which device, exactly do you observe that behavior? We shall try to reproduce locally. Best regards -- AlexD

H Namklak, Ozone does not support sending such control characters to the target. Best regards -- AlexD

SystemView: Yes, I've been using it on 15.0.1 but have yet to try it on 15.1 (it was only just updated). I haven't tried Ozone yet, but I'll try that and let you know how it goes.

I think this is a bad idea. Because for one, this "shared" library code must be located in the BL application/sector, or else it would most probably delete itself partially when updating the application. However, that defeats the main idea of a separate…

Recently I had a strange anomaly, where I build the project twice in a row and on the second build it seems that the path to the ARM toolchain has broken. I'm confused because I haven't changed anything for that to happen. The error is the…

I'm using the following command to read channel 1: Shell-Script (5 lines) When JLinkRTTLogger connects, the code starts executing immediately, but "Data written" in JLinkRTTLogger doesn't start counting. The code only blocks when JLinkRTTLogger…

I am using J-Trace Pro Cortex-M debugger with a S32K344, the problem is that I get an Unexpected core ID when connecting over JTAG to the MCU with J-Flash. However the issue does not occur when I connect over SWD. The same issue happens when using MDK…

Not sure if this is an SES issue or STM32 issue, so posting here and in an ST forum... Trying to work with the STM32F411 USB OTG peripheral and compiling with Segger Embedded Studio, I'm having trouble clearing out the USB interrupts. The USB…

I found some clues about this issue. (1) When I use __attribute__((section(".noncacheable"))) to assign some variables, the watch function is valid and can be updated when the mcu is running. exp: __attribute__((section(".noncacheable"))) int…

I'm debugging a target Running Zephyr CLI, which can use arrow keys and <ctrl>+key combo keystrokes, but when I type those in the Ozone Terminal input frame, Ozone doesn't seem to send those to the target - any ideas? Thanks, Namklak

Hello, before updating my Apple silicon Mac to MacOS 15 Sequoia I would like to ask wether Ozone and SystemView have been tested under MacOS 15? Regards AlfredJodaQuak

Hi there, I’m trying to program an external SPI flash (IS25LP032D) that is connected to a MCU STM32G474, but only the MCU can have a socket for plugging the J-Link to be programmed. Therefore, to program the external flash I need to use the MCU and do…

Hi, In my application I am using PDMA1 ch1 for audio buffer updates. LCD display seems to be using PDMA as well. NVT_Draw1 function defined in fsa506.c uses PDMA0 ch2 to write data to LCD. The logic inside NVT_Draw1 does not interfere with the logic of…