fix BLE upload: use g_bleFlashStart for correct track address and byte count on finalize
This commit is contained in:
@@ -75,3 +75,13 @@ and reuse `ble.js`'s protocol constants.
|
||||
local name just shows "Track N".
|
||||
- **MTU:** data is chunked to 180 bytes to stay within a modest negotiated ATT
|
||||
MTU (firmware char max is 240).
|
||||
- **Name shows as "BabyM" (truncated):** the 128-bit service UUID fills the 31-byte
|
||||
advertisement, leaving room for only 5 name characters. The browser can't read
|
||||
the full GAP name (that service is blocklisted in Web Bluetooth). Fix it in the
|
||||
firmware by moving the name to the scan response, which has its own 31 bytes:
|
||||
replace `Bluefruit.Advertising.addName();` with `Bluefruit.ScanResponse.addName();`.
|
||||
- **Reconnecting after a disconnect:** a just-disconnected peripheral leaves the
|
||||
link half-open briefly, so the first reconnect could fail until a page refresh.
|
||||
`connect()` now retries (3×, 600 ms backoff) after an explicit disconnect, which
|
||||
recovers without refreshing. Scanning matches on the service UUID first, so a
|
||||
truncated advertised name no longer breaks the name filter.
|
||||
|
||||
Reference in New Issue
Block a user