Unresolved Errors in Build

[GaryD]

Hello,

I have been struggling with Eclipse for a couple of days. I created the pwm_driver project via the File/New/Makefile with existing code option. After initializing the appropriate Build and Preprocessor properties along with manually entering the GNU Tools ARM Embedded Include directories in Paths and Symbols, and virtual paths for all the .c files, the first build of the pwm_driver project went perfect. I built the project, downloaded to the nRF52 development board via the flash Target, and it executed perfectly the first time. I thought I was ready to start integrating some additional functionality for connecting up a Bosch IMU sensor via I2C.

First, I wanted to integrate and test the SEGGER_RTT capability for debug messages. I included the SEGGER_RTT.c file in the Makefile and included it in a virtual directory called Tools. I then tried to build and suddenly the all of the include files in main.c could not be resolved (the preprocessor was not discovering the includes properly). I backed out the SEGGER_RTT files and still no luck - still had unresolved includes in main.c.

I decided to start all over again and deleted the pwm_driver project and then recreated it again thinking I could at least get another clean, executable build. I still ended up with unresolved symbols - all of the includes were resolved. I researched the problem and, based on your Develpment with GCC paper, went to Properties/Index/Rebuild followed by a new build. I am now stuck with the following issue:

I seem to have only 2 unresolved symbols now - unit32_t and APP_ERROR_CHECK types. The build appears to complete acceptably as indicated in the console.

Can you please give me some guidance on first clearing these issues and then including SEGGER_RTT debug message capability. In hindsight, when I included the SEGGER_RTT.c in the Makefile, I failed to put the path in the Makefile for the SEGGER_RTT.h file so maybe that triggered some of the issues when the preprocessor passed through to resolve includes and symbols.

Any help on this will be greatly appreciated.

Regards, GaryD

[Turbo J]

Looks loke one of those eclipse discovery bugs. Those are almost purely cosmetics in eclipse itself, when discovery is not perfectly set up with matching toolchain (arm-none-eabi-gcc). You can ignore those - but might miss a real one.

[GaryD]

It looks like you have to live with several errors. Here are a few I have found.

1. The unresolved discovery errors do not go away. I have tried several of the suggestions given on the blog and no luck. I have tried the index/rebuild followed by clean and rebuild - still there. Sometimes they go away if you close and re-open the project but as soon as you open a file, they are back. As long as I see a clean build with no errors and a hex file to load, I go with it. I also periodically build from the cmd line using a make command. I never see any unresolved unless I make a real error.

2. Debug is a bit odd. If you try to change something in the code, rebuild, and try to debug again, you get errors where it cannot find a file. My solution is to delete the GDB SEGGER J-Link Debugging configuration used the last time and create a new one.

3. Also, in Debug - BEWARE - when you created the virtual links as instructed in the tutorial, copies of the source code files virtually linked are kept in a newly created subdirectory in the armgcc directory where the makefile is located. The builds and edits from the C/C++ Perspective use this newly created file. The Debug build when you launch the Debugger uses the original file in the examples directory where it is located. You must change both files to maintain continuity with debug. Because of this issue, I may primarily use the command line for edits and pre-builds to check the code and use eclipse for debug unless I find a way to do it in the command line mode.

Has anyone tried Neon version of Eclipse with the sdk 11.0.0 for the nRF52 IDE? I sure would like some feedback before going down that (time consuming) path.

Regards, GaryD