-
Notifications
You must be signed in to change notification settings - Fork 2k
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
drivers/at86rf215: Incorrect channel number set for subGHz #15906
Comments
Can confirm it happens, seems to be that for now only EU 868–870 MHz band is supported, although it should still allow to specify at least one of the 3 channels available for this band on O-QPSK, probably not yet implemented as getting the channel scheme is quite tricky and the channel spacing is not defined clearly on the IEEE 802.15.4-2015 Std. The difference between channel 0 and 1 is 650 kHz, and between 1 and 2 it's 575 kHz. RIOT/drivers/at86rf215/at86rf215_o-qpsk.c Lines 30 to 32 in 09ca07e
The limitation happens here and hence the reason it defaults to channel 0: RIOT/drivers/at86rf215/at86rf215_o-qpsk.c Line 344 in 09ca07e
|
Description
Inside the
at86rf215_reset_and_cfg()
function, the channel number for subGHz radio is set toCONFIG_AT86RF215_DEFAULTL_SUBGHZ_CHANNEL
(5) at the start ofat86rf215_reset_and_cfg(dev)
function but is later set to zero while initialising the modulation for the radio in_end_configure_OQPSK(dev)
.This stops the user from using a channel number since
_end_configure_OQPSK(dev)
will always set the channel number to 0.Steps to reproduce the issue
Run the basic gnrc_networking example and execute the command
ifconfig
on the shell to see the interface configuration.Hardware used:
Board: nucleo-l476rg
Radio: at86rf215
Expected results
The channel number is set to the number in
CONFIG_AT86RF215_DEFAULTL_SUBGHZ_CHANNEL
(or a valid number isCONFIG_AT86RF215_DEFAULTL_SUBGHZ_CHANNEL
isn't valid)Actual results
Versions
The text was updated successfully, but these errors were encountered: