Thingy SDK compile error using Segger Embedded Studio within Windows 10

[Archer]

Hi sir,

I encountered a problem when I tried to build Thingy SDK. Here are steps what I did,

• Download "thingy_sdk_v2.1.0" SDK and followed README.md to install the prerequisites tools and also run "setup_sdk.bat".
• Try compiling the Thingy firmware using SES, I mean I navigated to the folder /thingy_sdk_v2.1.0/project/pca20020_s132/ses and double-click the project file ble_app_thingee_s132_pca20020.emProject to build FW, but it appeared error as below,

1. nrf_log.h: No such file or directory
2. thingy_sdk_v2.1.0\source\modules\thingee_ble_handler.c: No such file or directory
3. thingy_sdk_v2.1.0\source\modules\thingee_config_flash.c: No such file or directory
4. thingy_sdk_v2.1.0\source\modules\thingee_ui.c: No such file or directory

Could you please do me a big favor to see how to fix the problem?

Thanks.

Regards, Archer

[Joakim Jakobsen]

That is true shibshab. It actually applies to all of our SDK's.
The path lenght limitation in windows is 247 characters (260-12-1=247).
If the path lenght to your project exceeds this, it wont work.
Best regards.

[iotlight]

1. After I moved the entire Thingy_sdk to c:\Nordic as suggested in the link, I got the following result:

2. I don’t know which folder I should put the RTT_Syscalls_SES.c  file.

3. I think nrf.h is not a problem in my case (please see the screen shot above under CMSIS files), If not, please let me know how to add the path to the file in my preprocessor definitions. 

Thanks.

[Joakim Jakobsen]

Hi!

1)
If you take a look at one of my comments above, you can see that the SES project in the thingy SDK is not working;
"I'm afraid Tom is pretty much correct about the SES project from the thingy_sdk_v2.1.0.
The SES project is borken, and was not meant to be released in the SDK.
However, it is possible to import keil projects to SEGGER Embedded Studio"

2)
Note that my comment about RTT_Syscalls_SES.c, is referring to the process of importing the KEIL project to SES. But the file can be placed in any folder, but the nRF_Segger_RTT folder would be a good place to have it.

3)
The nrf.h and other header files should not be added to your project explorer like that.
You can just add the path to the header file. You can do that by opening your project settings -> preprocessor -> and adding the path to the user include directories.

If you want an introduction to owkring with SEGGER Embedded Studio and with the nRF5 SDK, we have a youtube tutorial-series that you can take a look at.
The tutorials cover how to add the free nordic license, how the build configurations and settings work, how to debug etc.

SEGGER Embedded Studio - Getting Started

Best regards,
Joakim.

[jp54l]

Hi.

2 years on, and there's still issues with importing,compiling,linking the Thingy52 project in SES?

Does anyone have a working project for Thingy52 in SES they are willing to share?




Regards
Jerome

[Joakim Jakobsen]

Hi Jerome. 

You can find a working version of the SES project in this thread: 
https://devzone.nordicsemi.com/f/nordic-q-a/51236/unable-to-compile-ses-project-in-thingy-52-sdk 

Best regards, 
Joakim

[jp54l]

Hi Joakim

Thankyou so much. After following the readme.md instructions this project compiles & links ok.

May I suggest uploading this to the Nordic gitHub repository so that others won't have to go through the same problem, also worth noting on thingy_52 firmware repo that it will not work with SES and to download this project.

Best Regards
Jerome

[Joakim Jakobsen]

No problem, happy to help! 

I will forward your feedback about the GitHub repo. 

Cheers, 
Joakim