cancel
Showing results for 
Search instead for 
Did you mean: 

Core Coupled RAM on F401/F410/F411

Uwe Bonnes
Principal III
Posted on April 26, 2016 at 13:56

Recent StCube device headers for F401 and F411 define Core coupled RAM for these devices. However datasheet/reference manual does not indicate existance of  CCM RAM:

stm32f401xc.h:#define CCMDATARAM_BASE       ((uint32_t)0x10000000U) /*!< CCM(core coupled memory) data RAM(64 KB) base address in the alias region  */

stm32f401xc.h:#define  RCC_AHB1ENR_CCMDATARAMEN            ((uint32_t)0x00100000U)

So either the headers or datasheet and reference manuals need update.
3 REPLIES 3
Posted on April 26, 2016 at 15:26

I think it has more to do with the lineage of the files and the core. I'm not aware that the 401 has any CCMRAM

May be you want to focus on functional defects, rather than defines that haven't been purged from every member of the F4 family offering a subset of function to the others.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
Nesrine M_O
Lead II
Posted on April 26, 2016 at 15:54

Hi bonnes.uwe,

Thank you for your feedback. The issue has been reported internally.

-Syrine-

Uwe Bonnes
Principal III
Posted on April 27, 2016 at 12:16

My work on the ethernut cross device cooperative RTOS

http://www.ethernut.de/

found in SVN HEAD

https://sourceforge.net/projects/ethernut/files/

tries to rely on the device header as much as possible. With wrong devices defining CCM, I need to manual add items in the configurator to decide if a linker script using CCM can be offered,

So perhaps you understand why I report these flaws in the device headers.