Before you can start debugging, you need to be able to establish a debug session with your target microcontroller.
- Please refer to the Getting Started chapter to learn where to find or how to configure a workspace and establish a debug session with your target microcontroller.
- Read the Technical notes to learn about the configuration specific to your target microcontroller.
- If you wish to debug multi-core microcontroller, refer to the Multi-core debugging chapter.
Once you have the debug session established, configure the OS awareness and network description (if used):
- OS Awareness
In case you are using an operating system in your target application, you should configure OS awareness to obtain the following benefits:
- Network awareness
If you wish to inspect how your application behaves in regard to the network traffic / signals, you need to provide the network description:
- CAN2/LIN2: baudrate, message and signal descriptions...
- ADIO: logical voltage levels, input-output selections...
This will enable you to trace network traffic and correlate it to the application running on the microcontroller.
Further configuration of network qualifies and triggers is available in the Hardware / FNet Operation dialog.
Once you have the debug session established and your environment properly described, you are ready to delve into debugging.
winIDEA features several debug windows and plugins for better insight into the application and microcontroller behavior. They offer insight in the memory contents, variable values, current callstack, disassembly reconstruction, special function register values and descriptions...