neulab/tldr huggingface dataset:
┌────────────────┬──────────────────┐ │Microcontroller │ 32MZ2048EFH100   │ ├────────────────┼──────────────────┤ │Frequency       │ 252MHz           │ ├────────────────┼──────────────────┤ │Flash           │ 1.98MB           │ ├────────────────┼──────────────────┤ │RAM             │ 512KB            │ ├────────────────┼──────────────────┤ │Vendor          │ MikroElektronika │ └────────────────┴──────────────────┘
Configuration Please use flipnclickmz ID for projectconf_env_board option in projectconf:
[env:flipnclickmz] platform = microchippic32 board = flipnclickmz
You can override default MikroElektronika Flip N Click MZ settings per build environment using board_*** option, where *** is a JSON object path from board manifest flipnclickmz.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MZ2048EFH100
; change MCU frequency board_build.f_cpu = 252000000L
Debugging piodebug currently does not support MikroElektronika Flip N Click MZ board.
Mini 2.0 Contents • Mini 2.0
┌────────────────┬──────────────┐ │Microcontroller │ 32MX270F256D │ ├────────────────┼──────────────┤ │Frequency       │ 48MHz        │ ├────────────────┼──────────────┤ │Flash           │ 240KB        │ ├────────────────┼──────────────┤ │RAM             │ 62KB         │ ├────────────────┼──────────────┤ │Vendor          │ Fubarino     │ └────────────────┴──────────────┘
Configuration Please use fubarino_mini_20 ID for projectconf_env_board option in projectconf:
[env:fubarino_mini_20] platform = microchippic32 board = fubarino_mini_20
You can override default Mini 2.0 settings per build environment using board_*** option, where *** is a JSON object path from board manifest fubarino_mini_20.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Mini 2.0 board.
Olimex PIC32-PINGUINO Contents • Olimex PIC32-PINGUINO
┌────────────────┬──────────────┐ │Microcontroller │ 32MX440F256H │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 252KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ Olimex       │ └────────────────┴──────────────┘
Configuration Please use pinguino32 ID for projectconf_env_board option in projectconf:
[env:pinguino32] platform = microchippic32 board = pinguino32
You can override default Olimex PIC32-PINGUINO settings per build environment using board_*** option, where *** is a JSON object path from board manifest pinguino32.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX440F256H
Debugging piodebug currently does not support Olimex PIC32-PINGUINO board.
OpenBCI 32bit Contents • OpenBCI 32bit
┌────────────────┬──────────────┐ │Microcontroller │ 32MX250F128B │ ├────────────────┼──────────────┤ │Frequency       │ 40MHz        │ ├────────────────┼──────────────┤ │Flash           │ 120KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ OpenBCI      │ └────────────────┴──────────────┘
Configuration Please use openbci ID for projectconf_env_board option in projectconf:
[env:openbci] platform = microchippic32 board = openbci
You can override default OpenBCI 32bit settings per build environment using board_*** option, where *** is a JSON object path from board manifest openbci.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support OpenBCI 32bit board.
PONTECH UAV100 Contents • PONTECH UAV100
┌────────────────┬──────────────┐ │Microcontroller │ 32MX440F512H │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ PONTECH      │ └────────────────┴──────────────┘
Configuration Please use usbono_pic32 ID for projectconf_env_board option in projectconf:
[env:usbono_pic32] platform = microchippic32 board = usbono_pic32
You can override default PONTECH UAV100 settings per build environment using board_*** option, where *** is a JSON object path from board manifest usbono_pic32.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MX440F512H
Debugging piodebug currently does not support PONTECH UAV100 board.
Pic32 CUI32-Development Stick Contents • Pic32 CUI32-Development Stick
┌────────────────┬──────────────┐ │Microcontroller │ 32MX440F512H │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ SparkFun     │ └────────────────┴──────────────┘
Configuration Please use cui32 ID for projectconf_env_board option in projectconf:
[env:cui32] platform = microchippic32 board = cui32
You can override default Pic32 CUI32-Development Stick settings per build environment using board_*** option, where *** is a JSON object path from board manifest cui32.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Pic32 CUI32-Development Stick board.
Pontech NoFire Contents • Pontech NoFire
┌────────────────┬────────────────┐ │Microcontroller │ 32MZ2048EFG100 │ ├────────────────┼────────────────┤ │Frequency       │ 200MHz         │ ├────────────────┼────────────────┤ │Flash           │ 1.98MB         │ ├────────────────┼────────────────┤ │RAM             │ 512KB          │ ├────────────────┼────────────────┤ │Vendor          │ Pontech        │ └────────────────┴────────────────┘
Configuration Please use nofire ID for projectconf_env_board option in projectconf:
[env:nofire] platform = microchippic32 board = nofire
You can override default Pontech NoFire settings per build environment using board_*** option, where *** is a JSON object path from board manifest nofire.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = 32MZ2048EFG100
Debugging piodebug currently does not support Pontech NoFire board.
Pontech Quick240 Contents • Pontech Quick240
┌────────────────┬──────────────┐ │Microcontroller │ 32MX795F512L │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 128KB        │ ├────────────────┼──────────────┤ │Vendor          │ Pontech      │ └────────────────┴──────────────┘
Configuration Please use quick240_usb ID for projectconf_env_board option in projectconf:
[env:quick240_usb] platform = microchippic32 board = quick240_usb
You can override default Pontech Quick240 settings per build environment using board_*** option, where *** is a JSON object path from board manifest quick240_usb.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support Pontech Quick240 board.
RGB Station Contents • RGB Station
┌────────────────┬──────────────┐ │Microcontroller │ 32MX270F256D │ ├────────────────┼──────────────┤ │Frequency       │ 48MHz        │ ├────────────────┼──────────────┤ │Flash           │ 240KB        │ ├────────────────┼──────────────┤ │RAM             │ 62KB         │ ├────────────────┼──────────────┤ │Vendor          │ ChipKIT      │ └────────────────┴──────────────┘
Configuration Please use rgb_station ID for projectconf_env_board option in projectconf:
[env:rgb_station] platform = microchippic32 board = rgb_station
You can override default RGB Station settings per build environment using board_*** option, where *** is a JSON object path from board manifest rgb_station.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support RGB Station board.
SeeedStudio CUI32stem Contents • SeeedStudio CUI32stem
┌────────────────┬──────────────┐ │Microcontroller │ 32MX795F512H │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 128KB        │ ├────────────────┼──────────────┤ │Vendor          │ SeeedStudio  │ └────────────────┴──────────────┘
Configuration Please use cui32stem ID for projectconf_env_board option in projectconf:
[env:cui32stem] platform = microchippic32 board = cui32stem
You can override default SeeedStudio CUI32stem settings per build environment using board_*** option, where *** is a JSON object path from board manifest cui32stem.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support SeeedStudio CUI32stem board.
UBW32 MX460 Contents • UBW32 MX460
┌────────────────┬──────────────┐ │Microcontroller │ 32MX460F512L │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ UBW32        │ └────────────────┴──────────────┘
Configuration Please use ubw32_mx460 ID for projectconf_env_board option in projectconf:
[env:ubw32_mx460] platform = microchippic32 board = ubw32_mx460
You can override default UBW32 MX460 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ubw32_mx460.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support UBW32 MX460 board.
UBW32 MX795 Contents • UBW32 MX795
┌────────────────┬──────────────┐ │Microcontroller │ 32MX795F512L │ ├────────────────┼──────────────┤ │Frequency       │ 80MHz        │ ├────────────────┼──────────────┤ │Flash           │ 508KB        │ ├────────────────┼──────────────┤ │RAM             │ 128KB        │ ├────────────────┼──────────────┤ │Vendor          │ UBW32        │ └────────────────┴──────────────┘
Configuration Please use ubw32_mx795 ID for projectconf_env_board option in projectconf:
[env:ubw32_mx795] platform = microchippic32 board = ubw32_mx795
You can override default UBW32 MX795 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ubw32_mx795.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support UBW32 MX795 board.
chipKIT Lenny Contents • chipKIT Lenny
┌────────────────┬──────────────┐ │Microcontroller │ 32MX270F256D │ ├────────────────┼──────────────┤ │Frequency       │ 40MHz        │ ├────────────────┼──────────────┤ │Flash           │ 120KB        │ ├────────────────┼──────────────┤ │RAM             │ 32KB         │ ├────────────────┼──────────────┤ │Vendor          │ chipKIT      │ └────────────────┴──────────────┘
Configuration Please use lenny ID for projectconf_env_board option in projectconf:
[env:lenny] platform = microchippic32 board = lenny
You can override default chipKIT Lenny settings per build environment using board_*** option, where *** is a JSON object path from board manifest lenny.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support chipKIT Lenny board.
chipKIT WiFire rev. C Contents • chipKIT WiFire rev. C
┌────────────────┬────────────────┐ │Microcontroller │ 32MZ2048EFG100 │ ├────────────────┼────────────────┤ │Frequency       │ 200MHz         │ ├────────────────┼────────────────┤ │Flash           │ 1.98MB         │ ├────────────────┼────────────────┤ │RAM             │ 512KB          │ ├────────────────┼────────────────┤ │Vendor          │ Digilent       │ └────────────────┴────────────────┘
Configuration Please use chipkit_wifire_revc ID for projectconf_env_board option in projectconf:
[env:chipkit_wifire_revc] platform = microchippic32 board = chipkit_wifire_revc
You can override default chipKIT WiFire rev. C settings per build environment using board_*** option, where *** is a JSON object path from board manifest chipkit_wifire_revc.json. For example, board_build.mcu, board_build.f_cpu, etc.
Debugging piodebug currently does not support chipKIT WiFire rev. C board.
Nordic nRF51 BBC micro:bit Contents • BBC micro:bit
Hardware Platform platform_nordicnrf51: The Nordic nRF51 Series is a family of highly flexible, multi-protocol, system-on-chip (SoC) devices for ultra-low power wireless applications. nRF51 Series devices support a range of protocol stacks including Bluetooth Smart (previously called Bluetooth low energy), ANT and proprietary 2.4GHz protocols such as Gazell.
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 16MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 16KB     │ ├────────────────┼──────────┤ │Vendor          │ BBC      │ └────────────────┴──────────┘
Configuration Please use bbcmicrobit ID for projectconf_env_board option in projectconf:
[env:bbcmicrobit] platform = nordicnrf51 board = bbcmicrobit
You can override default BBC micro:bit settings per build environment using board_*** option, where *** is a JSON object path from board manifest bbcmicrobit.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = nrf51822
Uploading BBC micro:bit supports the next uploading protocols:
BBC micro:bit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
BluzDK Contents • BluzDK
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 32MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 32KB     │ ├────────────────┼──────────┤ │Vendor          │ BluzDK   │ └────────────────┴──────────┘
Configuration Please use bluz_dk ID for projectconf_env_board option in projectconf:
[env:bluz_dk] platform = nordicnrf51 board = bluz_dk
You can override default BluzDK settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluz_dk.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading BluzDK supports the next uploading protocols:
• nrfjprog
Default protocol is jlink
upload_protocol = jlink
BluzDK 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      │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_stlink     │          │         │ └──────────────────────────┴──────────┴─────────┘
Calliope mini Contents • Calliope mini
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 16MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 16KB     │ ├────────────────┼──────────┤ │Vendor          │ Calliope │ └────────────────┴──────────┘
Configuration Please use calliope_mini ID for projectconf_env_board option in projectconf:
[env:calliope_mini] platform = nordicnrf51 board = calliope_mini
You can override default Calliope mini settings per build environment using board_*** option, where *** is a JSON object path from board manifest calliope_mini.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Calliope mini supports the next uploading protocols:
Calliope mini has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Delta DFCM-NNN40 Contents • Delta DFCM-NNN40
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 32MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 32KB     │ ├────────────────┼──────────┤ │Vendor          │ Delta    │ └────────────────┴──────────┘
Configuration Please use dfcm_nnn40 ID for projectconf_env_board option in projectconf:
[env:dfcm_nnn40] platform = nordicnrf51 board = dfcm_nnn40
You can override default Delta DFCM-NNN40 settings per build environment using board_*** option, where *** is a JSON object path from board manifest dfcm_nnn40.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Delta DFCM-NNN40 supports the next uploading protocols:
Delta DFCM-NNN40 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_cmsis-dap │ Yes      │ Yes     │ └─────────────────────────┴──────────┴─────────┘
Delta DFCM-NNN50 Contents • Delta DFCM-NNN50
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 32MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 16KB     │ ├────────────────┼──────────┤ │Vendor          │ Delta    │ └────────────────┴──────────┘
Configuration Please use delta_dfcm_nnn50 ID for projectconf_env_board option in projectconf:
[env:delta_dfcm_nnn50] platform = nordicnrf51 board = delta_dfcm_nnn50
You can override default Delta DFCM-NNN50 settings per build environment using board_*** option, where *** is a JSON object path from board manifest delta_dfcm_nnn50.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Delta DFCM-NNN50 supports the next uploading protocols:
Delta DFCM-NNN50 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
JKSoft Wallbot BLE Contents • JKSoft Wallbot BLE
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 16MHz    │ ├────────────────┼──────────┤ │Flash           │ 128KB    │ ├────────────────┼──────────┤ │RAM             │ 16KB     │ ├────────────────┼──────────┤ │Vendor          │ JKSoft   │ └────────────────┴──────────┘
Configuration Please use wallbot_ble ID for projectconf_env_board option in projectconf:
[env:wallbot_ble] platform = nordicnrf51 board = wallbot_ble
You can override default JKSoft Wallbot BLE settings per build environment using board_*** option, where *** is a JSON object path from board manifest wallbot_ble.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading JKSoft Wallbot BLE supports the next uploading protocols:
JKSoft Wallbot BLE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Nordic Beacon Kit (PCA20006) Contents • Nordic Beacon Kit (PCA20006)
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 32MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 32KB     │ ├────────────────┼──────────┤ │Vendor          │ Nordic   │ └────────────────┴──────────┘
Configuration Please use nrf51_beacon ID for projectconf_env_board option in projectconf:
[env:nrf51_beacon] platform = nordicnrf51 board = nrf51_beacon
You can override default Nordic Beacon Kit (PCA20006) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf51_beacon.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Nordic Beacon Kit (PCA20006) supports the next uploading protocols:
Nordic Beacon Kit (PCA20006) 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_cmsis-dap  │ Yes      │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │ Yes      │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_stlink     │          │         │ └──────────────────────────┴──────────┴─────────┘
Nordic nRF51 Dongle (PCA10031) Contents • Nordic nRF51 Dongle (PCA10031)
Configuration Please use nrf51_dongle ID for projectconf_env_board option in projectconf:
[env:nrf51_dongle] platform = nordicnrf51 board = nrf51_dongle
You can override default Nordic nRF51 Dongle (PCA10031) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf51_dongle.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Nordic nRF51 Dongle (PCA10031) supports the next uploading protocols:
Nordic nRF51 Dongle (PCA10031) 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_cmsis-dap │ Yes      │         │ ├─────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink     │ Yes      │ Yes     │ └─────────────────────────┴──────────┴─────────┘
Nordic nRF51822-mKIT Contents • Nordic nRF51822-mKIT
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 16MHz    │ ├────────────────┼──────────┤ │Flash           │ 128KB    │ ├────────────────┼──────────┤ │RAM             │ 16KB     │ ├────────────────┼──────────┤ │Vendor          │ Nordic   │ └────────────────┴──────────┘
Configuration Please use nrf51_mkit ID for projectconf_env_board option in projectconf:
[env:nrf51_mkit] platform = nordicnrf51 board = nrf51_mkit
You can override default Nordic nRF51822-mKIT settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf51_mkit.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Nordic nRF51822-mKIT supports the next uploading protocols:
Nordic nRF51822-mKIT has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Nordic nRF51X22 Development Kit(PCA1000X) Contents • Nordic nRF51X22 Development Kit(PCA1000X)
Configuration Please use nrf51_dk ID for projectconf_env_board option in projectconf:
[env:nrf51_dk] platform = nordicnrf51 board = nrf51_dk
You can override default Nordic nRF51X22 Development Kit(PCA1000X) settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf51_dk.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Nordic nRF51X22 Development Kit(PCA1000X) supports the next uploading protocols:
Nordic nRF51X22 Development Kit(PCA1000X) has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
OSHChip Contents • OSHChip
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 32MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 32KB     │ ├────────────────┼──────────┤ │Vendor          │ OSHChip  │ └────────────────┴──────────┘
Configuration Please use oshchip ID for projectconf_env_board option in projectconf:
[env:oshchip] platform = nordicnrf51 board = oshchip
You can override default OSHChip settings per build environment using board_*** option, where *** is a JSON object path from board manifest oshchip.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading OSHChip supports the next uploading protocols:
OSHChip 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 1.5 Contents • RedBearLab BLE Nano 1.5
┌────────────────┬────────────┐ │Microcontroller │ NRF51822   │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 32KB       │ ├────────────────┼────────────┤ │Vendor          │ RedBearLab │ └────────────────┴────────────┘
Configuration Please use redBearLabBLENano ID for projectconf_env_board option in projectconf:
[env:redBearLabBLENano] platform = nordicnrf51 board = redBearLabBLENano
You can override default RedBearLab BLE Nano 1.5 settings per build environment using board_*** option, where *** is a JSON object path from board manifest redBearLabBLENano.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading RedBearLab BLE Nano 1.5 supports the next uploading protocols:
RedBearLab BLE Nano 1.5 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_cmsis-dap  │ Yes      │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_stlink     │          │         │ └──────────────────────────┴──────────┴─────────┘
RedBearLab nRF51822 Contents • RedBearLab nRF51822
┌────────────────┬────────────┐ │Microcontroller │ NRF51822   │ ├────────────────┼────────────┤ │Frequency       │ 16MHz      │ ├────────────────┼────────────┤ │Flash           │ 256KB      │ ├────────────────┼────────────┤ │RAM             │ 16KB       │ ├────────────────┼────────────┤ │Vendor          │ RedBearLab │ └────────────────┴────────────┘
Configuration Please use redBearLab ID for projectconf_env_board option in projectconf:
[env:redBearLab] platform = nordicnrf51 board = redBearLab
You can override default RedBearLab nRF51822 settings per build environment using board_*** option, where *** is a JSON object path from board manifest redBearLab.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading RedBearLab nRF51822 supports the next uploading protocols:
RedBearLab nRF51822 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Seeed Arch BLE Contents • Seeed Arch BLE
┌────────────────┬─────────────┐ │Microcontroller │ NRF51822    │ ├────────────────┼─────────────┤ │Frequency       │ 16MHz       │ ├────────────────┼─────────────┤ │Flash           │ 128KB       │ ├────────────────┼─────────────┤ │RAM             │ 16KB        │ ├────────────────┼─────────────┤ │Vendor          │ SeeedStudio │ └────────────────┴─────────────┘
Configuration Please use seeedArchBLE ID for projectconf_env_board option in projectconf:
[env:seeedArchBLE] platform = nordicnrf51 board = seeedArchBLE
You can override default Seeed Arch BLE settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeedArchBLE.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Seeed Arch BLE supports the next uploading protocols:
Seeed Arch BLE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Seeed Arch Link Contents • Seeed Arch Link
┌────────────────┬─────────────┐ │Microcontroller │ NRF51822    │ ├────────────────┼─────────────┤ │Frequency       │ 16MHz       │ ├────────────────┼─────────────┤ │Flash           │ 256KB       │ ├────────────────┼─────────────┤ │RAM             │ 16KB        │ ├────────────────┼─────────────┤ │Vendor          │ SeeedStudio │ └────────────────┴─────────────┘
Configuration Please use seeedArchLink ID for projectconf_env_board option in projectconf:
[env:seeedArchLink] platform = nordicnrf51 board = seeedArchLink
You can override default Seeed Arch Link settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeedArchLink.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Seeed Arch Link supports the next uploading protocols:
Seeed Arch Link has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Seeed Tiny BLE Contents • Seeed Tiny BLE
Configuration Please use seeedTinyBLE ID for projectconf_env_board option in projectconf:
[env:seeedTinyBLE] platform = nordicnrf51 board = seeedTinyBLE
You can override default Seeed Tiny BLE settings per build environment using board_*** option, where *** is a JSON object path from board manifest seeedTinyBLE.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Seeed Tiny BLE supports the next uploading protocols:
Seeed Tiny BLE has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Sino:Bit Contents • Sino:Bit
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 32MHz    │ ├────────────────┼──────────┤ │Flash           │ 256KB    │ ├────────────────┼──────────┤ │RAM             │ 32KB     │ ├────────────────┼──────────┤ │Vendor          │ sino:bit │ └────────────────┴──────────┘
Configuration Please use Sinobit ID for projectconf_env_board option in projectconf:
[env:Sinobit] platform = nordicnrf51 board = Sinobit
You can override default Sino:Bit settings per build environment using board_*** option, where *** is a JSON object path from board manifest Sinobit.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Sino:Bit supports the next uploading protocols:
Sino:Bit 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.
Switch Science mbed HRM1017 Contents • Switch Science mbed HRM1017
┌────────────────┬────────────────┐ │Microcontroller │ NRF51822       │ ├────────────────┼────────────────┤ │Frequency       │ 16MHz          │ ├────────────────┼────────────────┤ │Flash           │ 256KB          │ ├────────────────┼────────────────┤ │RAM             │ 16KB           │ ├────────────────┼────────────────┤ │Vendor          │ Switch Science │ └────────────────┴────────────────┘
Configuration Please use hrm1017 ID for projectconf_env_board option in projectconf:
[env:hrm1017] platform = nordicnrf51 board = hrm1017
You can override default Switch Science mbed HRM1017 settings per build environment using board_*** option, where *** is a JSON object path from board manifest hrm1017.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Switch Science mbed HRM1017 supports the next uploading protocols:
Switch Science mbed HRM1017 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Switch Science mbed TY51822r3 Contents • Switch Science mbed TY51822r3
┌────────────────┬────────────────┐ │Microcontroller │ NRF51822       │ ├────────────────┼────────────────┤ │Frequency       │ 32MHz          │ ├────────────────┼────────────────┤ │Flash           │ 256KB          │ ├────────────────┼────────────────┤ │RAM             │ 32KB           │ ├────────────────┼────────────────┤ │Vendor          │ Switch Science │ └────────────────┴────────────────┘
Configuration Please use ty51822r3 ID for projectconf_env_board option in projectconf:
[env:ty51822r3] platform = nordicnrf51 board = ty51822r3
You can override default Switch Science mbed TY51822r3 settings per build environment using board_*** option, where *** is a JSON object path from board manifest ty51822r3.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Switch Science mbed TY51822r3 supports the next uploading protocols:
Switch Science mbed TY51822r3 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
VNG VBLUNO51 Contents • VNG VBLUNO51
┌────────────────┬──────────┐ │Microcontroller │ NRF51822 │ ├────────────────┼──────────┤ │Frequency       │ 16MHz    │ ├────────────────┼──────────┤ │Flash           │ 128KB    │ ├────────────────┼──────────┤ │RAM             │ 32KB     │ ├────────────────┼──────────┤ │Vendor          │ VNG      │ └────────────────┴──────────┘
Configuration Please use vbluno51 ID for projectconf_env_board option in projectconf:
[env:vbluno51] platform = nordicnrf51 board = vbluno51
You can override default VNG VBLUNO51 settings per build environment using board_*** option, where *** is a JSON object path from board manifest vbluno51.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading VNG VBLUNO51 supports the next uploading protocols:
VNG VBLUNO51 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Waveshare BLE400 Contents • Waveshare BLE400
┌────────────────┬───────────┐ │Microcontroller │ NRF51822  │ ├────────────────┼───────────┤ │Frequency       │ 32MHz     │ ├────────────────┼───────────┤ │Flash           │ 256KB     │ ├────────────────┼───────────┤ │RAM             │ 32KB      │ ├────────────────┼───────────┤ │Vendor          │ Waveshare │ └────────────────┴───────────┘
Configuration Please use waveshare_ble400 ID for projectconf_env_board option in projectconf:
[env:waveshare_ble400] platform = nordicnrf51 board = waveshare_ble400
You can override default Waveshare BLE400 settings per build environment using board_*** option, where *** is a JSON object path from board manifest waveshare_ble400.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Waveshare BLE400 supports the next uploading protocols:
Waveshare BLE400 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.
ng-beacon Contents • ng-beacon
┌────────────────┬───────────┐ │Microcontroller │ NRF51822  │ ├────────────────┼───────────┤ │Frequency       │ 16MHz     │ ├────────────────┼───────────┤ │Flash           │ 256KB     │ ├────────────────┼───────────┤ │RAM             │ 32KB      │ ├────────────────┼───────────┤ │Vendor          │ ng-beacon │ └────────────────┴───────────┘
Configuration Please use ng_beacon ID for projectconf_env_board option in projectconf:
[env:ng_beacon] platform = nordicnrf51 board = ng_beacon
You can override default ng-beacon settings per build environment using board_*** option, where *** is a JSON object path from board manifest ng_beacon.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ng-beacon supports the next uploading protocols:
ng-beacon 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.
y5 nRF51822 mbug Contents • y5 nRF51822 mbug
┌────────────────┬───────────┐ │Microcontroller │ NRF51822  │ ├────────────────┼───────────┤ │Frequency       │ 16MHz     │ ├────────────────┼───────────┤ │Flash           │ 256KB     │ ├────────────────┼───────────┤ │RAM             │ 16KB      │ ├────────────────┼───────────┤ │Vendor          │ y5 design │ └────────────────┴───────────┘
Configuration Please use nrf51822_y5_mbug ID for projectconf_env_board option in projectconf:
[env:nrf51822_y5_mbug] platform = nordicnrf51 board = nrf51822_y5_mbug
You can override default y5 nRF51822 mbug settings per build environment using board_*** option, where *** is a JSON object path from board manifest nrf51822_y5_mbug.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading y5 nRF51822 mbug supports the next uploading protocols:
y5 nRF51822 mbug has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Nordic nRF52 96Boards Nitrogen Contents • 96Boards Nitrogen
Hardware Platform platform_nordicnrf52: The nRF52 Series are built for speed to carry out increasingly complex tasks in the shortest possible time and return to sleep, conserving precious battery power. They have a Cortex-M4F processor and are the most capable Bluetooth Smart SoCs on the market.
┌────────────────┬──────────┐ │Microcontroller │ NRF52832 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 512KB    │ ├────────────────┼──────────┤ │RAM             │ 64KB     │ ├────────────────┼──────────┤ │Vendor          │ 96Boards │ └────────────────┴──────────┘
Configuration Please use 96b_nitrogen ID for projectconf_env_board option in projectconf:
[env:96b_nitrogen] platform = nordicnrf52 board = 96b_nitrogen
You can override default 96Boards Nitrogen settings per build environment using board_*** option, where *** is a JSON object path from board manifest 96b_nitrogen.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = nrf52832
; change MCU frequency board_build.f_cpu = 64000000L
Uploading 96Boards Nitrogen supports the next uploading protocols:
96Boards Nitrogen 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.
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.        │ └─────────────────┴──────────────────────────┘
Adafruit Bluefruit nRF52832 Feather Contents • Adafruit Bluefruit nRF52832 Feather
┌────────────────┬──────────┐ │Microcontroller │ NRF52832 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 512KB    │ ├────────────────┼──────────┤ │RAM             │ 64KB     │ ├────────────────┼──────────┤ │Vendor          │ Adafruit │ └────────────────┴──────────┘
Configuration Please use adafruit_feather_nrf52832 ID for projectconf_env_board option in projectconf:
[env:adafruit_feather_nrf52832] platform = nordicnrf52 board = adafruit_feather_nrf52832
You can override default Adafruit Bluefruit nRF52832 Feather settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_nrf52832.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Bluefruit nRF52832 Feather supports the next uploading protocols:
• nrfutil
Default protocol is nrfutil
upload_protocol = nrfutil
Adafruit Bluefruit nRF52832 Feather 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_jlink  │          │ Yes     │ ├──────────────────────┼──────────┼─────────┤ │debugging_tool_stlink │          │         │ └──────────────────────┴──────────┴─────────┘
Adafruit Feather Bluefruit Sense Contents • Adafruit Feather Bluefruit Sense
┌────────────────┬──────────┐ │Microcontroller │ NRF52840 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 796KB    │ ├────────────────┼──────────┤ │RAM             │ 243KB    │ ├────────────────┼──────────┤ │Vendor          │ Adafruit │ └────────────────┴──────────┘
Configuration Please use adafruit_feather_nrf52840_sense ID for projectconf_env_board option in projectconf:
[env:adafruit_feather_nrf52840_sense] platform = nordicnrf52 board = adafruit_feather_nrf52840_sense
You can override default Adafruit Feather Bluefruit Sense settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_nrf52840_sense.json. For example, board_build.mcu, board_build.f_cpu, etc.
; change microcontroller board_build.mcu = nrf52840
Uploading Adafruit Feather Bluefruit Sense supports the next uploading protocols:
Adafruit Feather Bluefruit Sense 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.
Adafruit Feather nRF52840 Express Contents • Adafruit Feather nRF52840 Express
Configuration Please use adafruit_feather_nrf52840 ID for projectconf_env_board option in projectconf:
[env:adafruit_feather_nrf52840] platform = nordicnrf52 board = adafruit_feather_nrf52840
You can override default Adafruit Feather nRF52840 Express settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_feather_nrf52840.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Adafruit Feather nRF52840 Express supports the next uploading protocols:
Adafruit Feather 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.
Arduino Nano 33 BLE Contents • Arduino Nano 33 BLE
┌────────────────┬──────────┐ │Microcontroller │ NRF52840 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 960KB    │ ├────────────────┼──────────┤ │RAM             │ 256KB    │ ├────────────────┼──────────┤ │Vendor          │ Arduino  │ └────────────────┴──────────┘
Configuration Please use nano33ble ID for projectconf_env_board option in projectconf:
[env:nano33ble] platform = nordicnrf52 board = nano33ble
You can override default Arduino Nano 33 BLE settings per build environment using board_*** option, where *** is a JSON object path from board manifest nano33ble.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Arduino Nano 33 BLE supports the next uploading protocols:
Arduino Nano 33 BLE 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.
BL652 Development Kit Contents • BL652 Development Kit
┌────────────────┬────────────────────┐ │Microcontroller │ NRF52832           │ ├────────────────┼────────────────────┤ │Frequency       │ 64MHz              │ ├────────────────┼────────────────────┤ │Flash           │ 512KB              │ ├────────────────┼────────────────────┤ │RAM             │ 64KB               │ ├────────────────┼────────────────────┤ │Vendor          │ Laird Connectivity │ └────────────────┴────────────────────┘
Configuration Please use laird_bl652_dvk ID for projectconf_env_board option in projectconf:
[env:laird_bl652_dvk] platform = nordicnrf52 board = laird_bl652_dvk
You can override default BL652 Development Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest laird_bl652_dvk.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading BL652 Development Kit supports the next uploading protocols:
BL652 Development Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
BL654 Development Kit Contents • BL654 Development Kit
┌────────────────┬────────────────────┐ │Microcontroller │ NRF52840           │ ├────────────────┼────────────────────┤ │Frequency       │ 64MHz              │ ├────────────────┼────────────────────┤ │Flash           │ 1MB                │ ├────────────────┼────────────────────┤ │RAM             │ 256KB              │ ├────────────────┼────────────────────┤ │Vendor          │ Laird Connectivity │ └────────────────┴────────────────────┘
Configuration Please use laird_bl654_dvk ID for projectconf_env_board option in projectconf:
[env:laird_bl654_dvk] platform = nordicnrf52 board = laird_bl654_dvk
You can override default BL654 Development Kit settings per build environment using board_*** option, where *** is a JSON object path from board manifest laird_bl654_dvk.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading BL654 Development Kit supports the next uploading protocols:
BL654 Development Kit has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
Bluey nRF52832 IoT Contents • Bluey nRF52832 IoT
┌────────────────┬─────────────────┐ │Microcontroller │ NRF52832        │ ├────────────────┼─────────────────┤ │Frequency       │ 64MHz           │ ├────────────────┼─────────────────┤ │Flash           │ 512KB           │ ├────────────────┼─────────────────┤ │RAM             │ 64KB            │ ├────────────────┼─────────────────┤ │Vendor          │ Electronut Labs │ └────────────────┴─────────────────┘
Configuration Please use bluey ID for projectconf_env_board option in projectconf:
[env:bluey] platform = nordicnrf52 board = bluey
You can override default Bluey nRF52832 IoT settings per build environment using board_*** option, where *** is a JSON object path from board manifest bluey.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Bluey nRF52832 IoT supports the next uploading protocols:
Bluey nRF52832 IoT 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.
Circuit Playground Bluefruit Contents • Circuit Playground Bluefruit
Configuration Please use adafruit_cplaynrf52840 ID for projectconf_env_board option in projectconf:
[env:adafruit_cplaynrf52840] platform = nordicnrf52 board = adafruit_cplaynrf52840
You can override default Circuit Playground Bluefruit settings per build environment using board_*** option, where *** is a JSON object path from board manifest adafruit_cplaynrf52840.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Circuit Playground Bluefruit supports the next uploading protocols:
Circuit Playground Bluefruit 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.
Delta DFBM-NQ620 Contents • Delta DFBM-NQ620
┌────────────────┬──────────┐ │Microcontroller │ NRF52832 │ ├────────────────┼──────────┤ │Frequency       │ 64MHz    │ ├────────────────┼──────────┤ │Flash           │ 512KB    │ ├────────────────┼──────────┤ │RAM             │ 64KB     │ ├────────────────┼──────────┤ │Vendor          │ Delta    │ └────────────────┴──────────┘
Configuration Please use delta_dfbm_nq620 ID for projectconf_env_board option in projectconf:
[env:delta_dfbm_nq620] platform = nordicnrf52 board = delta_dfbm_nq620
You can override default Delta DFBM-NQ620 settings per build environment using board_*** option, where *** is a JSON object path from board manifest delta_dfbm_nq620.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading Delta DFBM-NQ620 supports the next uploading protocols:
Delta DFBM-NQ620 has on-board debug probe and IS READY for debugging. You don't need to use/buy external debug probe.
ElectronutLabs Blip Contents • ElectronutLabs Blip
┌────────────────┬────────────────┐ │Microcontroller │ NRF52840       │ ├────────────────┼────────────────┤ │Frequency       │ 64MHz          │ ├────────────────┼────────────────┤ │Flash           │ 1MB            │ ├────────────────┼────────────────┤ │RAM             │ 256KB          │ ├────────────────┼────────────────┤ │Vendor          │ ElectronutLabs │ └────────────────┴────────────────┘
Configuration Please use electronut_blip ID for projectconf_env_board option in projectconf:
[env:electronut_blip] platform = nordicnrf52 board = electronut_blip
You can override default ElectronutLabs Blip settings per build environment using board_*** option, where *** is a JSON object path from board manifest electronut_blip.json. For example, board_build.mcu, board_build.f_cpu, etc.
Uploading ElectronutLabs Blip supports the next uploading protocols:
Default protocol is blackmagic
upload_protocol = blackmagic
ElectronutLabs Blip 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 │ Yes      │ Yes     │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_cmsis-dap  │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_jlink      │          │         │ ├──────────────────────────┼──────────┼─────────┤ │debugging_tool_stlink     │          │         │ └──────────────────────────┴──────────┴─────────┘
ElectronutLabs Papyr Contents • ElectronutLabs Papyr