Skip to main content
Your own design, a reference board, a development kit, or a product bought off the shelf. If the chip is one of these, the agent can work on it.
The chip is what matters, not the board. There is no list your board has to be on. Open your project and the agent reads it: your devicetree, your Kconfig, your build settings, and the hardware you have connected.

​
Nordic

Built with the nRF Connect SDK and Zephyr. Two tools come with the cellular parts: a board shell that speaks AT and Zephyr commands, and a modem trace that says why a modem will not attach. LoRa and LoRaWAN need a Semtech radio on the board, wired over SPI: an SX126x, an SX127x or an LR2021. The node path is verified on an nRF52840 with an SX1262. See LoRa and LoRaWAN.
DECT NR+ and NTN knowledge ships for both. NTN’s modem firmware runs only on an nRF9151 of the LACA A1A revision, not on LACA A0A, the nRF9161, the nRF9131 or the nRF9160. DECT NR+ needs a modem image from Nordic sales rather than a download.

​
Espressif

Built with ESP-IDF.

​
What is next

New chips and radios ship at the chip level, so every board built on them inherits the support. See the roadmap. If a chip you use is missing, tell us. It is the most useful thing you can send.

​
Some devices go further

On a few boards the work is already done: pinouts, which card carries which radio, which connector programs which chip, written down and tested on the bench. Those are boards whose makers publish their designs and work with us.

Partner open hardware

Why published designs make this possible, the boards it covers today, and what it would take to add yours.