nRF5 SDK 17.1.0 examples is not compiling in latest SES (6.20a)

[Fredrik Malmsten]

e.g, when compiling ble_app_hrs I get:

7> Compiling ‘cc310_backend_eddsa.c’
4> C:\nRF\nRF5SDK\external\segger_rtt\SEGGER_RTT_Syscalls_SES.c:76:10: fatal error: __vfprintf.h: No such file or directory
4> 76 | #include "__vfprintf.h"

Should I downgrade SES or is there any better solution to get a quick start?

[mconnor]

Hi,

I am having the same issue running the newest sdk 17.1 and SES 6.20. When I remove the file SEGGER_RTT_Syscalls_SES.c I get an error: 

Building ‘ble_app_blinky_c_pca10040_s132’ from solution ‘ble_app_blinky_c_pca10040_s132’ in configuration ‘Debug’[0m
1> Compiling ‘bsp_btn_ble.c’[0m
2> Compiling ‘main.c’[0m
4> Compiling ‘SEGGER_RTT.c’[0m
3> Checking Source File Exists[0m
3> C:/nRF5_SDK_17.1.0_ddde560/external/segger_rtt/SEGGER_RTT_Syscalls_SES.c does not exist.[0m
Build failed[0m

but when I do not remove the file I get the aforementioned issues already outlined here, namely, the vprintf.h issue.

I feel like I am in a catch-22 please help.

Regards

Matt

[Einar Thorsrud]

Hi Matt,

From what I can see, the only file in the SDK that includes __vfprintf.h is SEGGER_RTT_Syscalls_SES.c. So you really should not get this error when you have removed SEGGER_RTT_Syscalls_SES.c from the project. Looking at your log snippet it seems that SES is trying to find SEGGER_RTT_Syscalls_SES.c, so apparently it has not been removed from the project or perhaps something is cached so that you need to clean all build output and try building again.