Re: Nimble on U-blox Nina B112 (Nrf52832)

Hi Matias Have you some example to make the scan ? Enviado do Email para Windows 10

Re: Memory locations

On Tue, Jun 8, 2021 at 9:34 AM Tim Hardisty wrote: > > > On 08/06/2021 14:18, Sebastien Lorquet wrote: > > what I would check here (just a live thought process) > > > > * check that the ld file is actually used (ld file is pointed by main > > Make.defs IIRC) (easy: just add garbage in it and verif

Re: Memory locations

Hi Tim, I am not a linker script expert neither. But I'll let here a helpful link that helped me a lot: https://interrupt.memfault.com/blog/how-to-write-linker-scripts-for-firmware Em ter., 8 de jun. de 2021 às 10:19, Sebastien Lorquet escreveu: > what I would check here (just a live tought p

Re: Memory locations

On 08/06/2021 14:18, Sebastien Lorquet wrote: what I would check here (just a live thought process) * check that the ld file is actually used (ld file is pointed by main Make.defs IIRC) (easy: just add garbage in it and verify build actually breaks) You, sir, have earned the cigar! Garbage

Re: Memory locations

what I would check here (just a live tought process) * check that the ld file is actually used (ld file is pointed by main Make.defs IIRC) (easy: just add garbage in it and verify build actually breaks) * check that the driver source with the definition is being recompiled * check that the o

Re: Memory locations

Thanks, but still no cigar :( I have tried:     .isramdata_reserve (NOLOAD) :     {     *(.isramdata)     . = ALIGN(4);     _isramdata_heap_start = ABSOLUTE(.);     } > isram and also just     .isramdata(NOLOAD) :     {     *(.isramdata)     } > isram along with trying static

Re: Memory locations

Thanks, but still no cigar :( I have tried:     .isramdata_reserve (NOLOAD) :     {     *(.isramdata)     . = ALIGN(4);     _isramdata_heap_start = ABSOLUTE(.);     } > isram and also just     .isramdata(NOLOAD) :     {     *(.isramdata)     } > isram along with trying static

Re: Memory locations

Hello, The correct syntax is: .isramdata (NOLOAD) :  /*<- this is the segment name in the output, NOLOAD means that this segment is not to be initialized, like BSS, but the linker alread knows that BSS is NOLOAD*/     {     *(.isramdata)    /*<- this is the input sections from the reloca

RE: Memory locations

Here is a working example. https://github.com/apache/incubator-nuttx/blob/master/arch/arm/src/stm32h7/stm32_spi.c#L715-L716 https://github.com/apache/incubator-nuttx/blob/master/boards/arm/stm32h7/nucleo-h743zi/scripts/flash.ld#L179-L184 You can check it the arm-none-eabi-nm -C nuttx.elf | grep

Re: Memory locations

On 07/06/2021 19:06, Nathan Hartman wrote: On Mon, Jun 7, 2021 at 12:24 PM Tim wrote: I will, I believe, need to declare - place - MCAN related structures such that they (or at least some elements of them) are in SRAM. Yes. It is possible. It is done by adding attributes in the code which tel

Re: Memory locations

On 07/06/2021 20:45, Gregory Nutt wrote: I will, I believe, need to declare - place - MCAN related structures such that they (or at least some elements of them) are in SRAM. You will need to exercise care.  SRAM (called isram in the linker scripts) is already used for other things including