-
Notifications
You must be signed in to change notification settings - Fork 120
IEEE 802.15.4 Examples and API Fixes #587
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
base: master
Are you sure you want to change the base?
Conversation
The kernel exposese two 15.4 drivers, a standard driver and a phy driver. The standard driver takes a payload and other fields and forms the headers/handles encryption. The phy driver transmits "raw" payloads. - Update naming of examples / functions to specify using raw interface.
98788b7 to
d0c6f47
Compare
|
I realized that the existing |
The ieee802154_rx_raw and ieee802154_rx_tx apps expect a packet of the form "frame XXXX" where XXXX encodes the frame number using the last four bytes. This fixes the parsing logic to correctly display this information.
|
I've confirmed that the When testing, I noticed some issues with the parsing logic (which have now been fixed). Should be good to merge on my end. I see some CI failures, but those look like they are not relevant to me? |
|
Hm, it really looks like we ought to have a |
Or upgrade to edition 2024. |
IEEE 802.15.4 Examples and API Fixes
This PR updates the
libtock-rs15.4 API to account for the Phy/Standard 15.4 drivers in the kernel.For context, the kernel has two 15.4 driver interfaces (that are mutually exclusive): a standard 15.4 driver and a Phy driver. The standard driver accepts payloads and forms the frame (adding headers, handling encryption, etc.). The Phy driver takes a buffer and transmits this buffer without modification.
The existing 15.4 API uses the standard driver. However, this driver does not expose functionality for things such as setting the channel or tx power (resulting in the errors in #586).
Changes
TODO