Eclipse Managed Make Project for nRF52

RE: Eclipse Managed Make Project for nRF52

Tosa — Tue, 14 Feb 2017 23:27:22 GMT

My mistake; the files are actually different for the RAM regions. I believe the one listed in the project directory accounts for the softdevice: RAM (rwx) : RAM (rwx) : ORIGIN = 0x20002080, LENGTH = 0xdf80 vs ORIGIN = 0x20000000, LENGTH = 0x10000. But since the template .ld file is in the softdevice\toolchain directory, I would have guessed that the template would already account for this.

RE: Eclipse Managed Make Project for nRF52

bjorn-spockeli — Tue, 14 Feb 2017 13:34:03 GMT

I assume that the linker script in the toolchain folder is the template that was used to generate the linker scripts for each individual project.

RE: Eclipse Managed Make Project for nRF52

butch — Tue, 14 Feb 2017 12:59:15 GMT

1,2) Those are just two different forms of the same "option", both have the same effect (e.g. the gc-sections effect) -Wl,foo just says the option foo is passed to the compiler but understood by the linker. Maybe Eclipse managed make is passing the option directly to the linker instead of to the compiler which then invokes the linker.

Not necessary until your app uses a function from those libraries. The link phase of the build would fail otherwise.

I use Eclipse managed make. It seems fine but does require you to learn the GUI of Eclipse i.e. build configurations, project properties, etc. Also requires you to extract options and paths from the Nordic example makefiles.