Shimmer EEPROM Branding Tool advertising / product name provisioning

Reads and writes the brand record in the sensor's EEPROM, which holds the device's Bluetooth Classic, BLE and USB names. Firmware seeds the record with the stock defaults on first boot and uses it as the single source of truth afterwards, so what you see below is what the device actually advertises. Works over USB / dock serial (Shimmer3 in a base, Shimmer3R directly over USB-C) and over BLE (Shimmer3R only — the browser cannot reach a Shimmer3 over Bluetooth). Requires firmware with DEV-949 brand-record support.

disconnected

Reboot required — the new names are stored but not yet advertised

The Bluetooth module only picks up the name at Bluetooth initialisation, and the BLE advertising name cannot change while advertising is running, so the device has to restart.
Reboot now arms a soft reboot and disconnects — the device restarts by itself as the link drops, then advertises the new names.
This connection cannot request a soft reboot (dock/USB serial has no such command), so power-cycle the sensor by hand:
  1. Disconnect this tool (button below or unplug).
  2. Shimmer3: undock and re-dock it (or briefly press the reset pin through the enclosure hole). Shimmer3R: hold the button to power off, then on again, or undock/re-dock.
  3. Reconnect here and press Read record to confirm, or check a Bluetooth scan for the new name.

Current record not read

Classic BT prefix
–
BLE prefix
–
USB product prefix
–
USB manufacturer
–
Record type
–
Device
–
MAC suffix
–
An invalid or blank record is not an error state: firmware replaces it with the stock defaults at the next boot.

Provision new branding

Printable ASCII, no commas. Max lengths: Classic BT and USB product 16, BLE 10 (Shimmer3: 8 — the 31-byte BLE advertisement limit), USB manufacturer 24. Firmware appends the MAC suffix to the Classic BT, BLE and USB product names; the USB manufacturer string is used verbatim, and a stock unit carries "Shimmer Research Ltd." here.

The record is never write-protected — it stays rewritable and erasable from this page at any time. Writes are CRC-protected; a garbled record simply reverts to the stock defaults at the next boot.
Log