Part 3:
Part 3 will continues where part 2 left off.
See part 1 here: [Project: Embedded] Hands On RTOS with MCU’s Part 1
See part 2 here: [Project: Embedded] Hands On RTOS with MCU’s Part 2
The focus will be on ‘System View’ a debugging software that is used after firmware is built just like ‘Ozone’. The dev hardware also needs to be connected to the computer for debugging for ‘System View’ to work. The difference from ‘Ozone’ is program execution cannot be halted/interrupted and must be run in real-time to watch events and tasks. There is some overhead behind the scenes that enable ‘System View’ to work which includes some source code updates to enable Segger Real Time Transfer (RTT) for advanced debugging.
The step-by-step:
- Assuming part 2 was completed. Part 3 continues off. If not go back to part 2 and complete exercise.
- Open Application ‘STM32CubeIDE’
- Save to some workspace (not too critical where)…
- Go to File->Import
- Go to General->Existing Projects into Workspace
- Open and browse to ‘C:\projects…’ then click ‘Next’
- Right click on project RTOS_Example_1->properties
- Go to Resource->Linked Resources and click on ‘Linked Resources’ tab
- Resolve paths… and ‘Apply and Close’
- Right click on project RTOS_Example_1->Index->Rebuild
- Right click on project RTOS_Example_1->Build Project
- Run project so dev board runs.
- Open ‘System View’ and ensure dev hardware is connected to computer.
- Continue thru prompts if asked.
- Press ‘play’ button to run ‘System View’ and view information in real-time from MCU.
- If warranted, export to CSV file of session is possible for later analysis.
- DONE!
