Please enable JavaScript to view this site.

winIDEA Help

Version: 9.21.174

Navigation: » No topics above this level «

Scroll Prev Top Next More


Before you can start debugging, you need to configure and establish a Debug Session with your target microcontroller.


Learn where how to configure a workspace and establish a Debug Session with your target microcontroller.


Learn about the configuration specific to your target microcontroller.



Multi-core Debugging (optional).

Debug a multi-core microcontroller!



Operating Systems (optional).

Configure your OS awareness to obtain the following benefits:



FNet communication  (optional).

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.



Starting a Debug Session.

Once the Debug Configuration is ready, a Debug Session can be started. This happens with any of these commands:

  • Debug / Download - Establishes control of the device at its reset point and programs FLASH and RAM
  • Debug / Load Symbols Only - Establishes control of the device at its reset point
  • Debug / Attach - Establishes control of a running device without stopping it
  • Debug / Prepare to attach - Initializes the emulator to be ready for device attach
  • Debug / Reset - establishes control of the device at its reset point. within an active session, this will only reset the device
  • Debug / Run - same as Debug / Download but after programming the device is set to running




When a Debug Session is already active, the Download and Load Symbols Only will end the current session and start a new one.


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.



Ending a Debug Session.

A Debug Session ends with the Tools / Disconnect from Debugger command.



Copyright© iSYSTEM AG Carl-Zeiss-Str.1 85247 Schwabhausen Germany