SX126x sleep() function takes always 5 seconds about radiolib HOT 6 CLOSED

Extension after wondering why it is always 5 seconds to return from sleep().
From the datasheet

9.3 Sleep Mode
In this mode, most of the radio internal blocks are powered down or in low power mode and optionally the RC64k clock
and the timer are running. The chip may enter this mode from STDBY_RC and can leave the SLEEP mode if one of the
following events occurs:
• NSS pin goes low in any case
• RTC timer generates an End-Of-Count (corresponding to Listen mode)
When the radio is in Sleep mode, the BUSY pin is held high.

Which means when you send the sleep command, BUSY will go high and held high until the chip wakes up again. So the SPIwriteCommand will always go to timeout with the current implementation.
I want to move this from feature request to bug-fix. Wait for busy should be always false for the sleep() command.

from radiolib.

You're right, obviously it makes no sesnse to wait for BUSY to drop low in sleep mode. That's probably why I added the waitForBusy parameter - and then forgot to actually use it...

from radiolib.

Should be fixed in a04a376, release later today or tomorrow.

from radiolib.

Thanks!

Let's see what else I stumple upon 😉

from radiolib.

More bugs, probably - I was in bit of a hurry when writing the SX126x driver ;)

from radiolib.

@jgromes
Before you make a release, I would have an enhancement to Sx126x driver - possibility to set a sync word length in bits. I just have to write down the issue and sum up possible solutions. Probably later on today.

from radiolib.