issues with latest SDK 11.0.0-2

RE: issues with latest SDK 11.0.0-2

Richard von Lehe — Tue, 29 Dec 2015 22:10:46 GMT

Thanks - I'll take your advice on the support request.

RE: issues with latest SDK 11.0.0-2

RK — Tue, 29 Dec 2015 02:25:03 GMT

Well there you go - you found something I didn't know - that you can't have two SECTIONS commands in a linker script. Shame 'ld' doesn't flag that as an error!

Yes moving it into the main one works, and even though that's common, I can't see why it would be a problem, nothing else has that section, so it doesn't affect anything else.

In the quest to add a HAL to the SDK, make the drivers all singing-and-dancing and abstract away everything which might be confusing, the SDK is getting harder to use. It took me a while to figure out what fs_data even does and when I did I thought .. oh is that it.

For getting things fixed, file a My Page support request, they get dealt with pretty quickly, I reported some nRF52 makefile oddities there earlier and someone fixed them.

RE: issues with latest SDK 11.0.0-2

Richard von Lehe — Mon, 28 Dec 2015 19:27:54 GMT

Now I'm reading that there can be only one SECTIONS defined, though with multiple entries inside. Nordic has created two sections - one in the project-specific linker file and one via the INCLUDE "nrf5x_common.ld". Can we just move the .fs_data_out definition into nrf5x_common.ld? Then add the "> FLASH" so that it sits in the user area of flash and not forbidden softdevice 0x0 address?

Moving the .fs_data_out section definition into the common linker file did the trick. It gets put into the user-app area of flash. Thanks for getting me on the right path, RK. Nordic, can you fix this please? Thx

RE: issues with latest SDK 11.0.0-2

Richard von Lehe — Mon, 28 Dec 2015 18:27:02 GMT

OK, so I see the mechanism being used here. Basically any Nordic demo in 11.0.0-2.alpha that uses fds.c will have the FS_SECTION_VARS_ADD macro try to place a structure there. So where is this 'fs_data' section that the fstorage module needs really supposed to live?

RE: issues with latest SDK 11.0.0-2

Richard von Lehe — Mon, 28 Dec 2015 16:31:54 GMT

Thanks - yes this fs_data_out section is apparently new this latest SDK. I guess I'll try to figure out where it is supposed to be placed.

RE: issues with latest SDK 11.0.0-2

RK — Thu, 24 Dec 2015 01:05:29 GMT

fs_data_out               0x00000000       0x10  
                          0x00000000                PROVIDE (__start_fs_data, .)
*(fs_data) fs_data        0x00000000       0x10 _build/fds.o 
                          0x00000010                PROVIDE (__stop_fs_data, .)

looks like the problem. That's been placed down at 0x00000000.

Looking at the linker file it has no region (eg > RAM) so I think it would get placed into default which is 0x00000000 and that won't work. I believe the '=0' at the end of it just says it must be zero-filled.