Compiling with SDK on desktop for unit testing

[Nathan O.]

Hi,

I am working on a product based on an nRF52832.

For testing purposes, I have setup the Unity testing framework (using Ceedling).

As soon as a module I want to test includes a file from the nrf5 SDK, I get compiler error :

First I had issues with __STATIC_INLINE. I then added a define for __unix so that nrf.h would not include the hardware specifics headers. I then added a definition for __STATIC_INLINE through a -D compiler option.

Now my problem is that I get undefined errors from modules using IRQs (as IRQn_Type is defined in nrf52.h that is therefore not included).

Is there a proper way to run the SDK files on a desktop / host without having to redefine all these ?

Is anyone else using Unity testing framework to test their modules on a desktop / server setup (not on target) ?

Regards

[Krzysztof Chruscinski]

Hi,

we also use unity but we modified it to inject special defines to allow mocking static inlines. Unfortunately, it is quite coupled with test framework so I won't be able to share it with you.

You can take a look at how we approached this issue in nRF Connect SDK:  http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_unity_testing.html

Basically, we are first preprocessing the headers to replace or static inline functions with standard function declarations and that is passed to mock generator. I think this may work for you.

Here is the script: https://github.com/nrfconnect/sdk-nrf/blob/master/scripts/unity/header_prepare.py 

Note that script contains conversions specific to zephyr (syscalls removal).