RE: Segger Embedded Studio - FDS - warning .stack and hardfault

ColdBrew667 — Wed, 16 Nov 2016 17:37:44 GMT

Well, my thumb_crt0.s was ok. I missed the definition of the symbols in the FLASH segment. I added it and removed my size from the RAM section to be aligned with what you are mentioning. And in fact this is even worse, the warning is back and it looks like the init of fds cannot go through. In my code I directly call fds_init() function. During this execution, a call to pages_init() occurs just after the fs_init(). In this pages_init() function there is a tentative of retrieving the address of the start page which fails:

uint32_t        const * const p_page_addr = fs_config.p_start_addr + (i * FDS_PAGE_SIZE);

p_page_addr = 0xffffffff after this call, and thus all this ends in a hardfault on the line that follows

fds_page_type_t const         page_type   = page_identify(p_page_addr);

RE: Segger Embedded Studio - FDS - warning .stack and hardfault

FormerMember — Wed, 16 Nov 2016 09:52:27 GMT

As mentioned in @RK 's answer, you do also need to define the linker symbols __start_fs_data and __stop_fs_data. In flash_placement.xml it will look like the following:

<MemorySegment name="$(FLASH_NAME:FLASH)">
...
<ProgramSection alignment="4" load="Yes" name=".fs_data" address_symbol="__start_fs_data"  end_symbol="__stop_fs_data" />
<ProgramSection alignment="4" load="Yes" runin=".fs_data_run" name=".fs_data" />
...
</MemorySegment>

<MemorySegment name="$(RAM_NAME:RAM);SRAM">
...
<ProgramSection alignment="4" load="No" name=".fs_data_run" address_symbol="__start_fs_data"  end_symbol="__stop_fs_data" />
...
</MemorySegment>

Did you add the below in thumb_crt0.s (also from @RK 's answer)?

  ldr r2, =__tdata_end__
bl memory_copy
# ADD HERE ... 
ldr r0, =__fs_data_load_start__
ldr r1, =__fs_data_start__
ldr r2, =__fs_data_end__
bl memory_copy
# TO HERE ...