Hi Florian
Could you run the binary that I attached to see whether it operates correctly?
Unfortunately my FRDM-KL26Z board died recently (the OpenSDA K20 doesn't start anymore) so I could only test on a KL25 and simulate the KL26. If you find that the PWM stops in LLS I think that there may be a problem/restriction with the chip. My explanation is as follows:
- From my tests on the FRDM-KL25Z it is seen that the 8MHz OCS continues to operate in LLS (the signal is seen on the crystal) - it will stop in VLLS0, which is what is expected.
- OSCERCLK is being used to clock the TPM and this should continue to operate in LLS according to the user manuals.
- In the case of the FRDM-KL25Z the PWM output doesn't continue in LSS - it will randomly stop at '1' or '0'
- However I am not sure about the KL26 because it is a little different with respect to the OSCERCLK in LLS. The KL25 can use this clock in LLS but only when in the low frequency mode (that is, when driven by 32kHz). This restriction doesn't apply to the KL26 in LLS where it can also use the OSCERCLK at 8MHz.
This is where I cannot be sure because it may in fact be normal that the FRDM-KL25Z's PWM doesn't operate (since the OSCERCLK is in the invalid high frequency range), although the OSC itself certainly continues.
There is however a further question in whether the TPM is in fact running but the PWM output doesn't work because the port output is frozen in LLS?
What I know from the KL25 is that if you configure the RTC_CLKOUT (also needs the port module to operate and be configured for the MUX setting) to be driven by the OSCERCLK (8MHz clock output seen in normal mode) this clock output will stop in LLS although the OSC is obviously still running (again it could be due to the out-of-spec clock range on the KL25 (?)).
If my FRDM-KL26Z hadn't decided to give up its ghost two days ago I wouldn't need to guess (or rely on someone checking) but there may be the factor of ports involved that don't allow the outputs to run rather that the TPM itself stopping (difficult to check).
Should the KL26Z not work as expected I would also suggest that there is either a restriction that is not otherwise documented or the port output factor is restricting the actual outputs from being effective (which may also be an undocumented practical restriction) - it depends on the TPM output design as to whether it passes through the 'frozen' port or can bypass it in LLS, which is not specifically stated anywhere... My gut feeling is that PWM outputs may be inoperable due to the ports being frozen in LLS and not due to the TPM not continuing, but until I can verify on a real KL26 there is a still a glimmer of hope that this analysis is not fully correct.
Regards
Mark
Kinetis: µTasker Kinetis support
KL26: µTasker Kinetis FRDM-KL26Z support / µTasker Kinetis Teensy LC support
LLWU: µTasker LLWU Support
PWM: http://www.utasker.com/docs/uTasker/uTaskerHWTimers.PDF
For the complete "out-of-the-box" Kinetis experience and faster time to market