Programming operations

1. Connect to the device (see Connect device).
2. Click the Erase button.

ModusToolbox™ Programmer erases the device and displays various messages in the Log. Then, a message in the Status Bar indicates that the device was erased successfully or that an error occurred.

1. Connect the device to the host computer and select it in the Programmer/Board ID, Board Name, and Device drop-downs.
2. Select the programming file as described in Load programming file section.
3. Connect to the device (see Connect device).
4. Click the Program button.

ModusToolbox™ Programmer programs the device and displays various messages in the Log. Then, a message in the Status Bar indicates that device was programmed successfully or that an error occurred.

1. Connect the device to the host computer and select it in the Programmer/Board ID, Board Name, and Device drop-downs.
2. Select the programming file as described in the Load programming file section.
3. Connect to the device (see Connect device).
4. Select the Reset Chip check box under Program Settings.
5. Click the Program button.

ModusToolbox™ Programmer programs the device and displays various messages in the Log. Then, a message in the Status Bar indicates that the device was programmed successfully or that an error occurred.

The target device is reset and running.

1. Connect the device to the host computer and select it in the Programmer/Board ID, Board Name, and Device drop-downs.
2. Select a binary programming file as described in the Load programming file section.
3. Connect to the device (see Connect device).
4. Enter the desired address in the Offset field under Program Settings.
5. Click the Program button.

ModusToolbox™ Programmer programs the device and displays various messages in the Log. Then, a message in the Status Bar indicates that the device was programmed successfully or that an error occurred.

1. Attach and select a device that supports external memory (for example, CY8CKIT-062-WiFi-BT with QSPI support).
2. Select the External Memory option under Program Settings.
   
   
   
   
3. Select the programming file as described in the Load programming file section. The programming file should contain external memory region(s) and correct QSPI configuration data.
4. For PSOC™ 6 devices only, select Erase/Program USER/TOC/KEY allowed option under Probe Settings > Sflash Restrictions.
5. Connect to the device (see Connect device).
6. Click the Program button.

ModusToolbox™ Programmer programs the device and displays various messages in the Log. Then, a message in the Status Bar indicates that the device was programmed successfully or that an error occurred.

1. Connect the host computer to a MiniProg4 or J-Link probe attached to several MCU targets in the JTAG chain.
   The following hardware configuration is used in this example:
   

   

   
   

   The sample JTAG chain configuration contains six serially-connected PSOC™ MCU targets.

2. Select the MiniProg4 probe and target device in the Programmer/Board ID, Board Name, and Device drop-downs, and ModusToolbox™ Programmer will display information under Probe Settings. Ensure the JTAG chain is powered.
3. Select the JTAG interface in the Interface drop-down.
   
   
   
   
   ModusToolbox™ Programmer queries the JTAG chain and displays detected devices under the JTAG Chain option in Probe Settings. The list of devices in the chain contains target names for supported devices and ID codes for those which are not supported.
   

   

   
   
4. Select the desired target device in the list by clicking the radio button next to the target name.
5. Select the programming file as described in the Load programming file section.
6. Click Connect. ModusToolbox™ Programmer communicates with the device and displays various messages in the Log. Then, a message in the Status Bar indicates that it is connected.
   
   
   
   
7. Click the Program button.

ModusToolbox™ Programmer programs the device and displays various messages in the Log. Then, a message in the Status Bar indicates that the device was programmed successfully or that an error occurred.

1. Connect the device to the host computer and select it in the Programmer/Board ID, Board Name, and Device drop-downs.
2. Select the programming file as described in the Load programming file section.
3. Connect to the device (see Connect device).
4. Click the Verify button.

ModusToolbox™ Programmer performs the Verify device operation and displays various messages in the Log. Then, a message in the Status Bar indicates that the device was verified successfully or that an error occurred.

1. Connect the device that supports external memory (for example, CY8CKIT-062-WiFi-BT with QSPI support) to the host computer and select it in the Programmer/Board ID, Board Name, and Device drop-downs.
2. Select the programming file as described in the Load programming file section. The programming file should have external memory region(s).
3. Select the External Memory option under Program Settings.
4. Connect to the device (see Connect device).
   
   
   
   
5. Click the Verify button.

ModusToolbox™ Programmer verifies the device and displays various messages in the Log. Then, a message in the Status Bar indicates that the device was verified successfully or that an error occurred.

1. Connect the device to the host computer and select it in the Programmer/Board ID, Board Name, and Device drop-downs.
2. Select the programming file as described in the Load programming file section.
3. Connect to the device (see Connect device).
4. Expand Verify Regions option in Program Settings to see the list of flash regions available for verification. By default, only supported by target device regions are displayed:
   • application
   • AUXflash
   • Sflash
   • eFuse
   • QSPI
   
   
   
   
   
5. Right-click on Verify Regions or any region entry to open the context menu.
   
   
   
   
6. To add a custom flash region, select Add Region. Select the added list entry, and enter the correct values for start and end addresses of the region.
   
   
   
   
7. To remove any region in the list, right-click the desired region entry and select Remove Region.
   
   
   
   
8. To revert any previous change, select Undo.
9. When finished with the list of regions, start device verification by clicking the Verify button on the toolbar.
   
   
   
   
   You can also select Verify on the context menu.
   

   

   
   

   ModusToolbox™ Programmer verifies only the regions specified in the Verify Regions list. Then, a message in the Status Bar indicates that the device was verified successfully or that an error occurred.

10. To reset the Verify Regions list to its default state select Reload Regions from the context menu. This action will remove all custom regions and load default regions corresponding to the flash map.
    
    
    
    

1. Connect the device to the host computer and select it in the Programmer/Board ID, Board Name, and Device drop-downs.
2. Connect to the device (see Connect device).
3. Click the Read button.
   
   
   
   
4. On the Read Device to File dialog, navigate to the location of the HEX or SREC file to be saved, enter the file name, select the file type in the Save as type drop-down, and click Save.
   
   
   
   

ModusToolbox™ Programmer performs the Read device operation and displays various messages in the Log. Then, a message in the Status Bar indicates that the device was read successfully or that an error occurred.

1. Connect the device to the host computer and select it in the Programmer/Board ID, Board Name, and Device drop-downs.
2. Select the programming file as described in the Load programming file section. The programming file should contain valid eFuse data region (at address 0x90700000).
3. Select the Program Security Data check box under Program Settings.
   
   
   
   
4. Connect to the device (see Connect device).
5. Click the Program button.

ModusToolbox™ Programmer programs the device and displays various messages in the Log. Then, a message in the Status Bar indicates that the device was programmed successfully or that an error occurred.

If some eFuse bits have been already programmed before, a warning message "The efuse bit at address xx has been already blown" appears in Log.

The chip-level protection mechanism restricts access of the programmer application to silicon resources. In this mode, access to flash, SRAM, and most of the registers in the PSOC™ 4, PMG1, PAG2s, and CCGx are disabled.

If you try to connect ModusToolbox™ Programmer to a chip-protected PSOC™ 4/CCGx device, a warning message indicates that the device is in protected mode. The only available operation is Erase device in this case.

Use the Erase button to clear chip protection and move target to the open state.

You can program the flash of an AIROC™ CYW20829 device in Secure lifecycle mode only by providing a valid debug certificate file.

1. Connect the device to the host computer and select it in the Programmer/Board ID, Board Name, and Device drop-downs.
2. Select the programming file as described in the Load programming file section.
3. Click on the Debug Certificate option under Program Settings and select the certificate file in the dialog.
   The path will display under Settings.
   

   

   
   
4. Connect to the device (see Connect device).
5. Click the Program button.

This feature is supported by AIROC™ CYW20829 devices, as well as PSOC™ Edge E84, XMC7100/7200 and CYT4Bx MCUs. It allows you to specify the patched flashloader file in FLM format along with the appropriate QSPI configuration. Patched flashloaders contain data about how your external memory is configured.

1. Connect the device to the host computer and select it in the Programmer/Board ID, Board Name, and Device drop-downs.
2. Select the programming file as described in the Load programming file section.
3. Select the External Memory option under Program Settings (if supported).
4. Click on the Flashloader option under Program Settings and select the patched flashloader (FLM) file in the dialog.
   The path will display under Settings.
   

   

   
   
5. Connect to the device (see Connect device).
6. Click the Program button.

1. Connect the device to the host computer and perform recover device procedure as described in How to recover AIROC™ Bluetooth® devices on failure.
2. Click the Programmer pull-down and select 'WICED Bluetooth-PortXX' programmer.
   
   
   
   
   Note:

   The CYW9M2BASE-43012BT board should be switched to Dual UART mode first, otherwise the WICED Bluetooth® programmer will be unavailable in the Board Name pull-down menu. To do this, press the hardware 'Mode' button on the Kit, hold it for 3 seconds, then release it.
3. Open the Board Name pull-down and select the appropriate board name (e.g., CYW955513EVK-01)
4. Select the programming file as described in the Load programming file section.
5. Connect to the device (see Connect device).
6. Click the Program button.

ModusToolbox™ Programmer programs the device and displays various messages in the Log. Then, a message in the Status Bar indicates that the device was programmed successfully or that an error occurred.

Some KitProg3 development kits were released to market with missing board configuration in the EEPROM. In this case, the Programmer/Board ID displays the kit as generic KitProg3 device as:

KitProg3 CMSIS-DAP Bulk-1014091C02179400

Some development kits may require updating the name of the board after changing SOM modules on them for example:

KIT_PSE84_EVAL_EPC2 (EPC4).

1. Click on the Board Preferences button to update the name of your kit. The Board Preferences dialog opens.
2. As needed, click on the Show all boards check box to display the full list of supported names.
   
   
3. Select the correct board name for your kit in the list and click the Update button.
   
   
   
   
   The tool checks if the selected name corresponds to the actual connected KitProg3 device. Board configuration is updated in the EEPROM of KitProg3. The success status and a new board name are displayed.
   

   

   
   
   Note:

   The “Device not updated” error means an incorrect kit name was selected.
4. Click the Close button, the dialog closes and the updated board name displays in the pull-downs.