KEIL build with SDK 16.0.0 fails

RE: KEIL build with SDK 16.0.0 fails

Edvin — Thu, 04 Mar 2021 21:49:24 GMT

Hello,

That is a good idea. I can't discuss Nordic's roadmap details here on DevZone. For such questions, please contact our RSM (Regional Sales Manager) for your region. If you are already in contact with a Sales Rep, you can use that person. If not, please let me know if you are interested in the RSM details. Send me a PM containing your location, and I will send you the contact details.

BR,

Edvin

RE: KEIL build with SDK 16.0.0 fails

RVM — Thu, 04 Mar 2021 17:37:53 GMT

This is like pulling teeth here....

Maybe I should send an email to my Nordic FAE/Sales Rep and ask them when they will be releasing a version that is compatible with ARM KEIL compiler versions 6.x

RE: KEIL build with SDK 16.0.0 fails

awneil — Thu, 04 Mar 2021 08:55:36 GMT

https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/index.html

RE: KEIL build with SDK 16.0.0 fails

RVM — Wed, 03 Mar 2021 16:28:52 GMT

If it helps Nordic to fix the SDK, here is the offending piece of code from the file 'nrf_svci.h' in SDK 16.0.0, starting from line 123.

The problem is in the assembler command at line 133: " ldr r12, = %0 \n"
The =%0 gets translated to, in my specific case, as '=#3' and that is invalid ARM assembly command.

#if defined (__GNUC__)

    #define SVCI_DECL_0(svci_num, return_type, function_name)           \
        _Pragma("GCC diagnostic push")                                  \
        _Pragma("GCC diagnostic ignored \"-Wreturn-type\"")             \
        __attribute__((naked, unused))                                  \
        static return_type svci_ ## function_name(void)                 \
        {                                                               \
            /* Do the SuperVisor call by using svc instruction with     \
               R12 containing the SVCI number */                        \
            __ASM __volatile                                            \
            (                                                           \
                "  ldr r12, =%0       \n"                               \
                "  svc %1             \n"                               \
                "  bx lr              \n"                               \
                "  .ltorg"                                              \
                : /* output */                                          \
                : /* input */                                           \
                    "X"(svci_num),                                      \
                    "I"(GCC_CAST_CPP NRF_SVCI_SVC_NUM)                  \
                : /* clobbers */                                        \
                    "r12"                                               \
            );                                                          \
        }                                                               \
        _Pragma("GCC diagnostic pop")    
    
    #define SVCI_DECL(svci_num, return_type, function_name, ...)        \
        _Pragma("GCC diagnostic push")                                  \
        _Pragma("GCC diagnostic ignored \"-Wreturn-type\"")             \
        __attribute__((naked, unused))                                  \
        static return_type svci_ ## function_name(__VA_ARGS__)          \
        {                                                               \
            /* Do the SuperVisor call by using svc instruction with     \
               R12 containing the SVCI number */                        \
            __ASM __volatile                                            \
            (                                                           \
                "  ldr.w r12, =%0     \n"                               \
                "  svc %1             \n"                               \
                "  bx lr              \n"                               \
                "  .ltorg"                                              \
                : /* output */                                          \
                : /* input */                                           \
                    "X"(svci_num),                                      \
                    "I"(GCC_CAST_CPP NRF_SVCI_SVC_NUM)                  \
                : /* clobbers */                                        \
                    "r12"                                               \
            );                                                          \
        }                                                               \
        _Pragma("GCC diagnostic pop")

RE: KEIL build with SDK 16.0.0 fails

RVM — Wed, 03 Mar 2021 16:24:04 GMT

The release note says that one needs to 'download a previous version of the MDK' from another website, and not to mention that it only works with KEIL compiler version 5.x

My question was if there was a version that will build with KEIL compiler version 6.x

But I am not getting an answer to that question.

RE: KEIL build with SDK 16.0.0 fails

awneil — Wed, 03 Mar 2021 16:21:31 GMT

The SDK Release Notes say what versions of tools they work with

RE: KEIL build with SDK 16.0.0 fails

RVM — Wed, 03 Mar 2021 16:17:54 GMT

[quote userid="6462" url="~/f/nordic-q-a/72282/keil-build-with-sdk-16-0-0-fails/297594#297594"]

If it really is the compiler, then that's a question for Keil - not Nordic.

https://community.arm.com/developer/tools-software/tools/f/keil-forum

[/quote]

Well, my original post was a request to get a version of the SDK that builds with KEIL compiler -- a question to Nordic, not KEIL. Besides, the problem is in the ASM fragment that translates and forwards the SoftDevice service call to the SVC handler, also provided by Nordic.

RE: KEIL build with SDK 16.0.0 fails

awneil — Wed, 03 Mar 2021 16:11:02 GMT

[quote userid="86158" url="~/f/nordic-q-a/72282/keil-build-with-sdk-16-0-0-fails"]the ARM Compiler defines the symbol __GNUC__ [/quote]

Are you sure it's the compiler, and not something in the Nordic stuff that is defaulting to __GNUC__ in the absence of anything else it recognises?

If it is in the code, you should be able to find it with 'Go To Definition'

[quote userid="86158" url="~/f/nordic-q-a/72282/keil-build-with-sdk-16-0-0-fails"]is there any other option to convince the KEIL build system to not define __GNUC__[/quote]

If it really is the compiler, then that's a question for Keil - not Nordic.

https://community.arm.com/developer/tools-software/tools/f/keil-forum

You could check if there are any other uniquely identifying symbols for CC_ARM - and use that to #undef __GNUC__

RE: KEIL build with SDK 16.0.0 fails

RVM — Wed, 03 Mar 2021 15:51:28 GMT

If it helps, starting with version 6.x, the ARM Compiler uses CLANG which is also used by GCC which leads to the side effect (not sure if it was intentional or accidental) that it defines the symbol __GNUC__.

I did try to use version 5.x of the compiler but that led to a whole slew of other errors SDK, most of which I got rid of when I set the language to use C90 and GNU Extensions.... but I prefer something more recent and robust.

RE: KEIL build with SDK 16.0.0 fails

RVM — Wed, 03 Mar 2021 15:35:41 GMT

I found this in two ways.

The initial indication is due to the fact that the GUI parses the files behind the scenes and enables code within valid #if .... #else ... clauses.

The second, more accurate method, was that I edited the specific file and added a statement '#error FIXME' within the code fragment contained inside the #if defined(__GNUC__) .... #else combination and that line triggered that error and failed during the build.

RE: KEIL build with SDK 16.0.0 fails

Edvin — Wed, 03 Mar 2021 13:28:51 GMT

Hello,

I am not sure what setting that changes this. By searching for it it says that the __CC_ARM is always defined as 1 when using the Keil compiler. How did you determine that it was not?

Perhaps you can try to compare your project settings with one of the Keil projects found in our SDK and see if you can see anything that differs? If you can't find anything, perhaps you need to ask Keil directly.

Another option is to take a project that is already set up using Keil from our SDK, and swap it with your files.

Best regards,

Edvin