I'm working with a Kinetis MK22FX512AVLQ12 in a KDS project, using Processor Expert.
Right now, I am trying to verify the MCU's power usage in LLS mode. Datasheets for the K22 suggest that LLS is a valid mode for this MCU, for example see p.10 and p.11 of this document:
Table 6 calls out Id_LLS as the current consumption in LLS mode.
AN4470 lists LLS as a distinct low-power mode as well, distinct from VLLS1/VLLS2/VLLS3 modes.
However, AN4503 does not show LLS as a mode in Figure 4:
Why is that?
Additionally, the reference manual lists LLS3 and LLS2 as valid modes, but does not mention LLS:
Why is that?
The reason I'm asking is because I'm attempting to enter LLS using the following PE command:
Cpu_SetOperationMode(DOM_STOP, NULL, NULL);
But I'm measuring 7mA to my board, which suggests that we're not actually in LLS mode.
K22 has many different part numbers, MK22FN512, MK22FN256, MK22FN1M0....etc, There are functional differences between the devices.
There are different documentation sets for the different parts, please refer to below picture.
Please check the bulletin for more details
The K22 has LLS2 and LLS3 modes, which are both essentially LLS but with different levels of SRAM remaining powered.
The method to get to LLS2 or LLS3 is the same as core deep sleep, with the choice of exactly which LLS made in SMC_STOPCTRL and SMC_PMCTRL.
You can load binary files to NXP development boards from the links below which allows the mode to be dynamically changed via the OpenSDA VCOM interface at 115kBaud, displaying the available modes as follows:
RUN = 0
WAIT = 1 [active]
STOP = 2
VLPR = 3
VLPW = 4
VLPS = 5
LLS2 = 6
LLS3 = 7
VLLS0 = 8
VLLS1 = 9
VLLS2 = 10
VLLS3 = 11
Some more details and videos are at:
Low power and LLWU: http://www.utasker.com/kinetis/LLWU.html
Low power videos:
In the uTasker project the power mode is controlled by (for K22)
In case of problems with the PE methods you can also just copy the code from the open source project on Github (which supports dynamic power management).
For less questions and faster, cheaper developments: try uTasker for Kinetis