Skip to main content

IAR Debug Probes

Updating the probe firmware

In this section:

I-jet and I-jet Trace are designed so that firmware updates are not necessary unless new features added to IAR Embedded Workbench require extra hardware support. When a new version of IAR Embedded Workbench is released and a new feature that requires new firmware is used, C-SPY displays a message in the Debug Log window asking you to update the firmware.

Note

Support for new MCU devices is managed by software updates in IAR Embedded Workbench, and has nothing to do with I-jet or I-jet Trace firmware.

For more information about firmware versions, see the release notes.

Warning

Make sure that you do not accidentally disconnect the probe during the update process, as this can damage the probe permanently.

To update the probe firmware

How you update the probe firmware depends on your version of IAR Embedded Workbench.

IAR Embedded Workbench for Arm v9.70 and earlier and IAR Embedded Workbench for RISC-V v3.40 and earlier:
  1. In IAR Embedded Workbench, choose I-jet>EmuDiag to display the About to Connect to an Emulator dialog box.

    AboutToConnectToEmu_01.png

    Select Connect to an Emulator Automatically and click Next.

  2. In the EmuDiag dialog box, click Update Firmware.

    EmuDiag_01.png
  3. In the Open dialog box, browse to this folder of your IAR Embedded Workbench installation:

    IAR Embedded Workbench for Arm: arm\bin\jet\firmware\i-jet

    IAR Embedded Workbench for RISC-V: riscv\bin\ijet\firmware\i-jet

    In one of the subfolders, select the firmware file that you want to use and click Open.

    I-jetFWpath_ARM_01.png
  4. The update log information is displayed in the EmuDiag dialog box.

    EmuDiagUpdateLog_ARM_01.png
  5. When the firmware update is complete, a message is displayed.

    EmuUpdated_01.png
IAR Embedded Workbench for Arm v10.10 and later and IAR Embedded Workbench for RISC-V v4.10 and later:
  1. Connect the debug probe whose firmware you want to update. Only one I-jet or I-jet Trace probe can be connected during a firmware update.

  2. Make sure that the probe is not connected to a target.

  3. Navigate to the probe folder in the installation directory, arm\bin\jet or riscv\bin\jet, and open a terminal window there.

  4. Execute this command to start the update: emudiagcli.exe --firmware fw_file (see below for the file path)

  5. The terminal displays progress information throughout the update process. When the update completes, a confirmation message is displayed.

Example:

PS C:\iar\ewarmc-10.10.1\arm\bin\jet> .\emudiagcli.exe --firmware .\
firmware\i-jet\v8.2\I-JET.upg
 ___ __  __ _   _ ___ ___   _   ___
| __|  \/  | | | |   \_ _| /_\ / __|
| _|| |\/| | |_| | |) | | / _ \ (_ |
|___|_|  |_|\___/|___/___/_/ \_\___|

emudiagcli 1.0 started ...  
Probe: Probe SW module ver 1.69  
Enumerating probes ...  
Probe: Found I-jet, SN=89682  
Probe: Opened connection to I-jet:89682  
******  WARNING: Make sure that you do not accidentally disconnect the probe   
during the update process,  
as this can damage the probe permanently.  
******  
Are you sure you want to continue? [y/N] y  
Current FLASH (fmt_id=1): Model: I-jet (11/04/2020 11:49)  
 PRN: 1703 (07/06/2019 11:47)  
 S/N: 89682 (07/06/2019 11:47)  
Current EEPROM:  
USBEEPROM initialized.  
Reading image from EEPROM...  
 Model: I-jet  
 S/N: 89682 (09/11/2026 14:42)  
 Version: 2 (07/23/2013 17:29)  

FLASH will be programmed with file .\firmware\i-jet\v8.2\I-JET.sef  
Signature in file (fmt_id=1):  
 Model: I-jet (11/04/2020 11:49)  

EEPROM will be programmed with file .\firmware\i-jet\v8.2\  
EEP_C2_V2.sef  
Signature in file:  
 I-jet  
 Version: 12 (07/23/2013 17:29)  
FLASH controller loaded image from file .\firmware\i-jet\v8.2\I-JET.sef  
FLASH operation skipped (same FW date and time code).  
Starting EEPROM programming and verifying  
...................................EEPROM programming and verifying finished   
successfully.  

Programmed OK  
Emulator updated.  

Please disconnect the emulator from the USB port,  
turn the emulator power off and on,  
and then reconnect.  
***************************************************  
*********** Programming finished ***********  
***************************************************