MultiNav Pro+ BLE - white-label firmware build, any experience stripping RFOXiA branding?

@Stephanie Williams good timing on this — the MultiNav Pro+ firmware is actually open source, so you're not fighting a locked binary here. The GitHub repo is at https://github.com/RFOXiA/MultiNav-Pro-Long-Range-BLE-Module-Firmware-STM32WB07, which means you can go straight to the source and strip or replace whatever's in the advertisement configuration.

 

Since it's running on the STM32WB07, the BLE stack is ST's own implementation, so the GAP device name, ad payload structure, and manufacturer-specific data fields are all configurable in the firmware the same way you'd expect on any ST wireless project — no Nordic-specific quirks to worry about, but the pattern is similar enough that your existing experience will transfer. You're looking for the advertisement data setup, probably in an `app_ble.c` or similar file depending on how they've structured the project.

 

If you want to avoid touching the core firmware at all, it's also worth checking whether the AI Firmware Builder in the Dev Hub can generate a white-label variant for you — describe exactly what you need and it'll spit out source you can build from. Might save you some time vs. manually hunting through the codebase cold.

Hey, so the MultiNav Pro+ BLE does expose GAP device name and the manufacturer-specific data payload through the AT command interface - AT+BTNAME and AT+MFRID respectively - so you can overwrite those without touching the firmware directly. The default advertisement name is baked into the config partition though, not flash-locked, so as long as you're doing a factory config wipe before shipping you should be clean from a scanner's perspective. Haven't personally tested every field (RSSI calibration data still had an RFOXIA string in it last I checked) so worth doing a full Wireshark BLE capture before you hand off to the client.