Skip to content
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.

Sign up for GitHub

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

Fix dead link building-apps-bluetooth-specs.md #69

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix dead link building-apps-bluetooth-specs.md #69

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions frame/building-apps-bluetooth-specs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ Sometimes it may be more efficient to send raw byte data rather than strings. Fo

Raw byte data can also be returned to the host device using the `frame.bluetooth.send()` function. This data is also limited to MTU - 4 bytes in length, and will be prepended by a value of `1` in the first byte of the payload.

If you are using the SDK and want to await multiple chunks of data from the Frame sent via `frame.bluetooth.send()`, you can use the [`frame.bluetooth.wait_for_data()` function](building-apps-sdk#Wait-For-Data). In that case, prepend each chunk with a value of `1` in the first byte (`'\001'` or `'\x01'`) and send a final chunk with a value of `2` (`'\002'` or `'\x02'`). You can optionally include the total chunk count in the final message for reliability checking (for example, if you send 3 data chunks, then the final message should be `'\0023'`). Note that this functionality only exists in the SDK, so if you are manually sending data over Bluetooth, you will need to implement your own logic to handle multiple chunks.
If you are using the SDK and want to await multiple chunks of data from the Frame sent via `frame.bluetooth.send()`, you can use the [`frame.bluetooth.wait_for_data()` function](/frame/building-apps-sdk/#wait-for-data). In that case, prepend each chunk with a value of `1` in the first byte (`'\001'` or `'\x01'`) and send a final chunk with a value of `2` (`'\002'` or `'\x02'`). You can optionally include the total chunk count in the final message for reliability checking (for example, if you send 3 data chunks, then the final message should be `'\0023'`). Note that this functionality only exists in the SDK, so if you are manually sending data over Bluetooth, you will need to implement your own logic to handle multiple chunks.

### Bluetooth Raw Data Exchange Sequence Diagram

Expand All @@ -99,4 +99,4 @@ If no activity commences on the bootloader for more than 5 minutes, it will time

Unlike the application firmware, the bootloader will continue to operate even while Frame is on charge. It's therefore possible to update while the device is docked to the charging cradle. In this case, once the update completes, the firmware will reload and then go to sleep right away.

The latest release file of the official firmware is available from the [Frame codebase releases page](https://github.com/brilliantlabsAR/frame-codebase/releases) which you can include in your own host apps along with the DFU mechanism.
The latest release file of the official firmware is available from the [Frame codebase releases page](https://github.com/brilliantlabsAR/frame-codebase/releases) which you can include in your own host apps along with the DFU mechanism.