CS32F103 freezes on libmaple RTC codes
Posted: Wed Jul 05, 2023 12:08 pm
hi,
while I'm working something off a 'clone' deemed 'cs32f103 blue pill' board, the looked like 'blue pills' with the genuine chip, but with instead a cs32f103.
while trying out codes in the RTCAdjust
https://github.com/rogerclarkmelbourne/ ... /RTCAdjust
as it turns out that code freezes on startup, quite interestingly it is able to get past the freeze and continue running as my led blinks after a long stall (minutes).
If I switched to a real 'maple mini (clone)' with a real stm32f103cbt6, everything runs perfect, no freezes, the RTC clock runs as expected.
My thoughts are that there could be a few reason:
- LSE did not start on the 'clone' cs32f103 pill board - most likely (but I did not bother to find out). They placed a module that looked like one of those 'epson' 32k modules.
- the RTC implementation is after all different
if indeed it is the latter, i.e. different RTC implementation, then it is quite possible that the chip is after all reverse engineered.
but as I did not check if the 1st reason can be ruled out i.e. LSE not running, we can't conclude the 2nd reason to be likely.
as it is able to get past the stall, my guess is, it is more than likely it is simply due to LSE not running.
while I'm working something off a 'clone' deemed 'cs32f103 blue pill' board, the looked like 'blue pills' with the genuine chip, but with instead a cs32f103.
while trying out codes in the RTCAdjust
https://github.com/rogerclarkmelbourne/ ... /RTCAdjust
as it turns out that code freezes on startup, quite interestingly it is able to get past the freeze and continue running as my led blinks after a long stall (minutes).
If I switched to a real 'maple mini (clone)' with a real stm32f103cbt6, everything runs perfect, no freezes, the RTC clock runs as expected.
My thoughts are that there could be a few reason:
- LSE did not start on the 'clone' cs32f103 pill board - most likely (but I did not bother to find out). They placed a module that looked like one of those 'epson' 32k modules.
- the RTC implementation is after all different
if indeed it is the latter, i.e. different RTC implementation, then it is quite possible that the chip is after all reverse engineered.
but as I did not check if the 1st reason can be ruled out i.e. LSE not running, we can't conclude the 2nd reason to be likely.
as it is able to get past the stall, my guess is, it is more than likely it is simply due to LSE not running.