Web J-Link Flasher: Requirements and Firmware Guide
Use WebUSB and SWD to connect a J-Link probe and load BIN or Intel HEX firmware. This browser workflow does not require a local flashing server, but USB driver configuration may still be needed.
Requirements and Compatibility Limits
Use a desktop browser that exposes WebUSB over HTTPS or localhost. Connect the probe to the target’s SWDIO, SWCLK, ground and voltage-reference connections according to the probe and board documentation. Confirm target power and voltage compatibility.
The selector includes STM32F103, STM32F401/F411, nRF52832 and nRF52840 presets. A listed preset is not evidence of a hardware-tested configuration. In the current implementation, erase and programming branches exist for STM32F1 and nRF52; STM32F4 flash operations are not implemented. Do not use the STM32F401/F411 presets for flashing.
No physical board/probe validation matrix is published here. Compatibility depends on the probe, target and system; use the chip vendor’s supported programming tool where this implementation does not cover your configuration.
How to Prepare a Flashing Session
- Confirm the supported target family, firmware and SWD wiring before connecting.
- Close J-Link Commander, Keil, Ozone and other software that may own the probe.
- Connect in the browser and select the matching target preset.
- Load a HEX or BIN file and inspect every displayed segment address. Select the target before loading a BIN; reload the BIN if the target changes.
- Only start the erase-and-flash operation when the addresses and target match. This workflow performs a mass erase before writing and then requests a target reset.
BIN and Intel HEX Address Handling
Intel HEX records include addresses; the tool parses them into segments. A BIN file has no embedded load address. This interface places it at the selected preset’s flash base: 0x08000000 for the listed STM32 presets or 0x00000000 for the listed nRF52 presets.
There is no arbitrary BIN offset field in this interface. If your application belongs after a bootloader or at another address, do not flash that BIN at the preset base. Use an appropriately addressed HEX file or a programmer with explicit address control. Mass erase may remove existing application data and bootloader contents; this interface has no backup workflow.
USB Driver and Connection Troubleshooting
An interface-claim error can mean the probe is in use or its current driver prevents WebUSB access. Close other tools first. On Windows, some configurations require binding the intended J-Link interface to WinUSB.
Changing an interface driver can affect native SEGGER tools. Confirm the correct interface and how to restore its original driver before changing it. Driver changes are not required on every system.
If USB connects but SWD does not, check target power, reference voltage, wiring and target protection settings. A completed browser progress bar does not substitute for independent firmware verification.
Frequently Asked Questions
Does this support every STM32 or nRF52 device?
No. The presets and implemented flash branches define a limited scope. In particular, the listed STM32F4 presets currently lack erase/program implementations. No universal device or probe compatibility is claimed.
Does flashing preserve existing firmware and settings?
The workflow invokes mass erase before programming. Do not rely on it to preserve an existing application, bootloader or settings in erased flash.
Can I flash an ESP32 with J-Link here?
This page’s presets do not implement ESP flashing. Use the ESP Firmware Flasher for compatible serial download workflows.