-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature] Remember more than 4 hosts #37
Comments
Why can't we recover the BLE firmware? |
from what I heard in #dev-chat: when @ah- tried dumping the BLE fw via serial, there was rust strings in the output, so nobody trusted that the ouput was correct. |
And related: We do get info back via AckHostListQuery, which is three bytes. The last is a bool if it's legacy or ble, and I think the first byte is a set of bits if there's a host saved, and the second byte is whether it's connected to any of those hosts. Haven't looked in detail though. Some examples:
|
with 9b1a92b...c44cf25 |
Maybe? All that is just based on the same guessing :) Haven't tried what happens if you add a 5th host, currently busy with other parts. Upper limit is 8, due to the bit field that comes back. It's a bit suspicious that "connected, but not to a saved host" is 12. |
Caution We don't have any way to recover BLE fw yet, this might brick it?
BleOp::ConnectHost/SaveHost/DeleteHost
accepts a byte argument, but how well do values beyond 0-3 work?The text was updated successfully, but these errors were encountered: