Unique devices name

[zhovner]

As with Flipper Zero, we want Flipper One to have a unique name that is programmed during production and cannot be erased, equivalent to a serial number.

Where to store the name?

We need to choose where to store the name. It should be some kind of OTP memory. Ideally, the name should also be readable in MCU mode, but this is not mandatory. Depending on the storage location, the format and maximum length will be defined.

How the name will be used

• Default Wi-Fi network name, for example Flipper One P00per
• Hostname in the DHCP client: flipperone-p00per
• etc.

[johan-wd]

I would say don't store use as name FlipperOne-[lastsix] of macaddress
Then you have it for ethernet port and wifi two names but you can easy find them at the routing table off a nework, or choose one off these to be the main name

[VoidChecksum]

The RK3576 already ships with a 16-byte factory-programmed unique ID in non-secure OTP, so there may be nothing new to burn on the SoC side. Mainline has full support since the 6.15 cycle (RK3576 OTP series); rk3576.dtsi exposes it as nvmem cell id@a (reg = <0x0a 0x10>) on the rockchip,rk3576-otp controller.

@johan-wd's MAC idea points the right direction (derive, don't store), but the MAC is downstream of this same ID anyway — U-Boot's arch/arm/mach-rockchip/board.c reads the cpuid from OTP, sets cpuid#/serial#, and generates ethaddr from sha256(cpuid). Hex tails also aren't memorable, which is half the point of the Zero's names.

Proposal: name = f(OTP ID), deterministic

id   = otp_id nvmem cell (16 bytes, burned at fab)
h    = SHA-256("flipper-one-name-v1" || id)
adj  = adjectives[ be16(h[0:2]) % 256 ]
noun = nouns[ be16(h[2:4]) % 256 ]
name = leet(adj + noun)        # "P00per"-style substitutions

Properties:

• Immutable and unerasable by construction — it's a pure function of fab-burned OTP. No production-line write step, no write-locking story, nothing a user can corrupt.
• 256×256 wordlist = 16 bits. Birthday collisions start around ~300 units, so for fleet-scale uniqueness append 2 base32 chars of h[4:5] (→ ~26 bits, collision-free into the millions). Collisions are cosmetic anyway since the real identity is serial#.
• Same derivation runs anywhere the ID is readable, so every consumer agrees without coordination.

MCU mode: the SoC OTP isn't readable when the RK3576 is off. Fix at production: compute the name once, flash it into the MCU's OTP exactly like the Zero does today (scripts/otp.py second block, 8-char a-zA-Z0-9 limit at 0x1FFF7010 — assuming the One's MCU keeps that scheme). Deterministic derivation means both copies agree forever. If the 8-char MCU limit stays, constrain wordlists so adj+noun ≤ 8 chars, Zero-style.

Linux plumbing (one first-boot generator unit reading the nvmem cell, idempotent):

• /etc/hostname → flipperone-p00per (DHCP option 12, mDNS via avahi — free)
• /etc/machine-info → PRETTY_HOSTNAME="Flipper One P00per" — BlueZ picks this up via hostnamed for the adapter name, free again
• hostapd ssid=Flipper One P00per
• USB gadget: iProduct/iSerialNumber from name + serial#
• /proc/device-tree/serial-number already works — U-Boot's root fixup writes serial# there

Open question: does the MCU OTP layout carry over from the Zero, or is there a bigger field available? That decides whether the wordlists need the 8-char constraint.