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?

[Canastra]

Hi again,

Is there a similar option to remove __ASSERT()?

Thanks

[Øivind]

__ASSERT() should also be set to an empty macro by "CONFIG_ASSERT=n", are you not seeing that behavior?

We have some release and debug configuations for the nrf desktop sample, which may be useful.
They can be found in the folders at nrf/applications/nrf_desktop/configuration. Seems to mostly be asserts, logging and error handling.
Keep in mind that the configs starting with CONFIG_DESKTOP_* are specific to the sample.

[Canastra]

Hi

When I Set  "CONFIG_ASSERT=n" the NRFX_ASSERTE are removed.

But the __ASSERT() still generate code.

So I need a option to remove __ASSERT().

Thanks for the link nrf/applications/nrf_desktop/configuration. I will check the difference between debug and release.

[Ø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?