neulab/tldr huggingface dataset:
Configuration Please use electronut_papyr ID for projectconf_env_board option in projectconf:
[env:electronut_papyr] platform = nordicnrf52 board = electronut_papyr
You can override default ElectronutLabs Papyr settings per build environment using board_*** option, where *** is a JSON object path from board manifest electronut_papyr.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ElectronutLabs Papyr supports the next uploading protocols:
ElectronutLabs Papyr has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Frameworks ┌─────────────────┬──────────────────────────┐ │Name             │ Description              │ └─────────────────┴──────────────────────────┘
│framework_zephyr │ The Zephyr Project is a  │ │                 │ scalable real-time       │ │                 │ operating system (RTOS)  │ │                 │ supporting multiple      │ │                 │ hardware architectures,  │ │                 │ optimized for resource   │ │                 │ constrained devices, and │ │                 │ built with safety and    │ │                 │ security in mind.        │ └─────────────────┴──────────────────────────┘
Holyiot YJ-16019 Contents • Holyiot YJ-16019
┌────────────────┬──────────┐ │Microcontroller │ NRF52832 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 512KB    │ ├────────────────┼──────────┤ │RAM             │ 64KB     │ ├────────────────┼──────────┤ │Vendor          │ Holyiot  │ └────────────────┴──────────┘
Configuration Please use holyiot_yj16019 ID for projectconf_env_board option in projectconf:
[env:holyiot_yj16019] platform = nordicnrf52 board = holyiot_yj16019
You can override default Holyiot YJ-16019 settings per build environment using board_*** option, where *** is a JSON object path from board manifest holyiot_yj16019.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Holyiot YJ-16019 supports the next uploading protocols:
Holyiot YJ-16019 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
┌──────────────────────────┬──────────┬─────────┐ │Compatible Tools          │ On-board │ Default │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_blackmagic │          │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_cmsis-dap  │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_stlink     │          │         │ └──────────────────────────┴──────────┴─────────┘
ItsyBitsy nRF52840 Express Contents • ItsyBitsy nRF52840 Express
Configuration Please use adafruit_itsybitsy_nrf52840 ID for projectconf_env_board option in projectconf:
[env:adafruit_itsybitsy_nrf52840] platform = nordicnrf52 board = adafruit_itsybitsy_nrf52840
You can override default ItsyBitsy nRF52840 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_itsybitsy_nrf52840.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ItsyBitsy nRF52840 Express supports the next uploading protocols:
ItsyBitsy nRF52840 Express has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
┌──────────────────────┬──────────┬─────────┐ │Compatible Tools      │ On-board │ Default │ ├──────────────────────┼──────────┼─────────┤ │debugging_tool_jlink  │ Yes      │ Yes     │ ├──────────────────────┼──────────┼─────────┤ │debugging_tool_stlink │          │         │ └──────────────────────┴──────────┴─────────┘
Makerdiary nRF52832-MDK Contents • Makerdiary nRF52832-MDK
┌────────────────┬────────────┐ │Microcontroller │ NRF52832   │ ├────────────────┼────────────┤ │Frequency       │ 64MHz      │ ├────────────────┼────────────┤ │Flash           │ 512KB      │ ├────────────────┼────────────┤ │RAM             │ 64KB       │ ├────────────────┼────────────┤ │Vendor          │ Makerdiary │ └────────────────┴────────────┘
Configuration Please use nrf52832_mdk ID for projectconf_env_board option in projectconf:
[env:nrf52832_mdk] platform = nordicnrf52 board = nrf52832_mdk
You can override default Makerdiary nRF52832-MDK settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf52832_mdk.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Makerdiary nRF52832-MDK supports the next uploading protocols:
Makerdiary nRF52832-MDK has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Makerdiary nRF52840-MDK Contents • Makerdiary nRF52840-MDK
┌────────────────┬────────────┐ │Microcontroller │ NRF52840   │ ├────────────────┼────────────┤ │Frequency       │ 64MHz      │ ├────────────────┼────────────┤ │Flash           │ 1MB        │ ├────────────────┼────────────┤ │RAM             │ 256KB      │ ├────────────────┼────────────┤ │Vendor          │ Makerdiary │ └────────────────┴────────────┘
Configuration Please use nrf52840_mdk ID for projectconf_env_board option in projectconf:
[env:nrf52840_mdk] platform = nordicnrf52 board = nrf52840_mdk
You can override default Makerdiary nRF52840-MDK settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf52840_mdk.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Makerdiary nRF52840-MDK supports the next uploading protocols:
Makerdiary nRF52840-MDK has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Metro nRF52840 Express Contents • Metro nRF52840 Express
Configuration Please use adafruit_metro_nrf52840 ID for projectconf_env_board option in projectconf:
[env:adafruit_metro_nrf52840] platform = nordicnrf52 board = adafruit_metro_nrf52840
You can override default Metro nRF52840 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_metro_nrf52840.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Metro nRF52840 Express supports the next uploading protocols:
Metro nRF52840 Express does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Nordic Thingy:52 (nRF52-PCA20020) Contents • Nordic Thingy:52 (nRF52-PCA20020)
┌────────────────┬──────────┐ │Microcontroller │ NRF52832 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 512KB    │ ├────────────────┼──────────┤ │RAM             │ 64KB     │ ├────────────────┼──────────┤ │Vendor          │ Nordic   │ └────────────────┴──────────┘
Configuration Please use thingy_52 ID for projectconf_env_board option in projectconf:
[env:thingy_52] platform = nordicnrf52 board = thingy_52
You can override default Nordic Thingy:52 (nRF52-PCA20020) settings per build environment using board_*** option, where *** is a JSON object path from board manifest thingy_52.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Nordic Thingy:52 (nRF52-PCA20020) supports the next uploading protocols:
Nordic Thingy:52 (nRF52-PCA20020) does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Nordic nRF52-DK Contents • Nordic nRF52-DK
Configuration Please use nrf52_dk ID for projectconf_env_board option in projectconf:
[env:nrf52_dk] platform = nordicnrf52 board = nrf52_dk
You can override default Nordic nRF52-DK settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf52_dk.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Nordic nRF52-DK supports the next uploading protocols:
Nordic nRF52-DK has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Nordic nRF52840-DK Contents • Nordic nRF52840-DK
┌────────────────┬──────────┐ │Microcontroller │ NRF52840 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 1MB      │ ├────────────────┼──────────┤ │RAM             │ 256KB    │ ├────────────────┼──────────┤ │Vendor          │ Nordic   │ └────────────────┴──────────┘
Configuration Please use nrf52840_dk ID for projectconf_env_board option in projectconf:
[env:nrf52840_dk] platform = nordicnrf52 board = nrf52840_dk
You can override default Nordic nRF52840-DK settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf52840_dk.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Nordic nRF52840-DK supports the next uploading protocols:
Nordic nRF52840-DK has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Nordic nRF52840-DK (Adafruit BSP) Contents • Nordic nRF52840-DK (Adafruit BSP)
┌────────────────┬──────────┐ │Microcontroller │ NRF52840 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 796KB    │ ├────────────────┼──────────┤ │RAM             │ 243KB    │ ├────────────────┼──────────┤ │Vendor          │ Nordic   │ └────────────────┴──────────┘
Configuration Please use nrf52840_dk_adafruit ID for projectconf_env_board option in projectconf:
[env:nrf52840_dk_adafruit] platform = nordicnrf52 board = nrf52840_dk_adafruit
You can override default Nordic nRF52840-DK (Adafruit BSP) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf52840_dk_adafruit.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Nordic nRF52840-DK (Adafruit BSP) supports the next uploading protocols:
Nordic nRF52840-DK (Adafruit BSP) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Particle Argon Contents • Particle Argon
┌────────────────┬──────────┐ │Microcontroller │ NRF52840 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 796KB    │ ├────────────────┼──────────┤ │RAM             │ 243KB    │ ├────────────────┼──────────┤ │Vendor          │ Particle │ └────────────────┴──────────┘
Configuration Please use particle_argon ID for projectconf_env_board option in projectconf:
[env:particle_argon] platform = nordicnrf52 board = particle_argon
You can override default Particle Argon settings per build environment using board_*** option, where *** is a JSON object path from board manifest particle_argon.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Particle Argon supports the next uploading protocols:
Particle Argon does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Particle Boron Contents • Particle Boron
Configuration Please use particle_boron ID for projectconf_env_board option in projectconf:
[env:particle_boron] platform = nordicnrf52 board = particle_boron
You can override default Particle Boron settings per build environment using board_*** option, where *** is a JSON object path from board manifest particle_boron.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Particle Boron supports the next uploading protocols:
Particle Boron does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Particle Xenon Contents • Particle Xenon
Configuration Please use particle_xenon ID for projectconf_env_board option in projectconf:
[env:particle_xenon] platform = nordicnrf52 board = particle_xenon
You can override default Particle Xenon settings per build environment using board_*** option, where *** is a JSON object path from board manifest particle_xenon.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Particle Xenon supports the next uploading protocols:
Particle Xenon does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
RedBearLab BLE Nano 2 Contents • RedBearLab BLE Nano 2
┌────────────────┬────────────┐ │Microcontroller │ NRF52832   │ ├────────────────┼────────────┤ │Frequency       │ 64MHz      │ ├────────────────┼────────────┤ │Flash           │ 512KB      │ ├────────────────┼────────────┤ │RAM             │ 64KB       │ ├────────────────┼────────────┤ │Vendor          │ RedBearLab │ └────────────────┴────────────┘
Configuration Please use redbear_blenano2 ID for projectconf_env_board option in projectconf:
[env:redbear_blenano2] platform = nordicnrf52 board = redbear_blenano2
You can override default RedBearLab BLE Nano 2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest redbear_blenano2.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading RedBearLab BLE Nano 2 supports the next uploading protocols:
RedBearLab BLE Nano 2 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
RedBearLab Blend 2 Contents • RedBearLab Blend 2
Configuration Please use redbear_blend2 ID for projectconf_env_board option in projectconf:
[env:redbear_blend2] platform = nordicnrf52 board = redbear_blend2
You can override default RedBearLab Blend 2 settings per build environment using board_*** option, where *** is a JSON object path from board manifest redbear_blend2.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading RedBearLab Blend 2 supports the next uploading protocols:
RedBearLab Blend 2 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
SDT52832B Contents • SDT52832B
┌────────────────┬──────────────────────────┐ │Microcontroller │ NRF52832                 │ ├────────────────┼──────────────────────────┤ │Frequency       │ 64MHz                    │ ├────────────────┼──────────────────────────┤ │Flash           │ 512KB                    │ ├────────────────┼──────────────────────────┤ │RAM             │ 64KB                     │ ├────────────────┼──────────────────────────┤ │Vendor          │ Sigma Delta Technologies │ └────────────────┴──────────────────────────┘
Configuration Please use sdt52832b ID for projectconf_env_board option in projectconf:
[env:sdt52832b] platform = nordicnrf52 board = sdt52832b
You can override default SDT52832B settings per build environment using board_*** option, where *** is a JSON object path from board manifest sdt52832b.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading SDT52832B supports the next uploading protocols:
SDT52832B does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Taida Century nRF52 mini board Contents • Taida Century nRF52 mini board
┌────────────────┬───────────────┐ │Microcontroller │ NRF52832      │ ├────────────────┼───────────────┤ │Frequency       │ 64MHz         │ ├────────────────┼───────────────┤ │Flash           │ 512KB         │ ├────────────────┼───────────────┤ │RAM             │ 64KB          │ ├────────────────┼───────────────┤ │Vendor          │ Taida Century │ └────────────────┴───────────────┘
Configuration Please use stct_nrf52_minidev ID for projectconf_env_board option in projectconf:
[env:stct_nrf52_minidev] platform = nordicnrf52 board = stct_nrf52_minidev
You can override default Taida Century nRF52 mini board settings per build environment using board_*** option, where *** is a JSON object path from board manifest stct_nrf52_minidev.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Taida Century nRF52 mini board supports the next uploading protocols:
Taida Century nRF52 mini board does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
VNG VBLUno52 Contents • VNG VBLUno52
┌────────────────┬──────────┐ │Microcontroller │ NRF52832 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 512KB    │ ├────────────────┼──────────┤ │RAM             │ 64KB     │ ├────────────────┼──────────┤ │Vendor          │ VNG      │ └────────────────┴──────────┘
Configuration Please use vbluno52 ID for projectconf_env_board option in projectconf:
[env:vbluno52] platform = nordicnrf52 board = vbluno52
You can override default VNG VBLUno52 settings per build environment using board_*** option, where *** is a JSON object path from board manifest vbluno52.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading VNG VBLUno52 supports the next uploading protocols:
VNG VBLUno52 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
hackaBLE Contents • hackaBLE
Configuration Please use hackaBLE ID for projectconf_env_board option in projectconf:
[env:hackaBLE] platform = nordicnrf52 board = hackaBLE
You can override default hackaBLE settings per build environment using board_*** option, where *** is a JSON object path from board manifest hackaBLE.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading hackaBLE supports the next uploading protocols:
hackaBLE does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
u-blox EVK-NINA-B1 Contents • u-blox EVK-NINA-B1
┌────────────────┬──────────┐ │Microcontroller │ NRF52832 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 512KB    │ ├────────────────┼──────────┤ │RAM             │ 64KB     │ ├────────────────┼──────────┤ │Vendor          │ u-blox   │ └────────────────┴──────────┘
Configuration Please use ublox_evk_nina_b1 ID for projectconf_env_board option in projectconf:
[env:ublox_evk_nina_b1] platform = nordicnrf52 board = ublox_evk_nina_b1
You can override default u-blox EVK-NINA-B1 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ublox_evk_nina_b1.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading u-blox EVK-NINA-B1 supports the next uploading protocols:
u-blox EVK-NINA-B1 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
┌──────────────────────────┬──────────┬─────────┐ │Compatible Tools          │ On-board │ Default │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_blackmagic │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │ Yes      │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_stlink     │          │         │ └──────────────────────────┴──────────┴─────────┘
Nuclei GD32VF103V Evaluation Kit Contents • GD32VF103V Evaluation Kit
Hardware Platform platform_nuclei: Find professional RISC-V Processor IP in Nuclei, first professional RISC-V IP company in Mainland China, match all your requirements in AIoT Era.
┌────────────────┬───────────────┐ │Microcontroller │ GD32VF103VBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 108MHz        │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ GigaDevice    │ └────────────────┴───────────────┘
Configuration Please use gd32vf103v_eval ID for projectconf_env_board option in projectconf:
[env:gd32vf103v_eval] platform = nuclei board = gd32vf103v_eval
You can override default GD32VF103V Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest gd32vf103v_eval.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = gd32vf103vbt6
Uploading GD32VF103V Evaluation Kit supports the next uploading protocols:
Default protocol is rv-link
upload_protocol = rv-link
GD32VF103V Evaluation Kit does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
GD32VF103V RVStar Kit Contents • GD32VF103V RVStar Kit
┌────────────────┬───────────────┐ │Microcontroller │ GD32VF103VBT6 │ ├────────────────┼───────────────┤ │Frequency       │ 108MHz        │ ├────────────────┼───────────────┤ │Flash           │ 128KB         │ ├────────────────┼───────────────┤ │RAM             │ 32KB          │ ├────────────────┼───────────────┤ │Vendor          │ Nuclei        │ └────────────────┴───────────────┘
Configuration Please use gd32vf103v_rvstar ID for projectconf_env_board option in projectconf:
[env:gd32vf103v_rvstar] platform = nuclei board = gd32vf103v_rvstar
You can override default GD32VF103V RVStar Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest gd32vf103v_rvstar.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading GD32VF103V RVStar Kit supports the next uploading protocols:
GD32VF103V RVStar Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
┌──────────────────────────────────┬──────────┬─────────┐ │Compatible Tools                  │ On-board │ Default │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_altera-usb-blaster │          │         │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_gd-link            │          │         │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink              │          │         │ ├──────────────────────────────────┼──────────┼─────────┤ │debugging_tool_rv-link            │ Yes      │ Yes     │ └──────────────────────────────────┴──────────┴─────────┘
HummingBird Evaluation Kit Contents • HummingBird Evaluation Kit
┌────────────────┬─────────────┐ │Microcontroller │ HUMMINGBIRD │ ├────────────────┼─────────────┤ │Frequency       │ 5MHz        │ ├────────────────┼─────────────┤ │Flash           │ 64KB        │ ├────────────────┼─────────────┤ │RAM             │ 64KB        │ ├────────────────┼─────────────┤ │Vendor          │ Nuclei      │ └────────────────┴─────────────┘
Configuration Please use hbird_eval ID for projectconf_env_board option in projectconf:
[env:hbird_eval] platform = nuclei board = hbird_eval
You can override default HummingBird Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest hbird_eval.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = HummingBird
; change MCU frequency board_build.f_cpu = 5000000L
HummingBird Evaluation Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
┌───────────────────────┬──────────┬─────────┐ │Compatible Tools       │ On-board │ Default │ ├───────────────────────┼──────────┼─────────┤ │debugging_tool_rv-link │ Yes      │ Yes     │ └───────────────────────┴──────────┴─────────┘
NXP i.MX RT NXP i.MX RT1010 Evaluation Kit Contents • NXP i.MX RT1010 Evaluation Kit
Hardware Platform platform_nxpimxrt: The i.MX RT series of crossover processors features the Arm Cortex-M core, real-time functionality and MCU usability at a cost-effective price.
┌────────────────┬─────────────────┐ │Microcontroller │ MIMXRT1011DAE5A │ ├────────────────┼─────────────────┤ │Frequency       │ 500MHz          │ ├────────────────┼─────────────────┤ │Flash           │ 64KB            │ ├────────────────┼─────────────────┤ │RAM             │ 128KB           │ ├────────────────┼─────────────────┤ │Vendor          │ NXP             │ └────────────────┴─────────────────┘
Configuration Please use mimxrt1010_evk ID for projectconf_env_board option in projectconf:
[env:mimxrt1010_evk] platform = nxpimxrt board = mimxrt1010_evk
You can override default NXP i.MX RT1010 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1010_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mimxrt1011dae5a
; change MCU frequency board_build.f_cpu = 500000000L
Uploading NXP i.MX RT1010 Evaluation Kit supports the next uploading protocols:
NXP i.MX RT1010 Evaluation Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
┌──────────────────────────┬──────────┬─────────┐ │Compatible Tools          │ On-board │ Default │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_blackmagic │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │ Yes      │ Yes     │ └──────────────────────────┴──────────┴─────────┘
NXP i.MX RT1015 Evaluation Kit Contents • NXP i.MX RT1015 Evaluation Kit
┌────────────────┬─────────────────┐ │Microcontroller │ MIMXRT1015DAF5A │ ├────────────────┼─────────────────┤ │Frequency       │ 500MHz          │ ├────────────────┼─────────────────┤ │Flash           │ 96KB            │ ├────────────────┼─────────────────┤ │RAM             │ 128KB           │ ├────────────────┼─────────────────┤ │Vendor          │ NXP             │ └────────────────┴─────────────────┘
Configuration Please use mimxrt1015_evk ID for projectconf_env_board option in projectconf:
[env:mimxrt1015_evk] platform = nxpimxrt board = mimxrt1015_evk
You can override default NXP i.MX RT1015 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1015_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mimxrt1015daf5a
Uploading NXP i.MX RT1015 Evaluation Kit supports the next uploading protocols:
NXP i.MX RT1015 Evaluation Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
│debugging_tool_blackmagic │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │ Yes      │ Yes     │ └──────────────────────────┴──────────┴─────────┘
NXP i.MX RT1020 Evaluation Kit Contents • NXP i.MX RT1020 Evaluation Kit
┌────────────────┬─────────────────┐ │Microcontroller │ MIMXRT1021DAG5A │ ├────────────────┼─────────────────┤ │Frequency       │ 500MHz          │ ├────────────────┼─────────────────┤ │Flash           │ 64MB            │ ├────────────────┼─────────────────┤ │RAM             │ 256MB           │ ├────────────────┼─────────────────┤ │Vendor          │ NXP             │ └────────────────┴─────────────────┘
Configuration Please use mimxrt1020_evk ID for projectconf_env_board option in projectconf:
[env:mimxrt1020_evk] platform = nxpimxrt board = mimxrt1020_evk
You can override default NXP i.MX RT1020 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1020_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mimxrt1021dag5a
Uploading NXP i.MX RT1020 Evaluation Kit supports the next uploading protocols:
NXP i.MX RT1020 Evaluation Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
NXP i.MX RT1050 Evaluation Kit Contents • NXP i.MX RT1050 Evaluation Kit
┌────────────────┬─────────────────┐ │Microcontroller │ MIMXRT1052DVL6B │ ├────────────────┼─────────────────┤ │Frequency       │ 600MHz          │ ├────────────────┼─────────────────┤ │Flash           │ 64MB            │ ├────────────────┼─────────────────┤ │RAM             │ 512KB           │ ├────────────────┼─────────────────┤ │Vendor          │ NXP             │ └────────────────┴─────────────────┘
Configuration Please use mimxrt1050_evk ID for projectconf_env_board option in projectconf:
[env:mimxrt1050_evk] platform = nxpimxrt board = mimxrt1050_evk
You can override default NXP i.MX RT1050 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1050_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mimxrt1052dvl6b
; change MCU frequency board_build.f_cpu = 600000000L
Uploading NXP i.MX RT1050 Evaluation Kit supports the next uploading protocols:
NXP i.MX RT1050 Evaluation Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
NXP i.MX RT1060 Evaluation Kit Contents • NXP i.MX RT1060 Evaluation Kit
┌────────────────┬─────────────────┐ │Microcontroller │ MIMXRT1062DVL6A │ ├────────────────┼─────────────────┤ │Frequency       │ 600MHz          │ ├────────────────┼─────────────────┤ │Flash           │ 64MB            │ ├────────────────┼─────────────────┤ │RAM             │ 1MB             │ ├────────────────┼─────────────────┤ │Vendor          │ NXP             │ └────────────────┴─────────────────┘
Configuration Please use mimxrt1060_evk ID for projectconf_env_board option in projectconf:
[env:mimxrt1060_evk] platform = nxpimxrt board = mimxrt1060_evk
You can override default NXP i.MX RT1060 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1060_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mimxrt1062dvl6a
Uploading NXP i.MX RT1060 Evaluation Kit supports the next uploading protocols:
NXP i.MX RT1060 Evaluation Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
NXP i.MX RT1064 Evaluation Kit Contents • NXP i.MX RT1064 Evaluation Kit
┌────────────────┬─────────────────┐ │Microcontroller │ MIMXRT1064DVL6A │ ├────────────────┼─────────────────┤ │Frequency       │ 600MHz          │ ├────────────────┼─────────────────┤ │Flash           │ 4MB             │ ├────────────────┼─────────────────┤ │RAM             │ 1MB             │ ├────────────────┼─────────────────┤ │Vendor          │ NXP             │ └────────────────┴─────────────────┘
Configuration Please use mimxrt1064_evk ID for projectconf_env_board option in projectconf:
[env:mimxrt1064_evk] platform = nxpimxrt board = mimxrt1064_evk
You can override default NXP i.MX RT1064 Evaluation Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest mimxrt1064_evk.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = mimxrt1064dvl6a
Uploading NXP i.MX RT1064 Evaluation Kit supports the next uploading protocols:
NXP i.MX RT1064 Evaluation Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
NXP LPC ARM mbed LPC11U24 (+CAN) Contents • ARM mbed LPC11U24 (+CAN)
Hardware Platform platform_nxplpc: The NXP LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors. The LPC chips are grouped into related series that are based around the same 32-bit ARM processor core, such as the Cortex-M4F, Cortex-M3, Cortex-M0+, or Cortex-M0. Internally, each microcontroller consists of the processor core, static RAM memory, flash memory, debugging interface, and various peripherals.
┌────────────────┬──────────┐ │Microcontroller │ LPC11U24 │ ├────────────────┼──────────┤ │Frequency       │ 48MHz    │ ├────────────────┼──────────┤ │Flash           │ 32KB     │ ├────────────────┼──────────┤ │RAM             │ 8KB      │ ├────────────────┼──────────┤ │Vendor          │ NXP      │ └────────────────┴──────────┘
Configuration Please use lpc11u24_301 ID for projectconf_env_board option in projectconf:
[env:lpc11u24_301] platform = nxplpc board = lpc11u24_301
You can override default ARM mbed LPC11U24 (+CAN) settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u24_301.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc11u24
Uploading ARM mbed LPC11U24 (+CAN) supports the next uploading protocols:
ARM mbed LPC11U24 (+CAN) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Bambino-210E Contents • Bambino-210E
┌────────────────┬───────────┐ │Microcontroller │ LPC4330   │ ├────────────────┼───────────┤ │Frequency       │ 204MHz    │ ├────────────────┼───────────┤ │Flash           │ 8MB       │ ├────────────────┼───────────┤ │RAM             │ 264KB     │ ├────────────────┼───────────┤ │Vendor          │ Micromint │ └────────────────┴───────────┘
Configuration Please use lpc4330_m4 ID for projectconf_env_board option in projectconf:
[env:lpc4330_m4] platform = nxplpc board = lpc4330_m4
You can override default Bambino-210E settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc4330_m4.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc4330
; change MCU frequency board_build.f_cpu = 204000000L
Uploading Bambino-210E supports the next uploading protocols:
Bambino-210E has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
CQ Publishing TG-LPC11U35-501 Contents • CQ Publishing TG-LPC11U35-501
┌────────────────┬───────────────┐ │Microcontroller │ LPC11U35      │ ├────────────────┼───────────────┤ │Frequency       │ 48MHz         │ ├────────────────┼───────────────┤ │Flash           │ 64KB          │ ├────────────────┼───────────────┤ │RAM             │ 10KB          │ ├────────────────┼───────────────┤ │Vendor          │ CQ Publishing │ └────────────────┴───────────────┘
Configuration Please use lpc11u35_501 ID for projectconf_env_board option in projectconf:
[env:lpc11u35_501] platform = nxplpc board = lpc11u35_501
You can override default CQ Publishing TG-LPC11U35-501 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u35_501.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc11u35
Uploading CQ Publishing TG-LPC11U35-501 supports the next uploading protocols:
CQ Publishing TG-LPC11U35-501 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
┌──────────────────────────┬──────────┬─────────┐ │Compatible Tools          │ On-board │ Default │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_blackmagic │          │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ └──────────────────────────┴──────────┴─────────┘
CoCo-ri-Co! Contents • CoCo-ri-Co!
┌────────────────┬──────────────┐ │Microcontroller │ LPC812       │ ├────────────────┼──────────────┤ │Frequency       │ 30MHz        │ └────────────────┴──────────────┘
│Flash           │ 16KB         │ ├────────────────┼──────────────┤ │RAM             │ 4KB          │ ├────────────────┼──────────────┤ │Vendor          │ Elektor Labs │ └────────────────┴──────────────┘
Configuration Please use elektor_cocorico ID for projectconf_env_board option in projectconf:
[env:elektor_cocorico] platform = nxplpc board = elektor_cocorico
You can override default CoCo-ri-Co! settings per build environment using board_*** option, where *** is a JSON object path from board manifest elektor_cocorico.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc812
; change MCU frequency board_build.f_cpu = 30000000L
Uploading CoCo-ri-Co! supports the next uploading protocols:
CoCo-ri-Co! has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
DipCortex M3 Contents • DipCortex M3
┌────────────────┬────────────────────┐ │Microcontroller │ LPC1347            │ ├────────────────┼────────────────────┤ │Frequency       │ 72MHz              │ ├────────────────┼────────────────────┤ │Flash           │ 64KB               │ ├────────────────┼────────────────────┤ │RAM             │ 12KB               │ ├────────────────┼────────────────────┤ │Vendor          │ Solder Splash Labs │ └────────────────┴────────────────────┘
Configuration Please use lpc1347 ID for projectconf_env_board option in projectconf:
[env:lpc1347] platform = nxplpc board = lpc1347
You can override default DipCortex M3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc1347.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc1347
; change MCU frequency board_build.f_cpu = 72000000L
Uploading DipCortex M3 supports the next uploading protocols:
DipCortex M3 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
EA LPC11U35 QuickStart Board Contents • EA LPC11U35 QuickStart Board
┌────────────────┬──────────────────┐ │Microcontroller │ LPC11U35         │ ├────────────────┼──────────────────┤ │Frequency       │ 48MHz            │ ├────────────────┼──────────────────┤ │Flash           │ 64KB             │ ├────────────────┼──────────────────┤ │RAM             │ 10KB             │ ├────────────────┼──────────────────┤ │Vendor          │ Embedded Artists │ └────────────────┴──────────────────┘
Configuration Please use lpc11u35 ID for projectconf_env_board option in projectconf:
[env:lpc11u35] platform = nxplpc board = lpc11u35
You can override default EA LPC11U35 QuickStart Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u35.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading EA LPC11U35 QuickStart Board supports the next uploading protocols:
EA LPC11U35 QuickStart Board does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
Embedded Artists LPC4088 Display Module Contents • Embedded Artists LPC4088 Display Module
┌────────────────┬──────────────────┐ │Microcontroller │ LPC4088          │ ├────────────────┼──────────────────┤ │Frequency       │ 120MHz           │ ├────────────────┼──────────────────┤ │Flash           │ 512KB            │ ├────────────────┼──────────────────┤ │RAM             │ 96KB             │ ├────────────────┼──────────────────┤ │Vendor          │ Embedded Artists │ └────────────────┴──────────────────┘
Configuration Please use lpc4088_dm ID for projectconf_env_board option in projectconf:
[env:lpc4088_dm] platform = nxplpc board = lpc4088_dm
You can override default Embedded Artists LPC4088 Display Module settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc4088_dm.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc4088
Uploading Embedded Artists LPC4088 Display Module supports the next uploading protocols:
Embedded Artists LPC4088 Display Module has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Embedded Artists LPC4088 QuickStart Board Contents • Embedded Artists LPC4088 QuickStart Board
Configuration Please use lpc4088 ID for projectconf_env_board option in projectconf:
[env:lpc4088] platform = nxplpc board = lpc4088
You can override default Embedded Artists LPC4088 QuickStart Board settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc4088.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Embedded Artists LPC4088 QuickStart Board supports the next uploading protocols:
Embedded Artists LPC4088 QuickStart Board has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
LPCXpresso11U68 Contents • LPCXpresso11U68
┌────────────────┬──────────┐ │Microcontroller │ LPC11U68 │ ├────────────────┼──────────┤ │Frequency       │ 50MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 36KB     │ ├────────────────┼──────────┤ │Vendor          │ NXP      │ └────────────────┴──────────┘
Configuration Please use lpc11u68 ID for projectconf_env_board option in projectconf:
[env:lpc11u68] platform = nxplpc board = lpc11u68
You can override default LPCXpresso11U68 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u68.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc11u68
Uploading LPCXpresso11U68 supports the next uploading protocols:
LPCXpresso11U68 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
LPCXpresso824-MAX Contents • LPCXpresso824-MAX
┌────────────────┬────────┐ │Microcontroller │ LPC824 │ ├────────────────┼────────┤ │Frequency       │ 30MHz  │ ├────────────────┼────────┤ │Flash           │ 32KB   │ ├────────────────┼────────┤ │RAM             │ 8KB    │ ├────────────────┼────────┤ │Vendor          │ NXP    │ └────────────────┴────────┘
Configuration Please use lpc824 ID for projectconf_env_board option in projectconf:
[env:lpc824] platform = nxplpc board = lpc824
You can override default LPCXpresso824-MAX settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc824.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc824
Uploading LPCXpresso824-MAX supports the next uploading protocols:
LPCXpresso824-MAX has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
MicroNFCBoard Contents • MicroNFCBoard
┌────────────────┬───────────┐ │Microcontroller │ LPC11U34  │ ├────────────────┼───────────┤ │Frequency       │ 48MHz     │ ├────────────────┼───────────┤ │Flash           │ 48KB      │ ├────────────────┼───────────┤ │RAM             │ 10KB      │ ├────────────────┼───────────┤ │Vendor          │ AppNearMe │ └────────────────┴───────────┘
Configuration Please use micronfcboard ID for projectconf_env_board option in projectconf:
[env:micronfcboard] platform = nxplpc board = micronfcboard
You can override default MicroNFCBoard settings per build environment using board_*** option, where *** is a JSON object path from board manifest micronfcboard.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc11u34
Debugging piodebug currently does not support MicroNFCBoard board.
NGX Technologies BlueBoard-LPC11U24 Contents • NGX Technologies BlueBoard-LPC11U24
┌────────────────┬──────────────────┐ │Microcontroller │ LPC11U24         │ ├────────────────┼──────────────────┤ │Frequency       │ 48MHz            │ ├────────────────┼──────────────────┤ │Flash           │ 32KB             │ ├────────────────┼──────────────────┤ │RAM             │ 8KB              │ ├────────────────┼──────────────────┤ │Vendor          │ NGX Technologies │ └────────────────┴──────────────────┘
Configuration Please use blueboard_lpc11u24 ID for projectconf_env_board option in projectconf:
[env:blueboard_lpc11u24] platform = nxplpc board = blueboard_lpc11u24
You can override default NGX Technologies BlueBoard-LPC11U24 settings per build environment using board_*** option, where *** is a JSON object path from board manifest blueboard_lpc11u24.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading NGX Technologies BlueBoard-LPC11U24 supports the next uploading protocols:
NGX Technologies BlueBoard-LPC11U24 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
NXP LPC11C24 Contents • NXP LPC11C24
┌────────────────┬──────────┐ │Microcontroller │ LPC11C24 │ ├────────────────┼──────────┤ │Frequency       │ 48MHz    │ ├────────────────┼──────────┤ │Flash           │ 32KB     │ ├────────────────┼──────────┤ │RAM             │ 8KB      │ ├────────────────┼──────────┤ │Vendor          │ NXP      │ └────────────────┴──────────┘
Configuration Please use lpc11c24 ID for projectconf_env_board option in projectconf:
[env:lpc11c24] platform = nxplpc board = lpc11c24
You can override default NXP LPC11C24 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11c24.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc11c24
Uploading NXP LPC11C24 supports the next uploading protocols:
NXP LPC11C24 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
NXP LPC11U34 Contents • NXP LPC11U34
┌────────────────┬──────────┐ │Microcontroller │ LPC11U34 │ ├────────────────┼──────────┤ │Frequency       │ 48MHz    │ ├────────────────┼──────────┤ │Flash           │ 40KB     │ ├────────────────┼──────────┤ │RAM             │ 8KB      │ ├────────────────┼──────────┤ │Vendor          │ NXP      │ └────────────────┴──────────┘
Configuration Please use lpc11u34_421 ID for projectconf_env_board option in projectconf:
[env:lpc11u34_421] platform = nxplpc board = lpc11u34_421
You can override default NXP LPC11U34 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u34_421.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading NXP LPC11U34 supports the next uploading protocols:
NXP LPC11U34 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
NXP LPC11U37 Contents • NXP LPC11U37
┌────────────────┬──────────┐ │Microcontroller │ LPC11U37 │ ├────────────────┼──────────┤ │Frequency       │ 48MHz    │ ├────────────────┼──────────┤ │Flash           │ 128KB    │ ├────────────────┼──────────┤ │RAM             │ 10KB     │ ├────────────────┼──────────┤ │Vendor          │ NXP      │ └────────────────┴──────────┘
Configuration Please use lpc11u37_501 ID for projectconf_env_board option in projectconf:
[env:lpc11u37_501] platform = nxplpc board = lpc11u37_501
You can override default NXP LPC11U37 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc11u37_501.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc11u37
Uploading NXP LPC11U37 supports the next uploading protocols:
NXP LPC11U37 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
NXP LPC800-MAX Contents • NXP LPC800-MAX
┌────────────────┬────────┐ │Microcontroller │ LPC812 │ ├────────────────┼────────┤ │Frequency       │ 30MHz  │ ├────────────────┼────────┤ │Flash           │ 16KB   │ ├────────────────┼────────┤ │RAM             │ 4KB    │ ├────────────────┼────────┤ │Vendor          │ NXP    │ └────────────────┴────────┘
Configuration Please use lpc812 ID for projectconf_env_board option in projectconf:
[env:lpc812] platform = nxplpc board = lpc812
You can override default NXP LPC800-MAX settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc812.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading NXP LPC800-MAX supports the next uploading protocols:
NXP LPC800-MAX has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
NXP LPCXpresso1549 Contents • NXP LPCXpresso1549
┌────────────────┬─────────┐ │Microcontroller │ LPC1549 │ ├────────────────┼─────────┤ │Frequency       │ 72MHz   │ ├────────────────┼─────────┤ │Flash           │ 256KB   │ ├────────────────┼─────────┤ │RAM             │ 36KB    │ ├────────────────┼─────────┤ │Vendor          │ NXP     │ └────────────────┴─────────┘
Configuration Please use lpc1549 ID for projectconf_env_board option in projectconf:
[env:lpc1549] platform = nxplpc board = lpc1549
You can override default NXP LPCXpresso1549 settings per build environment using board_*** option, where *** is a JSON object path from board manifest lpc1549.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = lpc1549
Uploading NXP LPCXpresso1549 supports the next uploading protocols:
NXP LPCXpresso1549 does not have on-board debug probe and IS NOT READY for debugging. You will need to use/buy one of external probe listed below.
NXP LPCXpresso54114 Contents • NXP LPCXpresso54114