d1136b4857
* Demo/CORTEX_MPS2_QEMU_IAR_GCC: fix warnings * fix compiler warning "gcc -Wmissing-prototypes" in startup_gcc.c * fix compiler warning "gcc -Wredundant-decls" in main.c * change stack size from 88 to 128 * change heap from 60 to 64 Kbyte Signed-off-by: Florian La Roche <Florian.LaRoche@gmail.com> * Increase heap size for tracing on --------- Signed-off-by: Florian La Roche <Florian.LaRoche@gmail.com> Co-authored-by: Rahul Kar <118818625+kar-rahul-aws@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| .vscode | ||
| build | ||
| CMSIS | ||
| TraceRecorderConfig | ||
| FreeRTOSConfig.h | ||
| Instructions.url | ||
| IntQueueTimer.c | ||
| IntQueueTimer.h | ||
| main.c | ||
| main_blinky.c | ||
| main_full.c | ||
| Readme.md | ||
Running with VSCode Launch Configurations
Prerequisites
- Install C/C++ extension in VSCode.
- Install arm-none-eabi-gcc.
- Install GNU make utility.
- Ensure the required binaries are in PATH with
arm-none-eabi-gcc --version,arm-none-eabi-gdb --version, andmake --version.
Building and Running
- Open VSCode to the folder
FreeRTOS/Demo/CORTEX_MPS2_QEMU_IAR_GCC. - Open
.vscode/launch.json, and ensure themiDebuggerPathvariable is set to the path where arm-none-eabi-gdb is on your machine. - Open
main.c, and setmainCREATE_SIMPLE_BLINKY_DEMO_ONLYto1to generate just the simply blinky demo. - On the VSCode left side panel, select the “Run and Debug” button. Then select “Launch QEMU RTOSDemo” from the dropdown on the top right and press the play button. This will build, run, and attach a debugger to the demo program.
Tracing with Percepio View
This demo project includes Percepio TraceRecorder, configured for snapshot tracing with Percepio View or Tracealyzer. Percepio View is a free tracing tool from Percepio, providing the core features of Percepio Tracealyzer but limited to snapshot tracing. No license or registration is required. More information and download is found at Percepio's product page for Percepio View.
TraceRecorder Integration
If you like to study how TraceRecorder is integrated, the steps for adding TraceRecorder are tagged with "TODO TraceRecorder" comments in the demo source code. This way, if using an Eclipse-based IDE, you can find a summary in the Tasks window by selecting Window -> Show View -> Tasks (or Other, if not listed). See also the official getting-started guide.
Usage with GDB
To save the TraceRecorder trace, start a debug session with GDB. Halt the execution and the run the command below. This saves the trace as trace.bin in the build/gcc folder. Open the trace file in Percepio View or Tracealyzer.
If using an Eclipse-based IDE, run the following command in the "Debugger Console":
dump binary value trace.bin *RecorderDataPtr
If using VS Code, use the "Debug Console" and add "-exec" before the command:
-exec dump binary value trace.bin *RecorderDataPtr
Note that you can typically copy/paste this command into the debug console.
Usage with IAR Embedded Workbench for Arm
Launch the IAR debugger. With the default project configuration, this should connect to the QEMU GDB server. To save the trace, please refer to the "Snapshot Mode" guide at https://percepio.com/iar. In summary:
- Download the IAR macro file save_trace_buffer.mac (click "save as")
- Add the macro file in the project options -> Debugger -> Use Macro File(s).
- Start debugging and open View -> Macros -> Debugger Macros.
- Locate and run "save_trace_buffer". Open the resulting "trace.hex" in Percepio View or Tracealyzer.