https://devzone.nordicsemi.com/f/nordic-q-a/20999/unresolved-errors-in-buildHello, 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 enteringen-USTelligent Community 13Mon, 03 Apr 2017 08:12:14 GMThttps://devzone.nordicsemi.com/thread/82068?ContentTypeID=1Mon, 03 Apr 2017 08:12:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7bc59d36-3270-4b7a-8bd6-2540a3c3ad1aGaryD<p>It looks like you have to live with several errors. Here are a few I have found.</p> <ol> <li> <p>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.</p> </li> <li> <p>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.</p> </li> <li> <p>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.</p> </li> </ol> <p>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.</p> <p>Regards, GaryD</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/82067?ContentTypeID=1Fri, 31 Mar 2017 14:40:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:23491d59-4414-4adc-9ef2-d5148024e8a2Turbo J<p>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.</p><div style="clear:both;"></div>