NiusCrypto targets all nrf52 boards in the ArduinoNRF package. Public API
details: API_REFERENCE.md. Local compile checks should cover at least:
| FQBN | Role |
|---|---|
arduinonrf:nrf52:promicro_nrf52840:bootloader=autonosd |
HW reference (board1) — clone @ 0x1000, J-Link + COM18 |
arduinonrf:nrf52:xiao_nrf52840 |
Different UF2 layout (0x27000 S140 v7); compile-only until HW available |
arduino-cli compile \
--fqbn arduinonrf:nrf52:xiao_nrf52840 \
--library /path/to/ArduinoNRF-Crypto \
examples/CryptoSelfTestCC310 hardware tests require vendored blobs on the build machine (setup_vendored.py).
| Board | CryptoSelfTest | CC310Smoke | Notes |
|---|---|---|---|
| ProMicro nRF52840 (board1) | 23/23 PASS | BleCryptoStress OK | MBR-only @ 0x1000, COM18 |
| Seeed XIAO nRF52840 | compile-only | compile-only | Awaiting HW in lab |
When a second board is available, run the local verify script with an adjusted FQBN:
powershell -File vendor\hwverify\verify_board1.ps1 -Fqbn 'arduinonrf:nrf52:xiao_nrf52840:uploadmode=jlink'(adjust -ComPort for that board's data CDC).