Search Results

Hello AlexD, you are right, it is definitely a problem with the JLink_x64.dll shipped with Ozone V3.32a (7.96). I replaced the DLL with version 7.94k (this version is shipped with Ozone V3.32) and that works and I also used the one from the latest J-Link Package, 7.96c, which also works.

The latest version of the Ozone Debugger fails to connect to the NXP S32K344 microcontroller. This can be reproduces with the sample project from wiki.segger.com/NXP_S32K3xx#Streaming_trace NXP_S32K344_TracePins.zip Open the project with Ozone V3.32 and connect -> Works, open the project with Ozone V3.32a and connect -> Fails. I am using an older j-Trace Pro for ARM Cortex-M (Part No. 8.18.00) and my operating System is Windows 10 Professional. This is the Console output with the failing connect…

I tried to create a minimal example showing the issue but now it is working again. Also the original project (which I changed in the mean time) is working again, including J-Scope. I don't know what happened and I am not able to reproduce it again.

I am trying to graph a variable with the Data Sampling feature but Ozone does not sample any values, I know that it was working in the past. The Watch window refresh is working and RTT is also working so background memory access itself works. Whenever I change the sampling frequency a new value is recorded but nothing more. I am using Ozone V3.28c, Segger Jlink Package V7.84d and a j-Trace Pro for Arm Cortex-M running the lasted Firmware compiled 23.01.2023. I attached a gif showing this behavio…

After a lot of trial and error I found out that my sModule string is wrong and that I also need a module description file additionally, this thread can be closed. Still it is not nice that SystemView just hangs in this case

I am currently in the process of instrumenting a MICROSAR OS based application on an NXP S32K148 ARM Cortex M4 processor. The relevant code looks like this: C Source Code (22 lines)However SystemView records only a few milliseconds of activity and then hangs. The controller itself is running and with the debugger I see that the SystemView API is called correctly. If I comment out the SEGGER_SYSVIEW_RegisterModule(&TestModule); line then everything is working as expected. I am only registering th…

I am trying to debug some data that is held within a reference on the stack. However, I am not able to see the content of it in ozone. In my production project I get "<outofscope>" in the location. In the minimal example shown below I get the correct address, size and type; however I don't get any values displayed: forum.segger.com/index.php/Attachment/4764/ OS: Windows 10 1909 Compiler: ARMCC 6.6.3 with -O0 Target: LPC1768 Ozone Version: 3.22e The example code: C Source Code (35 lines)