This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Lots of warning in Nordic library

I use the SES ver 4.12 with embOS of Segger.

It happened to me all the time.

I take an example from Nordic. I rebuild it with no warning. Then I take and add my files , build a new app. On rebuild I have no error but a lot of worning comming only from the Nordic standard lib.

FOr example:

#if NRF_MODULE_ENABLED(XXXX)

*XXX mean different defines

with warning "this use of "defined" may not be portable [-Wexpansion-to-defined] "

It show on all libraries 

In app_timer.c this warning.

Like "no previous prototype for 'RTC1_IRQHandler' [-Wmissing-prototypes]" because there is no declare in the h. (How it can be use in different c files without declare in the h file?

and it get repeated again and again. 

I get about 3600 warning from those types.

1. Is it something I need to be worry about ?

2. Why it is show in Nordic library which show be clean from warnings?

3. If it is not critical and usual, can I  change any setting not to see them?

Regards

Bar.

  • Hello Bar,

    Did you include the file ses_startup_nrf52840.s file in your project? This file is included in the examples in the SDK, and is probably the reason why you don't get the same warnings there.

    That being said, I am not too familiar with embOS.

  • Hello Advin.

    I have some time now to go back to this issue.

    I made the  change but still all warning. see 1 example attach. I have lots of it.

    It is not concern the embOS because it is only the envelope and not the task themself.

    I also try to close all warning and open them individually in my files (to see if I do any warning) but still it show me warning in Nordic librery especially in the BLE_lib because I include H files from there.

    Did anyone in Nordic try to get ride of those warnings?

    Regards

    Bar.

  • Hello Bar,

    I suggest that you start with an example from the SDK, and add the things you want to use from embOS. The projects from the SDK is correctly set up. We don't officially support embOs. You may use it, but you need to include all the files that are necessary from the SDK.

Related