Hello David,
Thank you for your inquiry.
The default method for using the post-mortem analysis is to connect to the target without resetting or modifying the RAM.
In case that you want to save the buffer in a file, this is also possible. Then you have to copy the SystemView buffer to the corresponding file when your system enters the fault handler.
For more information about both methods see: https://www.segger.com/doc/UM08027_Sy…mortem_analysis
Best regards,
Tobias
Hello Cosmin,
Could you please clarify which exat version of SystemView has displayed the cycle counter?
It is correct that only the run time and the run count is displayed sice the run time is much more meanigful than the cycle counter.
Best regards,
Tobias
Hello Luca,
The wiki article is for the case that you want to use RTT for your outputs (e.g. printf).
Since all data relating to SystemView is sent via events, there is no need for the Syscalls file. This means, that you do not have to include the Syscalls file to your project to be able to use SystemView.
You mentioned RTX is running on the device, so you should take a look at the OS instrumentation for SystemView (see https://www.segger.com/doc/UM08027_Sy…View_into_an_OS). Otherwise the timeline will propably not be displayed correctly (due to different tasks, scheduler, etc.).
Best regards,
Tobias
Hello Vinay,
I have replied to your support ticket.
The issue was caused by the configuration of the interrupt locking fuction (SEGGER_RTT_LOCK).
In future, please use only use one support channel for one topic.
We will consider this case as closed now.
Best regards,
Tobias
