NRFX_ASSERT

[Canastra]

Hi

I'm new on zephyr and nRF9160.

In the nrfx source are lots of NRFX_ASSERT() macros.

This macro checks a condition and thrown a exception.

Normaly we use asserts in debug code.

In release code we set assert() to an empty macro for speed and codesize.

How can I set NRFX_ASSERT() to an empty macro for nrfx code?

[Øivind]

Hi,

Setting

CONFIG_ASSERT=n

in the prj.conf file will set NRFX_ASSERT() to an empty macro.

[Canastra]

Hi,

Great This 'removes' the NRFX_ASSERT().

Are there other settings to change between debug and release build?

[Øivind]

Just as a troubleshooting step, try to set

CONFIG_FORCE_NO_ASSERT=y

As far as I am aware this config is only intended for testing, but the result will be interesting.

[Canastra]

Hi

I add CONFIG_FORCE_NO_ASSERT=y but the __ASSERT() still generate code.

When I build on the command line I get 

CMake Warning at F:/Programme/Nordic/v1.6.0/zephyr/CMakeLists.txt:1607 (message):
__ASSERT() statements are globally ENABLED

[Øivind]

Does your project build a child image? hci_uart for example? Could the message be coming from the child image build?

[Canastra]

Hi

I don't know what a child image is.

I take the blinky sample, add CONFIG_ASSERT=n and CONFIG_FORCE_NO_ASSERT=y to prj.conf and build with SES.

Attachted is the sample.

In Debugger I search for __ASSERT() and found code behind the macro. (ex. fault.c line 335)

When I build from command line I get

CMake Warning at F:/Programme/Nordic/v1.6.0/zephyr/CMakeLists.txt:1607 (message):
__ASSERT() statements are globally ENABLED

3201.blinky.zip

Hope You find a solution

[Øivind]

Yes, it is coming from the spm child image. The secure partition manager (spm) is included in all non-secure builds.

Make a folder called "child_image" in blinky, put a config file named "spm" in that folder containing the line "CONFIG_ASSERT=n". This will be added to the spm's config file.

You can also remove "CONFIG_FORCE_NO_ASSERT=y" from your regular config file.

[Canastra]

Hi  Øivind

Great work.

Now the __ASSERT() code is gone and the build warning too.

Thanks a lot.