UF2 converter and inspector
Drop a UF2 to see what is inside and save it as a .bin, or drop a .bin, choose the chip family and address, and get a UF2 to copy to the board's drive. Like uf2conv.py, without Python.
A UF2 is read and can be saved as .bin; a .bin becomes a UF2 for the family and address above.
Addresses
- RP2040 and RP2350: flash starts at 0x10000000. An app behind a bootloader starts where its partition does, for example 0x10010000 for slot 0 behind a 64 KB MCUboot.
- ESP32-S2, S3, C3 with TinyUF2: addresses are offsets into the app partition, starting at 0.
- nRF52840 with Adafruit's bootloader: after the SoftDevice, 0x26000 or 0x27000 depending on its version.
- SAMD21 and SAMD51: after the UF2 bootloader, 0x2000 and 0x4000.
On the RP2350, picotool adds one block of the "absolute" family to work around erratum E10; the inspector shows it separately. Files never leave your browser.
Updating boards without the drive
Copying a UF2 needs the board on USB. Pinscope on the Pico 2 W sends the UF2 over the internet into the other A/B partition, boots it on trial and keeps it only when it comes back online.
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?
- Raspberry Pi Pico 2 W: remote access, logs and OTA over the internet
- Zephyr fatal error decoder
- Cortex-M HardFault decoder
- MCUboot image inspector
- Zephyr flash partition checker
- Memfault vs Pinscope: which one fits
- Golioth vs Pinscope: which one fits
- nRF Cloud vs Pinscope: which one fits