![]() ![]() It is not meant to be an exhaustive guide and will not provide any kind of in depth information about how SystemView works, but is provided here in the hope that it may save someone else time somewhere down the track. It is these notes that I will share in this post. The entire setup was a little protracted so I kept notes on everything I did to get everything work. The STM32 Nucleo and Discovery boards are very well suited for this use case as they contain an on-board ST-LINK programmer/debugger, and SEGGER provide a free way to convert the ST-LINK module to a J-Link module. ![]() This particular setup was pretty neat because it provided multiple methods for debugging the system, and was entirely free. In this setup I was also using System Workbench for STM32 with SEGGER J-Link debugging. I recently setup SystemView to work with a STM32 Nucleo based development board to debug the behaviour of FreeRTOS in a visual manner. #Segger embedded studio raspberry softwareThis limit is actually very easy to exceed in larger applications, but still renders the free version of the software very useful. A huge plus for using SystemView is that it is totally free to use, provided that in one event recording session you do not exceed one million recorded events. These events can be recorded using J-Link, IP, or UART communication. ![]() SEGGER SystemView is a very cool graphical tool for embedded systems that enables the visualisation of run-time behaviour in an application by the recording on configurable events. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |