Re: os data.core memory section

Hey Will, thanks for the background - much appreciated. I did indeed need the additional memory to store a time series generated at high frequencies, so offloading wasn't an option. I solved it by storing some of the time series in CCM memory, which is probably the better solution anyway. Given

Re: os data.core memory section

On Mon, Apr 2, 2018, at 4:42 PM, markus wrote: > On Mon, 02 Apr 2018 14:16:54 -0300 > Fabio Utzig wrote: > > > Both > > > > hw/mcu/stm/stm32f7xx/stm32f767.ld > > hw/mcu/stm/stm32f4xx/stm32f407.ld > > > > already define the stack on CCM (called DTCM on the F7xx). Am I > >

Re: os data.core memory section

On Mon, 02 Apr 2018 14:16:54 -0300 Fabio Utzig wrote: > Both > > hw/mcu/stm/stm32f7xx/stm32f767.ld > hw/mcu/stm/stm32f4xx/stm32f407.ld > > already define the stack on CCM (called DTCM on the F7xx). Am I > missing something here? It might be me who's missing something (most

Re: os data.core memory section

Markus: I presume you are referring to these definitions: #define sec_data_core __attribute__((section(".data.core"))) #define sec_bss_core__attribute__((section(".bss.core"))) #define sec_bss_nz_core __attribute__((section(".bss.core.nz"))) As far as I know there is no real magic here

Re: os data.core memory section

Both hw/mcu/stm/stm32f7xx/stm32f767.ld hw/mcu/stm/stm32f4xx/stm32f407.ld already define the stack on CCM (called DTCM on the F7xx). Am I missing something here? On Mon, Apr 2, 2018, at 2:15 PM, Christopher Collins wrote: > Hi Markus, > > On Sat, Mar 31, 2018 at 04:02:05PM -0700, markus wrote:

Re: os data.core memory section

Hi Markus, On Sat, Mar 31, 2018 at 04:02:05PM -0700, markus wrote: > I looked into moving the stack into the CCM memory of the stm32 > mcu's - and although almost every linker script defines ".data.core" > sections and there are some defines in bsp.h's for section > attributes they don't seem to