Compiling issue with SEGGER EMBEDDED STUDIO V6.30

[Sunil vignesh]

Hi,

  I am working with the nRF5SDK , nRF Thread SDKs long time. Recently i have update segger embedded studio to V 6.30 . previously i have used v5.68

1.

for nRF 5 SDK while build the ble_blinky example code  i got an error __vfprintf.h: No such file or directory

i found the solution that by removing the SEGGER_RTT_Syscalls_SES.c .and rebuild the code it is working

but i need the solution that without removing the SEGGER_RTT_Syscalls_SES.c how to build the project

because i need to work this project in both older / newer version of segger embedded studio

2.

also tried to work with nrf thread sdk 4.2.0 -thread_simple_coap_client_pca10056 . there i am facing same error __vfprintf.h: No such file or directory

while is remove SEGGER_RTT_Syscalls_SES file and rebuild the code i am facing some other errors

 
  Linking thread_simple_coap_client_pca10056.elf
    E:/nRF5x/2.thread_4.2.0/examples/thread/simple_coap_client/pca10056/blank/ses/Output/Debug/Exe/thread_simple_coap_client_pca10056.elf: TLS sections are not adjacent:
            TLS: .tdata
        non-TLS: .bss
            TLS: .tbss
    map sections to segments failed: bad value
Build failed

[Edvin]

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

[Sunil vignesh]

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  

[Edvin]

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

[pieterc]

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.

[Edvin]

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

[Timor]

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.

[Edvin]

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

[Timor]

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.