Hi
I’m not sure if it is a bug or not. but seems a bug or something is weird. this error was the first time I came across it,
sequentially, I am executing these commands;
- lr11xx_wifi_scan_time_limit
- lr11xx_wifi_get_nb_results
lr11xx_wifi_get_nb_results this command sometimes returns 0 or 13(hex) in nbresult byte. I’m sure it should be 0 and whenever I read 13 and the status byte was always CMD_PERR (3) and I can understand that nbresult byte value is wrong and must ignore it. However, one time I got the status byte 5 with nbresults 13. Now I am really confused.
here is a write command output for the nbresult
here is a read command output below for nb result. as seen in the first byte the status indicator shows the last command was processed successfully. but I got 13 as nbresult byte.
I’m wondering why I get sometimes 13 sometimes 0. there is no problem with the status indicator when I got nbresult byte as 0.
