Nrf52 are great BLE chips, however the full bluetooth spec (classic+BLE) is orders of magnitude more complex...
Sadly that's common in the hardware world. Step 1. Have a reliable hardware watchdog that restarts everytime there's a software problem. Step 2. There is no step 2.
Correct. It's a small table of: address1, 4 bytes overlay data address2, 4 bytes overlay data etc The data is overlayed over the specified addresses, in runtime. On some chips its 8 bytes instead of 4. On a typical…
It's shipped in Android 11, but in disabled state. On Pixel, developer options, bluetooth, enable "Gabeldorsh" if you want to live on the bleeding edge.
> fighting Broadcom's old, god-awful bluetooth code Correction: god-awful host side bluetooth code. There is still the bluetooth firmware residing on the BCMxxx chip (or Qualcomm chip) - >1MB of god-awfulerer…
Nrf52 are great BLE chips, however the full bluetooth spec (classic+BLE) is orders of magnitude more complex...
Sadly that's common in the hardware world. Step 1. Have a reliable hardware watchdog that restarts everytime there's a software problem. Step 2. There is no step 2.
Correct. It's a small table of: address1, 4 bytes overlay data address2, 4 bytes overlay data etc The data is overlayed over the specified addresses, in runtime. On some chips its 8 bytes instead of 4. On a typical…
It's shipped in Android 11, but in disabled state. On Pixel, developer options, bluetooth, enable "Gabeldorsh" if you want to live on the bleeding edge.
> fighting Broadcom's old, god-awful bluetooth code Correction: god-awful host side bluetooth code. There is still the bluetooth firmware residing on the BCMxxx chip (or Qualcomm chip) - >1MB of god-awfulerer…