Zephyr flash partition checker

Paste build/zephyr/zephyr.dts, a board .dts or your overlay, and see the flash partitions laid out, with what MCUboot and the settings subsystem need checked: overlaps, sector alignment, equal slots, a storage partition big enough for NVS.

What it checks

• No two partitions overlap, and each starts and ends on an erase sector: erasing one must not erase its neighbour.
• MCUboot: a boot_partition, a slot0_partition and a slot1_partition of the same size for the swap modes, and enough room for a bootloader that checks signatures.
• A storage_partition of at least two sectors, for NVS or ZMS settings.
• Everything fits the flash, with slots on external flash shown on their own map.

Use the full build/zephyr/zephyr.dts for the real layout: it has the board's partitions and your overlay's changes merged. Nothing is uploaded.

Updates over the internet

With the slots right, Pinscope's Zephyr module takes zephyr.signed.bin from the dashboard to devices anywhere and lets MCUboot test it.

Try it

Three devices are free, and no card is needed. Create an account, or read the guide for your platform: ESP32, Zephyr, Raspberry Pi Pico, Linux, ESP8266.

More

• Remote access to an ESP32 without TLS: what it measured and what it costs
• Serial monitor in the browser for ESP32 and Zephyr, with crash decoding
• Pinscope now runs on Zephyr, Raspberry Pi Pico, Linux and ESP8266
• Zephyr devices in the field: logs, crashes and OTA over the internet
• Reading a Zephyr fatal error: fault, reason, CFSR and call trace
• MCUboot: are your images signed with the public development key?
• Zephyr fatal error decoder
• Cortex-M HardFault decoder
• MCUboot image inspector
• UF2 converter and inspector
• Memfault vs Pinscope: which one fits
• Golioth vs Pinscope: which one fits
• nRF Cloud vs Pinscope: which one fits
• Memfault, Golioth, nRF Cloud and Pinscope compared