In some, well-optimized (by the compiler) binaries, the LFRC startup code can cause erratum 3.34 to occur by restarting the LFRC oscillator between 66 and 138 us after stopping it.
It's tricky to create a reproducible example because it seems to rely on compiler optimizations whether it occurs or not, but the only code you need to run for it to occur is:
In some, well-optimized (by the compiler) binaries, the LFRC startup code can cause erratum 3.34 to occur by restarting the LFRC oscillator between 66 and 138 us after stopping it.
It's tricky to create a reproducible example because it seems to rely on compiler optimizations whether it occurs or not, but the only code you need to run for it to occur is:
This code may hang forever on the
events_lfclkstarted
check inclocks.rs