Search Results

Hello, in case the recording works while the system is crashing (and the target can still be accessed afterwards) the recording should still show the corruption. But SystemView may not record everything fine enough. In such cases tracing may be preferable. RTT is only used as input here. As long as the idle time or crashing issue is part of the recording, it can be shown in SystemView. Best regards, Sebastian

Hello, in case your target does not support RTT, you need to save the data recording from the target to a file on the host system. This is explained in the manual here: segger.com/doc/UM08027_SystemView.html#Single_shot_recording In short, following steps are required: - Halt the application with the debugger when either the recording is done or the buffer is full - Get the RTT buffer address and number of bytes used (usually _SEGGER_RTT.aUp[1].pBuffer and _SEGGER_RTT.aUp[1].WrOff) - Save the us…

Hello, in case SystemView otherwise already works on your setup, the markers are shown in the main recording window. You can filter for all marker events by clicking View -> Event Filter -> Show Markers. Best regards, Sebastian

Hi Frank, maybe I have not been completely clear. As written in the other thread: The package has been fixed and will be released with the next batch of packages Meaning the package has already been fully prepared and is ready for the next release. This of course means it is not available in Embedded Studio yet, but will be soon. Best regards, Sebastian

Hi, thank you for your inquiry. The packages has recently been updated using the most recent CMSIS files provided by ST. Unfortunately the RAM size for some of the subfamilies was set incorrectly, meaning larger than actually available on the device. Because of this memory addresses were used which are not actually available on the device. As the stack is usually placed at the end of the RAM region, it hard-faults on the first push instruction. The package has already been fixed and will be rele…

Hello Pradeep, Thank you for your inquiry. Generally SystemView should work in your case, but there are some limitations: Arm9 does not support background memory access, so continuous mode with RTT cannot be used. So only single-shot or post-mortem mode can be used. You can find more information regarding these modes in the manual. Alternatively you may use UART or IP as interface instead of using J-Link, as this is also supported when using Arm9 You can find more information regarding SystemVie…

We reproduced and fixed the issue. The fix is already available in the newly released J-Link V7.80. Could you give the latest version a try? BR Sebastian

Hi, We will close this thread, as you also contacted us via the Support Ticket system. Please make sure to keep communication to one channel for future request. Otherwise - information might be lost between channels - this might lead to a higher work load on our side, resulting in slower response time Best regards, Sebastian