Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
On page 9 of the 20732S datasheet, it says that the oscillator circuit can be designed for a 32 kHz or 32.768 kHz crystal oscillator and implies in the next sentence that this can be provided externally (characteristics defined in Table 1).
Does this mean that there is already an internal low power oscillator internal to the device?
I have seen mentions of this clock scattered throughout various pieces of the API/SDK documentation, but nothing within the datasheet really explains the internal LPO.
My guess is that the external oscillator is used to provide better accuracy and lower sleep current, but what I'm wondering is whether or not the clock that's internal to the module can be used to wake from deep sleep.
Per the diagram on page 8 of the datasheet, the module includes a standard 24MHz Pierce oscillator for System and RF timing. In addition, there is an internal LPO which handles the other clocking chores required by the SOC inside the module.
Related to Deep Sleep, the firmware supports waking the part after configured time interval.
With the internal clock, it can wake anywhere from 64mS to ~36 Hrs.
From the SDK API documentation and also doing searches it would appear there is a 128KHz internal clock that can be used to wake from DEEP_SLEEP. This 128KHz Clock and the ability to use it to wake from DEEP SLEEP is referenced in platform.cgs and also in devicelpm.c as shown below. There is no mention of this 128KHz clock in the BCM20732S Reference Manual though and/or what all it can be used for so there is a bit of uncertainty here...?
This 128KHz clock is also referenced in miadriver.h and rtc.h in which it is not clear what the difference is between what the differences between the MIA function such as mia_enterHidOff and mia_setupTimedWake() functions vs. similar functions found in devicelpm.c.