From 7442148f330a78e5dd0088508d047e0d6b388e82 Mon Sep 17 00:00:00 2001 From: patacongo Date: Thu, 29 Oct 2009 21:51:09 +0000 Subject: [PATCH] Document bugfix git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2189 42af7a65-404d-4744-a932-0658087f49c3 --- ChangeLog | 7 +++++++ Documentation/NuttX.html | 7 +++++++ 2 files changed, 14 insertions(+) diff --git a/ChangeLog b/ChangeLog index ff97641c48..ca3bdb9a7e 100644 --- a/ChangeLog +++ b/ChangeLog @@ -936,3 +936,10 @@ NOTE: This USB driver is completely untested as of the initial check-in + * arch/arm/src/stm32/stm32_rcc.c - Fixed an error in clock initialization. + On some boards (none of mine), the HSE (high speed external clock) delay + loop times out if the optimization level is high. The STM32 then falls + back to the HSI (internal clock), and the system clock is too slow by a + factor of 11.1%. This was fixed by simply add the volatile storage class + to the timeout loop counter + diff --git a/Documentation/NuttX.html b/Documentation/NuttX.html index c50d16dd98..bdd87219a0 100644 --- a/Documentation/NuttX.html +++ b/Documentation/NuttX.html @@ -1588,6 +1588,13 @@ nuttx-0.4.13 2009-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> NOTE: This USB driver is completely untested as of the initial check-in + * arch/arm/src/stm32/stm32_rcc.c - Fixed an error in clock initialization. + On some boards (none of mine), the HSE (high speed external clock) delay + loop times out if the optimization level is high. The STM32 then falls + back to the HSI (internal clock), and the system clock is too slow by a + factor of 11.1%. This was fixed by simply add the volatile storage class + to the timeout loop counter + pascal-0.1.3 2009-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> buildroot-0.1.8 2009-xx-xx <spudmonkey@racsa.co.cr>