Flash UltraWideLock from your browser.

Already have a board running UltraWideLock? Update it from this page — over Bluetooth with no cable at all, or down a USB cable, which is about three times faster. Either way the board is identified first, so you find out what applies to it before you go and press anything on it.

A DWM3001CDK also offers reinstall everything over USB. That one writes a whole image through the bootloader instead of a patch through the application, so it is the option to reach for when a board no longer starts — it does not need the software on the board to be working, or even present.

Two limits worth knowing before you rely on this. The DWM3001CDK has a single MCUboot slot, so what travels over the air is a signed delta against the exact bytes already on the part — about 11 KB. That means a board running a build we publish no delta from has no over-the-air path at all, and the page will say so rather than pretend. And nothing is written until you open the update window on the board itself — SW2 on the CDK, a double-click on the ESP32's button. That gesture is the only thing standing between the lock and anyone else in radio range, so it cannot be done from here. The ESP32 has two full OTA slots and so takes a whole image rather than a delta: about 2 MB over Bluetooth, which is several minutes with the tab open.

• A Qorvo DWM3000EVB (DW3110) — the UWB radio, hand-wired over SPI
• 11 jumper wires and a USB data cable
• Chrome or Edge on a computer. WebSerial is a Chromium API: Firefox has never shipped it, and neither Safari nor any mobile browser has, so those cannot flash.

Apple side: an iPhone with a UWB chip (iOS 26 is the validated floor), a Home hub (HomePod or Apple TV), and a 2.4 GHz Wi-Fi network.

1. Wire the UWB radio

   first

   Check the DWM3000EVB's power-select jumper before anything else. Wrong source and the radio fails silently — no device ID, a deaf responder — which looks exactly like a software fault. It cost days on the bench once.

   Power the EVB from 3V3, not 5 V (the DW3000 is a 3.3 V part), share ground, and wire:

   Pin map per chip. Scroll sideways for the C5 and C6 columns on a narrow screen.

   EVB pin	Signal	ESP32-S3	ESP32-C5	ESP32-C6
   D13	SCLK	GPIO12	GPIO8	GPIO6
   D11	MOSI	GPIO11	GPIO9	GPIO7
   D12	MISO	GPIO13	GPIO23	GPIO2
   D10	CS	GPIO10	GPIO10	GPIO10
   D8	IRQ	GPIO5	GPIO5	GPIO3
   D7	RSTn	GPIO4	GPIO4	GPIO1
   D9	WAKEUP	GPIO6	GPIO6	GPIO0
   3V3	power	3V3 on all three — never 5 V
   GND	ground	GND
   D1	SPI-POL	GND (mode-0 strap)
   D0	SPI-PHA	GND (mode-0 strap)

   The C5's data pins differ because the S3's GPIO11/12 are the C5's UART0 console and GPIO13 is its USB-Serial-JTAG. The C6 uses GPIO6/7/2 because those are SPI2's direct IO_MUX pins on that part, with the control signals kept clear of its strapping pins, its USB Serial/JTAG pair and UART0.

   The two straps hold the DW3000 in SPI mode 0. Skip them if your EVB revision already fixes the mode — check its manual.

2. Write the firmware

   Plug the board in over USB, click Install, and pick its serial port. One merged image — bootloader, partition table and app — is written in a single pass. Reflashing wipes any previous commissioning either way; “erase device” also clears everything beyond the image, which is the safe pick on a used board.

   Board Auto-detect (recommended)
   Connect & install ⚠ This browser cannot flash over WebSerial. Use Chrome, Edge, or Firefox on a computer — Safari and mobile browsers do not support it. ⚠ WebSerial needs a secure page. Open this page over https (or localhost) and try again.
   standby no board 0%

   0x000000image end

   1. 0x000000bootloader48 KB
   2. 0x00C000partition table4 KB
   3. 0x00D000esp_secure_cert8 KB
   4. 0x010000nvs48 KB
   5. 0x01C000nvs_keys4 KB
   6. 0x01D000otadata8 KB
   7. 0x01F000phy_init4 KB
   8. 0x020000ota_0 (app)rest of image

   Nothing written yet. The write runs left to right from 0x000000. The seven regions ahead of the app cover the first 128 KB; ota_0 is everything after 0x020000.

   No port in the list? Use a data cable rather than a charge-only one, or hold the board's BOOT button while plugging it in, then retry. After a BOOT-button flash, replug before first boot.

3. Pair it

   The board comes up advertising for commissioning, and this is its setup code. It is the same on every board flashed from this page: the image builds with Matter's test setup parameters, so the passcode and discriminator are fixed rather than per-device. Scan it with the iPhone you want to carry the key, or type the digits into Home.

   Manual pairing code

   3497-011-2332

   QR payload

   MT:Y.K9042C00KA0648G00

   The board prints the same two lines on its console at every boot, and codes reprints them. If this page and the board ever disagree, the board is right.

4. First boot

   1. In Home: add accessory, scan the code above or type the 11 digits. Keep the phone next to the board; commissioning starts over BLE, then joins your 2.4 GHz Wi-Fi. Expect a minute or two. There is no Improv Wi-Fi step — the network join happens during commissioning.
   2. To watch it go, open a serial console at 115200 baud. The installer's “Logs & Console” option works, or screen /dev/cu.usbmodem… 115200 on macOS, screen /dev/ttyACM0 115200 on Linux, PuTTY on Windows. The boot log ends at a matter> prompt.
   3. Home warns about an uncertified accessory, because the image carries test certificates. Add it anyway.
   4. Home then provisions the key into Wallet on its own. Walk up: the Wallet animation plays, the lock opens, and it relocks as you leave.

   The matter> console also has status, range, lock/unlock, and factoryreset.

More depth: the bring-up checklist and the known traps.