This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Eclipse partial pre-processor discovery

SDK version: 13.1 Hardware: nRF52832 Eclipse version: link text (I could not get the marketplace working in the latest Mars Eclipse version, so I downloaded this version since it already had the necessary plugins installed)

Hello,

I've been following the tutorial for Eclipse IDE setup devzone.nordicsemi.com/.../, but I'm currently stuck at the auto-discovery. I've been able to compile, build and program the blinky and the ble_apps_hrs_pca10040_s132 example succesfully, but still functions like APP_ERROR_CHECK() are red underlined, because the auto-discovery is only working partially I assume.

I do get the verbose output, so the build command: C:\MinGW\bin\mingw32-make.exe VERBOSE=1 is working. This is the output I get:

image description

But if I look at for example main.c's Properties -> C/C++ General -> Preprocessor Include Path -> CDT GCC Build Output Parser, there are no Pre-processor Symbols added like in the Development with GCC and Eclipse.pdf Troubleshooting Guide.

image description

I use SDK 13.1, so the default makefile.common found under s132/armgcc/ is equal to the fixed makefile.common added to the Tutorial. I've also compared the makefile from the SDK13.1 example with that of the Tutorial application, the only difference I could find where optimization level for the CFLAGS and the added -g3 flag at the ASMFLAGS in the example project.

Eventhough it does compile and runs, I've been unsuccesfull in fixing this. I've continued with the Tutorial but I can't get debugging to work either, but my best guess was that maybe it was connected to the partial pre-processor Symbols discovery problem.

Any help would be greatly appreciated, as I really need to move away from Keil Uvision due to the linker 32k restrictions.

Parents Reply Children
No Data
Related