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

[shibshab]

There might be issues with long path names.

Try moving the entire sdk to C:/thingy and see if that helps.

[Tom]

I am on Windows 7 - I dont think version of Windows is the issue.

[Tom]

The SES Project that is included in the latest release (thingy_sdk_v2.1.0) is broken. It makes reference to files that do not exist.

Looking at the ble_app_thingee_s132_pca20020.emProject - it makes reference to a lot of files that do not exist. You can compare the list of source files and include paths in the Makefile and see that they are very different.

If I had to guess, I would say that they accidentally uploaded a very old version of their SES project. Also very early on they renamed Thingee->Thingy and the SES project is full of "Thingee" references.

For now, try compiling with the GCC version using the Makefile. You could use the source file listing and include paths from the Makefile to fix your SES project until such a time that Nordic updates it.

[Joakim Jakobsen]

Hi Archer.

I'm afraid Tom is pretty much correct about the SES project from the thingy_sdk_v2.1.0.

The SES project is broken, and was not meant to be released. Sorry for the inconvenience.

However, is is possible to import keil projects to SEGGER Embedded Studio.

Best regards,
Joakim.

[shibshab]

This is an actual issue with Keil on windows 7 (havent tested 10). Put the files deep enough in your folder structure and it will not work. I know its not the issue in this case, but its good to know anyway :)