Versions Compared

Old Version 10

changes.mady.by.user Thomas Watteyne

Saved on

compared with

New Version Current

changes.mady.by.user Jonathan Simon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

During  the build process, the bottom pane of the IAR Windows lists those steps:


 

No Format
Building configuration: 02-temp - Debug 
Updating build tree... 

22  file(s) deleted. 
Updating build tree... 
cli_task.c  
temp_app.c  
dnm_cli_util.c  
dnm_cli.c  
dnm_local.c  
notification_task.c  
Linking 
ocfdk_02-temp.out 

Total number of errors: 0 
Total number of warnings: 0

Loading a Sample Application

You have two options for loading your application onto your 

Include Page
_def_board_fraser
_def_board_fraser
-based board.

Load the ELF File for Debugging

Info

To be able to debug your application, you need an in-circuit debugging probe. The projects have been set up for the j-link.

Include Page
_inc_i-jet
_inc_i-jet

Tip

This option is best suited when developing your application. It allows you to use on-chip debugging tools such as breakpoints and live watch.

  • In your IAR project, click on the Download and Debug button.
     
  • This builds the project and loads your application file onto your 
    Include Page
    _def_board_fraser
    _def_board_fraser
    -based board.

  • After your program has loaded, you can start execution by clicking the Go button to start execution.

  • You can now halt the execution, place breakpoints, and inspect variables.
  • Click the Stop Debugging button to exit the debugging section.
     
Note

When loading your application onto the board, IAR may display the following dialog.

Image Removed

This indicates that IAR is not able to display the source file for a module inside the library. This is normal, and is not an error.

When this message appears, check If possible, don't show this dialog again and click Skip.


Note

This procedure only loads the main executable. For the board to function correctly, you also need to load additional elements in flash (fuse table, partition table, loader).

We recommend you follow the steps in the Programming Eterna Devices page once, after which you can replace the main executable multiple times using the procedure above. When reprogramming, IAR only replaces the main executable while other elements in flash (fuse table, partition table, loader) remain untouched.

One side-effect is that, even if you replace the main executable, the file system remains untouched. If you had created files with a previous main executable, those files are still there after reprogramming the device using the procedure above. You can use the

Include Page
_def_esp
_def_esp
to erase the file system.

Load the binary file

Tip

This option is best suited when you are done creating your application, and you want to deploy it on one or more motes without needing debugging capabilities.

IAR is configured to output both an ELF and a binary file (see Installing the IAR Tool Chain).

You can use the 

Include Page
_def_esp
_def_esp
 tool to load this binary file as the main application by following the steps in the Programming Eterna Devices section.

Note

This option replaces the entire flash image. This means that:

  • you lose any nonvolatile configurations during the loading process, such as the netid.
  • you lose the security state maintained between the manager and the mote. If the mote you are reprogramming previously joined a manager, you need to power-cycle the manager before the mote can re-join, or delete the mote (from CLI or API).