2008-12-08 09:30 PM
stm32 errata update request
2011-05-17 03:54 AM
Hi,
As the following post is now blocked i have started another one.http://www.st.com/mcu/forums-cat-7336-23.html&start=30
codesoucery have released a new version of their eabi arm tools (2008q3-66). The release notes mention the following:Quote:
Workaround for Cortex-M3 CPU errata. Errata present in some Cortex-M3 cores can cause data corruption when overlapping registers are used in LDRD instructions. The compiler avoids generating these problematic instructions when the -mfix-cortex-m3-ldrd or -mcpu=cortex-m3 command-line options are used. The Sourcery G++ runtime libraries have also been updated to include this workaround. does this fix the issues that you have seen and mentioned in the stm32 errata? An update on this issue would be very helpful. UPDATE - For info IAR 5.20 have released a patch that corrects the same cortex_m3 errata - is all ok for iar now aswell? Regards sjo [ This message was edited by: sjo on 02-12-2008 14:00 ]2011-05-17 03:54 AM
Dear sjo,
Please refer to STM32 Erratas, in ''ARM™ 32-bit Cortex®-M3 limitations'' section and then click on the link to be redirected to ARM Cortex errata : 1) This limitation does not affect the STM32 code execution when fetching from embedded FLASH (standard use of the product). 2) The limitation may affect the STM32 code execution when fetching from: - Embedded RAM - External memory (via FSMC for the STM32 High Density ). This applies to applications requiring large amount of code (more than the embedded Flash size ). To finish, as the limitation is based on asynchronous event (interrupt) on a specific code sequence (LDRD) not executed from STM32 embedded flash, there is very limited chance to get end-customer application fault. Nevertheless, all our Compilers partners (Keil, IAR, GNU CodeSourcery, Hitex etc..) already provide a ''Detection'' tool for code deployed in the field with previous/old revisions of compilers that may generate this sequence , Here as example an FAQ from ARM/Keil : Cheers, STOne-32. [ This message was edited by: STOne-32 on 07-12-2008 22:48 ]2011-05-17 03:54 AM
Hi,
I was more interested in whether the latest codesoucery suffers the issue 2.6 in the following errata: Cheers sjo [ This message was edited by: sjo on 09-12-2008 11:01 ]