Compiling issue with SEGGER EMBEDDED STUDIO V6.30

Hello,

I believe you already saw this thread, which discusses the upgrade to SES v6.2.0 and vfprintf() :

https://devzone.nordicsemi.com/f/nordic-q-a/85405/nrf5-sdk-17-1-0-examples-is-not-compiling-in-latest-ses-6-20a

I believe the same applies to SES v6.30.

BR,

Edvin

I can't understand where to put this line #if !defined(__SEGGER_RTL_VERSION) ... #endif

and more over the removing of file is work out only for non ble_uart example codes

for ble_uart example even removing this file also it has same error SEGGER_RTT_Syscalls_SES  

Hi Edvin ,

This is how i am getting in two different Segger version V5.68 and V6.30 for both nrf5 sdk 17.1.0 and thread v4.2.0

1. ble_blink example nrf 5 SDK

V5.68

V6.30

2. ble_uart_example nRF5SDK

v5.68

V6.30

note: for uart example code the error is different and it is showing the retarget.c

Regarding 2.

nRF Thread 4.2.0

simple_coap_client example

V5.68

V6.30

Hello,

Please try to contact Segger and ask them why the #if is not working, as this information is directly from them:

https://wiki.segger.com/Embedded_Studio_Library_IO

We only officially support the Segger Embedded Version studio up until the one mentioned in the release notes from that specific SDK, which is SES 4.12 in this case. 

BR,

Edvin

Did you got no error while adding #if !defined(__SEGGER_RTL_VERSION)
in SEGGER_RTT_Syscalls_SES.c?

I don't have Segger embedded studio v6.30 installed, because it is not a Segger Embedded Studio version that is supported in any of our SDKs.

If there was something that I could do to figure it out, I would have checked it out. You can exclude the file that includes the __vfprintf.h, and your project will compile, but if you want to use the macro that checks what version you have, we didn't make that, and I don't know how it works, and also I don't have anyone in Nordic that I can check with, because we didn't make it. So I think it is easier if you contact Segger and ask them why it is not working.

Best regards,

Edvin

Hi Edvin,

I've been watching this thread because I have the same problem with SES 6.30. I did manage to figure out that the project has to be explicitly configured to use RTT. Project Options > Library > Debug I/O > RTT. This is a new drop down option.

I also got a " TLS sections are not adjacent" linker error and this is where I threw in the towel. TLS = Thread Local Storage?

Best regards,

Pieter

P.S. The SES license expires and it "forces" one to install the latest version. After renewing the license with the latest version then it is possible to run the old version again. This makes it tough to keep a stable code base supported.

Hi Edvin,

I've been watching this thread because I have the same problem with SES 6.30. I did manage to figure out that the project has to be explicitly configured to use RTT. Project Options > Library > Debug I/O > RTT. This is a new drop down option.

I also got a " TLS sections are not adjacent" linker error and this is where I threw in the towel. TLS = Thread Local Storage?

Best regards,

Pieter

P.S. The SES license expires and it "forces" one to install the latest version. After renewing the license with the latest version then it is possible to run the old version again. This makes it tough to keep a stable code base supported.

I just installed a license on version 5.34, and that worked just fine.

Without having tested myself, I think having several versions of SES may confuse the compiler. Files, such as the thumb_crt0s have a tendency to be picked from the wrong version. I don't have enough knowledge on how this works to say how to change it or what this file does, but I suspect Segger will be able to give a better answer, and perhaps they know why the __SEGGER_RTL_VERSION doesn't work, and perhaps they have another that is working.

BR,

Edvin

I also see a problem with the bootloader on V6.30 (built from secure_bootloader_ble_s140_pca10100 SDK17.1). It compiles but doesn't work (some error causes the device to reset).

I rolled back to Segger v5.66, cleaned and rebuilt the project and it works.

Thank you for the information. 

As stated in the release notes, the older Segger version is the one that is tested for the SDK. Although I am not sure what the changes may be, I would check the included libraries. It happens that some IDEs change the sizes of default parameters, which causes the prebuilt libraries to fault. Did the log say anything about why it crashed? (you probably need to build the _debug bootloader project). 

Best regards,

Edvin

I didn't get to the bottom of it. It requires building debug version as you mentioned. For now i just rolled back to the previous IDE i was working with.