Thingy 52 build error.

[twar]

Hello.

I am trying to build project for thingy52 but since latest release of sdk for thingy does not work well with SES -> https://devzone.nordicsemi.com/f/nordic-q-a/27311/thingy-sdk-compile-error-using-segger-embedded-studio-within-windows-10

I imported keil project into SES but it still does not build correctly for some reason.

1> Output/debug_v1_0_0 Internal/Exe/ble_app_thingy_s132_pca20020.elf does not exist.
1> Linking ble_app_thingy_s132_pca20020.elf
1> "C:/tools/SEGGER/SEGGER Embedded Studio for ARM 3.50/bin/segger-ld" --add-region FLASH=0x00100000@0x00000000 --add-region SRAM=0x00040000@0x20000000 --defsym=__STACKSIZE__=1024 --defsym=__STACKSIZE_PROCESS__=0 --defsym=__HEAPSIZE__=1024 --full-section-headers -ereset_handler --defsym=__vfprintf=__vfprintf_int_nwp --defsym=__vfscanf=__vfscanf_int --silent --list-all-undefineds --fatal-warnings -EL -mcpu=cortex-m4 "-TC:/tools/SEGGER/SEGGER Embedded Studio for ARM 3.50/samples/SEGGER_Flash.icf" -Map "Output/debug_v1_0_0 Internal/Exe/ble_app_thingy_s132_pca20020.map" -u_vectors -o "Output/debug_v1_0_0 Internal/Exe/ble_app_thingy_s132_pca20020.elf" "@C:/Downloads/thigy/thingy_sdk_v2.1.0/project/pca20020_s132/arm5_no_packs/Output/ble_app_thingy_s132_pca20020 debug_v1_0_0 Internal/Obj/ble_app_thingy_s132_pca20020.ind"
1>
1> Diagnostics:
1>   error: undefined symbol: SystemCoreClock
1>   error: undefined symbol: __data_start__
1>   error: undefined symbol: __start_fs_data
1>   error: undefined symbol: __stop_fs_data
1>   error: undefined symbol: arm_sin_f32
1>   error: undefined symbol: inv_enable_9x_sensor_fusion
1>   error: undefined symbol: inv_enable_fast_nomot
1>   error: undefined symbol: inv_enable_gyro_tc
1>   error: undefined symbol: inv_enable_heading_from_gyro
1>   error: undefined symbol: inv_enable_in_use_auto_calibration
1>   error: undefined symbol: inv_enable_magnetic_disturbance
1>   error: undefined symbol: inv_enable_quaternion
1>   error: undefined symbol: inv_enable_vector_compass_cal
1>   error: undefined symbol: nfc_t2t_emulation_start
1>   error: undefined symbol: nfc_t2t_payload_set
1>   error: undefined symbol: nfc_t2t_setup
Build failed

Btw I excluded RTT_Syscalls_KEIL.c from build because it gave me some compiler error about those two includes not being found:

#include <rt_sys.h>
#include <rt_misc.h>

Thank you for your help and best regards.

[AndreasF]

Hi.

If you want to import a KEIL project into SES, you should take a good look at this guide.

- Andreas

[twar]

That did not help a lot.

I built using make but those Makefile are incorrect either they all have path messed up when it comes to source files and header files.

[AndreasF]

Hi.

Since we do not really have any support at the moment for SES in the Thingy SDK, its really hard to make this work.

But if you dont want to use keil, you could always compile with armgcc?

I compiled the project in the Nordic-Thingy52-FW-master\project\pca20020_s132\armgcc folder using the command make -j without any problems.

- Andreas

[jp54l]

Hi Andreas

I'm having exact same problem as twar.

I finally got the thingy project to compile successfully and now I get a linker error



Can you point me in the right direction to solve this.

Regards
Jerome

[AndreasF]

Hi Jerome.

The SES Project for the Thingy:52 is broken, and was not supposed to be published with the Thingy:52 SDK.

You can find a copy of the Thingy:52 SDK (v2.0.0) with a project ported to SEGGER Embedded Studio attached below. 
Please follow the instructions in README.md to install the SDK.

You can find the project file of the example in the following folder: <InstallFolder>\project\pca20020_s132\ses

Thingy52_wSES_FW.zip

Note: 
This application is one of several applications that has been built by the support team at Nordic Semiconductor, as a demo of some particular feature or use case. It has not necessarily been thoroughly tested, so there might be unknown issues. It is hence provided as-is, without any warranty.


Best regards,

Andreas

[jp54l]

Hi Andreas

After revisiting this....it appears the project does is set up differently than the binary that runs on the Thingy.

After loading Thingy with the project hex the LED green flashes....but does not accept connection from the Thingy app.

Is there a version of the project, that is identical to pre-compiled hex file?

The pre-compiled hex file runs as expected and allows connections from the app.

Any assistance would be much appreciated.

[Kenneth]

Andreas is out of office, have you tried:

https://devzone.nordicsemi.com/f/nordic-q-a/46171/thingy-52-sdk-generate-smaller-hex-than-precompiled-thingy-52-hex 

[jp54l]

Hi Kenneth

Yes, that is not the problem as I flash the thingy from SES which loads the softdevice prior to flashing the thingy applicaiton.

I'm not sure where else to look I could spend many hours debugging and stepping through the immense code and not get anywhere, surely someone at Nordic could identify the issue and offer a fix very quickly???

[Kenneth]

Have you tried to download the latest master of thingy52 from github?
https://github.com/NordicSemiconductor/Nordic-Thingy52-FW 

[jp54l]

Hi Kenneth

I have the Thingy 52 git repository cloned on my PC and have already tried reverting to a previous release, unfortunately, what makes this more difficult is there is no working SES project and that is all I can use as I don't have licenses for the other IDEs. Importing the Keil project yields no joy.

I have the same symptoms on the thingy as this user which posted a few days ago, unsure whether he fixed his issue. It seems to be a common problem.

https://devzone.nordicsemi.com/f/nordic-q-a/55201/thingy-52-custom-firmware

When I read back the memory from nRF connect, after flashing from SES, the app and softdevice are programmed.

Again it runs, but does not work to app and does not accept connections.