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

Eclipse Kepler as IDE for nordic SDK stucks on __INLINE ()

I am trying to setup the hrs sample with gcc (4.8.3) and Eclipse Kepler but althoug it compiles fine the editor is complaining about:

Symbol 'softdevice_evt_schedule' could not be resolved Symbol 'app_timer_evt_schedule' could not be resolved

Can sombody explain that issue?

Brgds Maik

  • here a screenshot of my eclipse window. As described by Maik there are "Semantic Errors" saying "Field 'xyz' could not be resolved".

    Although the corresponding includes are made in eclipse (as you can see in the picture) it shows errors.

    eclipse_could_not_resolve_errors.PNG

  • As I would describe the error in the absolutely same way as Maik I attach the screenshot here. See below.

  • This is definitely a different problem than the original poster here, who only saw two undefined symbols, and in that particular case, there isn't much to do about it.

    However, in your case, it seems that the problem is that the Include paths are wrong. When testing this, I see that this unfortunately an issue with the default configuration of the project in SDK 5.1.0, in that it includes the wrong paths. You should therefore verify that you have set up the following include paths for GNU C: ${project_loc}/../ ${project_loc}/../../../../../Include ${project_loc}/../../../../../Include/app_common ${project_loc}/../../../../../Include/ble ${project_loc}/../../../../../Include/ble/ble_services ${project_loc}/../../../../../Include/s110 ${project_loc}/../../../../../Include/sd_common

    Also, to make the board specific defines resolve, you should make sure to define the Symbol BOARD_NRF6310 (or whatever board you use). This is by default done in the Makefile, which Eclipse unfortunately can't pick up.

    I've reported this internally so that it can be fixed in a future release.

  • FormerMember
    0 FormerMember in reply to Mike

    In addition to what Ole has mentioned, do include the paths {path-until-here}/gcc-arm-none-eabi-4_8-2013q4/arm-none-eabi/include {path-until-here}/gcc-arm-none-eabi-4_8-2013q4/arm-none-eabi/lib/gcc/arm-none-eabi/4.8.3/include

    This will let Eclipse find stdint.h and its buddies so that uint32_t can be understood. The actual path might vary depending on the version of GCC that you are using. Cheers.

  • Adding the extra includes mentioned by Phithvi helped. And yes Ole, you were right, what Maik described is what I have now. Sorry for the missunderstanding. Thank you guys, I'm fine now!

1 2 3