Thingy SDK compile error using Segger Embedded Studio within Windows 10

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Joakim Jakobsen — Fri, 23 Aug 2019 10:27:01 GMT

No problem, happy to help!

I will forward your feedback about the GitHub repo.

Cheers,
Joakim

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

jp54l — Fri, 23 Aug 2019 10:23:17 GMT

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

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Joakim Jakobsen — Wed, 21 Aug 2019 08:27:18 GMT

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

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

jp54l — Wed, 21 Aug 2019 05:19:18 GMT

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

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Joakim Jakobsen — Thu, 17 Jan 2019 14:05:53 GMT

Hi.

Maybe you create a new support ticket regarding this?

You can mention that the ticket is for me (Joakim) so that the ticket will be assigned to me.

Best regards.

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Niteesh — Thu, 17 Jan 2019 07:16:34 GMT

I added RTT_Syscalls_SES.c in place of RTT_Syscalls_KEIL.c. However, I am getting a number of errors like this.

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Niteesh — Thu, 17 Jan 2019 06:59:41 GMT

This does not work for the Thingy. occ_lib_nrf52.lib does not exist in the Thingy FW

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Joakim Jakobsen — Thu, 08 Feb 2018 09:36:10 GMT

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.

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

iotlight — Wed, 07 Feb 2018 21:43:36 GMT

After I moved the entire Thingy_sdk to c:\Nordic as suggested in the link, I got the following result:
I don’t know which folder I should put the RTT_Syscalls_SES.c file.
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.

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Joakim Jakobsen — Fri, 24 Nov 2017 13:12:39 GMT

Hi again Archer!
The RTT_Syscalls_KEIL.c should be removed from your project, and the RTT_Syscalls_SES.c added instead.
You should be able to find the RTT_Syscalls_SES.c file in you SES install folder;
<InstallFolder>\SEGGER\SEGGER Embedded Studio 3.30\samples
If not, you can copy the file from the newest SDK (v14.1.0).

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Archer — Wed, 22 Nov 2017 02:35:59 GMT

Hi Joakim,

Okay. The "nrf.h: No such file or directory". issue was gone after adding the path in preprocessor definitions. Thanks.

But it appeared another error that is Compiling ‘RTT_Syscalls_KEIL.c’ rt_sys.h: No such file or directory

I found out a link, link text, that had same problem, however I can't find the occ as its mentioned.

Could you please help to take a look?

Thanks

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Joakim Jakobsen — Mon, 20 Nov 2017 14:45:06 GMT

Hi Archer.
You shouldn't need any knowledge about Keil, as you only import the Keil project file to SES.
As for the nrf.h file not being found, you should check that the path to the file is added in your preprocessor definitions.
I haven't tried importing it myself yet, but I will try it and let you know the result.

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Archer — Fri, 17 Nov 2017 09:58:02 GMT

Hi Joakim,

I tried to follow the steps in the link. (Note: I never used Keil IDE before.) However, when I did "Building" step, it appeared a error, "nrf.h: No such file or directory".

So, I just have a simple thought, is it possible to write a instruction that is for importing Thingy SDK to SES to me for reference?

Thanks.

Regards.

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Archer — Fri, 17 Nov 2017 09:16:55 GMT

Hi Tom,

Understood. Thanks for your information.

Sincerely.

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Joakim Jakobsen — Fri, 17 Nov 2017 08:42:27 GMT

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.

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

shibshab — Fri, 17 Nov 2017 08:34:18 GMT

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 :)

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Joakim Jakobsen — Fri, 17 Nov 2017 07:11:12 GMT

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.

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Tom — Thu, 16 Nov 2017 21:22:56 GMT

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.

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

Tom — Thu, 16 Nov 2017 20:47:09 GMT

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

RE: Thingy SDK compile error using Segger Embedded Studio within Windows 10

shibshab — Thu, 16 Nov 2017 11:21:02 GMT

There might be issues with long path names.

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