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.

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

Board resets when sending message using default access class at index 1 set to normal rate. #114

Open
Dond96 opened this issue Dec 7, 2021 · 6 comments

Comments

@Dond96
Copy link

Dond96 commented Dec 7, 2021

I ran into a bug where the B-L072Z-LRWAN1 board would reset when sending a message using access class 1 to normal rate. the code below would cause the board to reset using access class 0x11 in the session config.

dae_access_profile_t profile;
d7ap_fs_read_access_class(1, &profile);
profile.channel_header = (channel_header_t)
{
  .ch_class = PHY_CLASS_NORMAL_RATE,
  .ch_coding = PHY_CODING_FEC_PN9,
  .ch_freq_band = PHY_BAND_868
};
d7ap_fs_write_access_class(1, &profile);

d7ap_send(args); 
@LOorts-Aloxy
Copy link
Member

do you have any logs of this? did the board assert somewhere?

@Dond96
Copy link
Author

Dond96 commented Dec 7, 2021

Nope didn't get an assert the board would just reset and print the logs from the bootstrap function again.

@LOorts-Aloxy
Copy link
Member

hmmm ok, normal rate is automatically being tested, but these tests are very basic. We're not testing low power listening (which is default for access class 0x11) combined with normal rate at this time. Could be that there's still an issue there.

@LOorts-Aloxy
Copy link
Member

and what is the reboot reason when the device reboots?

@Dond96
Copy link
Author

Dond96 commented Dec 7, 2021

It didn't show a reason it just rebooted. But I just switched to lo-rate for the background message now because I don't need to increased data speed for that.

@LOorts-Aloxy
Copy link
Member

normally one of the first messages when booting is "rebooted with reason X" which should show you the reboot reason. but if it's fixed like this for now, that's also great :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants