summaryrefslogtreecommitdiff
path: root/nuttx
diff options
context:
space:
mode:
Diffstat (limited to 'nuttx')
-rwxr-xr-xnuttx/ChangeLog15
1 files changed, 14 insertions, 1 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog
index 408d29626..a90726497 100755
--- a/nuttx/ChangeLog
+++ b/nuttx/ChangeLog
@@ -10041,4 +10041,17 @@
not fully functional. From Kristopher Tate (2015-030-29).
* arch/arm/src/armv7-m: Add configuration option and logic to support
the D-Cache in write-through mode (2015-03-29).
-
+ * arch/arm/src/stm32/Kconfig, stm32_lse.c, stm32_lsi.c, stm32_rtc.c/.h,
+ stm32_rtcc.c, stm32_rtcounter.c, and stm32f*_rcc.c: The
+ STM32F4Discovery board doesn't come with a Low speed external
+ oscillator so the default LSE source for the RTC doesn't work. In
+ stm32_rtcc.c the up_rtcinitialize() logic doesn't work with the LSI.
+ The check on RTC_MAGIC on the BK0R register lead to rtc_setup() call
+ that rightfully enables the lsi clock; but the next times, when the
+ rtc is already setup, the rtc_resume() call does NOT start the lsi
+ clock! The right place to put LSE/LSI initialisation is inside
+ stm32_stdclockconfig() in stm32fxxxxx_rcc.c. Doing this I checked
+ the possible uses of the LSI and the LSE sources: the LSI can be used
+ for RTC and/or the IWDG, while the LSE only for the RTC (and to output
+ the MCO1 pin). This change is not verifed for any other platforms.
+ From Leo Aloe3132