identify - Identify DUT
Identify DUT MCU and/or RF peripherals.
The MCU identifier is stored in the mcu_id key, and the
BLE MAC address (if available) is stored in the ble_mac key.
Usage:
- command: identify <target> [<uartPort>]
[id: <usbDeviceID>]
[path: <usbDevicePath>]
[interface: <usbDeviceInterface>]
[retry: <retryCount>]
Argument |
Description |
|---|---|
target |
Target to identify. 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
identify is only implemented for the targets listed below (a specific subset of
program/erase targets, since MCU identification requires vendor- and family-specific
register reads). CMSIS, SDCard, and USB-DFU targets do not support identification.
AVR targets are only supported when programmed via ISP or Xplained mini (_XPm); the
FTDI and PICkit4 AVR variants, and all PIC18 targets, do not support identification.
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) 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) |
|
Espressif ESP32 RFSoC (UART) |
|
Analog Devices (Maxim) MAX32690 (SWD) |
|
Analog Devices (Maxim) MAX32690 (USB, JLink) |
|
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) |
|
ST STM32F0xx MCU (SWD) |
|
ST STM32F0xx MCU (USB, ST-Link) |
|
ST STM32F1xx MCU (SWD) |
|
ST STM32F1xx MCU (USB, ST-Link) |
|
ST STM32F2xx MCU (SWD) |
|
ST STM32F2xx MCU (USB, ST-Link) |
|
ST STM32F3xx MCU (SWD) |
|
ST STM32F3xx 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 STM32L1xx Category 1 or 2 MCU (SWD) |
|
ST STM32L1xx Category 3 MCU (SWD) |
|
ST STM32L1xx Category 4, 5, or 6 MCU (SWD) |
|
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) |