erase - Erase DUT Flash
Erase DUT MCU on-board flash.
Usage:
- command: erase <target> [<uartPort>]
[id: <usbDeviceID>]
[path: <usbDevicePath>]
[interface: <usbDeviceInterface>]
[retry: <retryCount>]
Argument |
Description |
|---|---|
target |
Target to erase. A clock frequency may be appended as |
uartPort |
UART port name. Only required for UART programming targets. |
usbDeviceID |
Optional: Programming adapter USB device identifiers: |
usbDevicePath |
Optional: Programming adapter USB device path: |
usbDeviceInterface |
Optional: Programming adapter USB device interface: |
retryCount |
Optional: Number of times to retry the test step. |
Note
USB-DFU targets cannot be erased with this command; the erase step will fail. USB-DFU
devices are erased as part of program (unless noerase is specified).
- command: erase CMSIS
pack: <cmsisPack>
target: <cmsisTarget>
[id: <usbDeviceID>]
[path: <usbDevicePath>]
[retry: <retryCount>]
Argument |
Description |
|---|---|
target |
Target to erase |
cmsisPack |
Optional: CMSIS Pack file. |
cmsisTarget |
Target name, as defined in CMSIS Pack file. |
usbDeviceID |
Optional: USB device identifiers: |
usbDevicePath |
Optional: USB device path: |
retryCount |
Number of times to retry the test step (optional) |
On the PLT-300A, the programming adapter can be specified using usbDeviceID, usbDevicePath, and
usbDeviceInterface. Specifying the programming adapter location allows multiple adapters of the
same type to be used in a single test plan, or for an external adapter to be used in place of the built-in
programming adapter. See USB Interaction for details on specifying USB devices.
Supported target values:
target |
Description |
|---|---|
|
Microchip (Atmel) SAM D1x/D2x, C2x, L2x, R2x or R3x (SWD) |
|
Microchip (Atmel) SAM D1x/D2x, C2x, L2x, R2x or R3x (USB, DAPlink) |
|
Microchip (Atmel) SAM D5x/E5x (SWD) |
|
Microchip (Atmel) SAM D5x/E5x (USB, DAPlink) |
|
Microchip (Atmel) AVR ATmega168P(A) (JTAG:ISP) |
|
Microchip (Atmel) AVR ATmega168P(A) (USB, XPmini) |
|
Microchip (Atmel) AVR ATmega168PB (JTAG:ISP) |
|
Microchip (Atmel) AVR ATmega168PB (USB, XPmini) |
|
TI CC1352P1, CC1352R1 RFSoC (USB, CMSIS-DAP) |
|
TI CC1352P7 RFSoC (USB, CMSIS-DAP) |
|
CMSIS-DAP programmer, requires |
|
Silicon Labs EFM32 MCU (SWD) |
|
Silicon Labs EFR32 RFSoC (SWD) |
|
Espressif ESP32 RFSoC (UART) |
|
NXP LPC11xx MCU (SWD) |
|
Nordic nRF52 RFSoC (SWD) |
|
Nordic nRF52 RFSoC (USB, CMSIS-DAP) |
|
Nordic nRF52 RFSoC (USB, JLink) |
|
Nordic nRF9160 RFSoC:Cortex-M33 (SWD) |
|
Nordic nRF9160 RFSoC:Cortex-M33 (USB, JLink) |
|
Microchip PIC18F25K20 (JTAG:ICSP) |
|
Microchip PIC18F25K20 (USB, PICkit2) |
|
NXP PN7360 (SWD) |
|
NXP PN7362 (SWD) |
|
NXP PN7412 (SWD) |
|
NXP PN7462 (SWD) |
|
Infineon (Cypress) PSoC4 (SWD) |
|
Infineon (Cypress) PSoC6 (SWD) |
|
Infineon (Cypress) PSoC6 (USB, KitProg3) |
|
Raspberry Pi RP2040 (SWD) |
|
Raspberry Pi RP2040 (USB, CMSIS-DAP) |
|
ST STM32F1xx MCU (SWD) |
|
ST STM32F1xx MCU (USB, ST-Link) |
|
ST STM32F2xx MCU (SWD) |
|
ST STM32F2xx MCU (USB, ST-Link) |
|
ST STM32F4xx MCU (SWD) |
|
ST STM32F4xx MCU (USB, ST-Link) |
|
ST STM32G0xx MCU (SWD) |
|
ST STM32G0xx MCU (USB, ST-Link) |
|
ST STM32G4xx MCU (SWD) |
|
ST STM32G4xx MCU (USB, ST-Link) |
|
ST STM32L0xx MCU (SWD) |
|
ST STM32L0xx MCU (USB, ST-Link) |
|
ST STM32L4xx MCU (SWD) |
|
ST STM32L4xx MCU (USB, ST-Link) |
|
ST STM32L5xx MCU (SWD) |
|
ST STM32L5xx MCU (USB, ST-Link) |
|
ST STM32H7xx MCU (SWD) |
|
ST STM32H7xx MCU, dual-bank flash (SWD) |
|
ST STM32H7xx MCU (USB, ST-Link) |
Note
The target list above covers commonly used programming targets. Additional MCU-specific targets (further STM32 and LPC family variants, TI CC13xx/CC26xx RFSoCs, additional PIC18 and AVR parts, and others) are supported by the underlying programmer; contact Blue Clover Devices if the target you need is not listed here.
Examples