Skip to main content

IAR Embedded Workbench for RH850 3.20.x

Some considerations

In this section:

When you debug more than one core, you should be aware of how this affects other aspects of debugger behavior:

  • Reset and Go commands reset/start all cores. The Go command starts only the core in focus.

  • All cores initialize their own system registers and variables located in their local RAM. The first core (PE0 for G4 or PE1 for G3) will also initialize all global RAM areas and the C++ constructors while the other cores wait for it to complete.

  • Code breakpoints affect all cores

  • The stack size settings in the Project Options dialog box affect all cores

  • Timer Start and Timer Stop breakpoints are valid for the core that is in focus when the execution starts.

  • Trace collection is performed for the core that is in focus when the execution starts.

  • The contents in the Memory window for the zones LOCAL_RAM_SELF, LOCAL_RAM_PE1, LOCAL_RAM_PE2, etc., are valid when the execution stops. Any manual edits in one of these memory zones are not reflected in the other zones until the next time that the execution stops.