Again messing with the nrfx drivers, glue and error headers.

RE: Again messing with the nrfx drivers, glue and error headers.

rico — Thu, 14 May 2020 08:55:31 GMT

I think that is what i was missing! I will mark as solved as soon as i can test it, but it seems to be the way it did it with the last project in SES aswell.

Thanks.

RE: Again messing with the nrfx drivers, glue and error headers.

hmolesworth — Thu, 16 Apr 2020 15:52:25 GMT

This issue has wasted untold hours for us, mostly due to migrating across versions from 14.2 to 15.2, 15.3 and 16.0. I monitor nRFx on github for updates, but sometimes a simple override helps. Here is an example (nRF52840 with SPI3, but nRF52832 is same general idea):

// Example:
// Add "FEATURE_REQUIRE_NRFX_SPIM3" to the project preprocessor definitions

// Add this at the top of sdk_config.h:
#if defined(FEATURE_REQUIRE_NRFX_SPIM3)
#define SPIM_PRESENT               1
#define NRF_SPI_ENABLED            1//0
#define NRFX_SPI_ENABLED           1//0
#define NRF_SPIM3_ENABLED          1//0
#define NRFX_SPIM_ENABLED          1//0
#define NRFX_SPIM3_ENABLED         1//0
#define NRFX_SPIM_EXTENDED_ENABLED 1//0
#endif

There is also a _glue and _legacy header which might require using (in this case) FEATURE_REQUIRE_NRFX_SPIM3 as a conditional, I forget but will edit later if it comes to mind.

RE: Again messing with the nrfx drivers, glue and error headers.

Nguyen Hoan Hoang — Thu, 16 Apr 2020 14:29:57 GMT

Don't under estimate C++. See this post https://devzone.nordicsemi.com/f/nordic-q-a/53106/uart-communication-fifo-error. There is a comparison of uart driver implementation. The C++ IOsonata is about 15-20% faster than nrfx. Even without DMA IOsonata is still faster then nrfx with DMA. All that without the #defines jungle of the sdk_config.h

RE: Again messing with the nrfx drivers, glue and error headers.

Simonr — Thu, 16 Apr 2020 06:56:20 GMT

Hi Rico

Have you checked out the nrfx set of drivers on our GitHub with its own documentation files? The intention of this page is to provide drivers that can be used in other projects than the SDK examples.

The recommended development process from Nordic is to start out with an SDK project where these drivers are already implemented and add whatever you'd like from there.

Best regards,

Simon

RE: Again messing with the nrfx drivers, glue and error headers.

rico — Wed, 15 Apr 2020 11:27:31 GMT

Thanks for the tip I will have a look at it, but I would like to stick with C at the moment.

RE: Again messing with the nrfx drivers, glue and error headers.

Mojo — Mon, 23 Mar 2020 16:33:07 GMT

I use this library https://github.com/IOsonata/IOsonata

It compile most used part of the SDK into it and it's drivers are better designed and better performance than the SDK. Best of all, no sdk_config jungle. Only one drawback, It's C++ so it won't work with SES. But no worries, even though it is C++ object designed, It is still more performance the plain C driver of the SDK. Eclipse is the preferred IDE but you can also use it with IAR, Keil and CrossWorks but not with SES.