See inside every Zephyr device you ship.

A Zephyr module that reaches your devices wherever they are installed: their web server over HTTPS, LOG_* output live and stored, fatal errors decoded, and MCUboot updates from the dashboard. Two lines in prj.conf, no code.

Adding it

CONFIG_PINSCOPE=y
CONFIG_PINSCOPE_PROJECT_KEY="psk_..."

What you get

• Its web server from anywhere: an HTTPS address for the HTTP server already on the device, behind your login, a share link or an API token. No port forwarding, no VPN.
• Logs: live and stored, searchable, from the device's normal log output.
• Health: memory, stack, signal, uptime and restarts without code, and your own numbers with one call.
• Crashes: kept across the reboot and decoded with the ELF of the build.
• Updates: from the dashboard, with the platform's own fallback when the new firmware does not come back.
• Alerts: email or webhook when a device goes offline or crashes.

Free tools

• ESP32 serial monitor
  A serial monitor in Chrome or Edge: colored log levels, reset, filter, errors explained and ESP32 or Zephyr crashes decoded live with your ELF.
• Zephyr fatal error decoder
  Paste a Zephyr fatal error and zephyr.elf: the reason by name, every CFSR and HFSR bit explained, and the call trace as functions and lines.
• Cortex-M HardFault decoder
  Paste a CFSR value or a fault dump and get every MemManage, BusFault and UsageFault bit explained, with PC and LR decoded from your ELF.
• MCUboot image inspector
  Drop zephyr.signed.bin to see its header, version and TLVs, check its hash as MCUboot does, and spot images signed with the public dev key.
• UF2 converter and inspector
  Convert .bin to UF2 for RP2040, RP2350, ESP32-S2/S3, SAMD, nRF52840 or STM32, convert UF2 back to .bin, and see what a UF2 contains.
• Zephyr flash partition checker
  Paste zephyr.dts or an overlay: the flash partitions on a map, overlaps, sector alignment, MCUboot slot sizes, scratch and the storage partition for settings checked.

Guides

• Remote access to an ESP32 without TLS: what it measured and what it costs
  Why the Pinscope device component uses the Noise protocol instead of TLS, what it measured on an ESP32-S2, and what that choice costs.
• Pinscope now runs on Zephyr, Raspberry Pi Pico, Linux and ESP8266
  Remote access, logs, crash reports and OTA updates, as on the ESP32, now for Zephyr, the Pico 2 W, Linux and the ESP8266. About 9 KB of RAM.
• Zephyr devices in the field: logs, crashes and OTA over the internet
  Logs, fatal errors and metrics of Zephyr devices in the field, their web server, and MCUboot updates over the internet. Two lines in prj.conf.
• Reading a Zephyr fatal error: fault, reason, CFSR and call trace
  What ">>> ZEPHYR FATAL ERROR" and the Cortex-M fault lines mean: reason codes, CFSR and HFSR bits, and the call trace as functions and lines.
• MCUboot: are your images signed with the public development key?
  Zephyr sysbuild signs MCUboot images with a development key whose private half is public. How to check an image and switch to your own key.
• Memfault vs Pinscope: which one fits
  Memfault and Pinscope side by side: what each does, which devices they support, how they are priced, and when each one is the better choice.
• Golioth vs Pinscope: which one fits
  Golioth and Pinscope side by side: device management services, supported SDKs, usage-based versus fixed pricing, and when each fits.
• nRF Cloud vs Pinscope: which one fits
  Nordic's nRF Cloud and Pinscope side by side: chips supported, FOTA and lifetime licences, location, remote access, and when each fits.
• Memfault, Golioth, nRF Cloud and Pinscope compared
  Device management and observability for embedded fleets compared: Memfault, Golioth, nRF Cloud and Pinscope, by features, platforms and pricing.
• The Cyber Resilience Act, for the devices you ship
  What the EU Cyber Resilience Act asks of device makers, and when: an SBOM, handling vulnerabilities, security updates, a support period, reporting. What Pinscope does for it, and what it does not.
• SBOMs and known vulnerabilities for ESP32 and Zephyr firmware
  Pinscope now keeps the SBOM of each build, checks it against the NVD every day with the same matching as idf.py sbom-check, and shows which devices run an affected build.

Other platforms: ESP32 · Raspberry Pi Pico · Linux · ESP8266