how much does iar embedded workbench for arm cost

If we take a closer look at some of the new interesting items in the IDE, the first one is the Cores window. In this window, we can see that it is taken from the IDE instance connected to the Cortex-A core (bold), that it is stopped, and the PC for that core.

We also get some info for the Cortex-M core, namely that it is running.Īnother new item is these additions to the debug toolbar:įirst there are two icons describing the state of the cores, and then the new controls starting and stopping all cores buttons.īy hovering over one of the core in the toolbar, you can get further info, matching the info in the Cores window. In this toolbar, there is also a pull down menu for each core and with the use of these you can either stop or start the selected core.ĭebugging a symmetric device with several cores is similar to the example above. But instead of two instances, only one instance of the IDE is displaying the info. Here the normal debug windows such as watch windows, memory windows etc. will display the information that is related to the core being in focus. Selecting what core to focus on is done in the Cores window. There is some special setup to handle, but not much. For instance, in the asymmetric case, for the master session you must declare it as a multicore master, and also describe what project to use as a partner.

For the partner, we have already mentioned that if the master programs the device, the partner debug session cannot do it. Also the selected reset strategy must not affect the master session, so usually partner sessions use some kind of software reset.

How much does iar embedded workbench for arm cost