nrfx_spim not enabled through sdk_config.h with SPI_ENABLED , NRFX_SPIM_ENABLED as NRFX_SPIM3_ENABLED is missing

Hi,

apply_old_config.h is intended only for use with legacy drivers. SPIM3 is not supported by the legacy driver. If you want to use SPIM3, I would recommend completely removing the legacy SPI_ENABLE config from sdk_config.h and configure the nrfx_spim driver directly using NRFX_SPIM_ENABLE configs.

Best regards,
Jørgen

On one side, I've got you telling us to use the NRFX drivers, whilst I have Nordic's Einar Thorsrud telling me I have to use the legacy libraries if I want my project to include the SoftDevice (which uses the AppTimer, which is tied to the legacy libraries).

e.g. This exchange:

Nicholas Lee said:

I quote from your website: "For new applications, consider to use the new nrfx API."
This instruction seemed perfectly clear and unequivocal to us.
ref: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.2.0%2Fnrfx_migration_user_guide.html

I am painfully aware of the documentation suggesting that you use the nrfx API direclty. It has been reported internally and will hopefully be fixed at some point.

I need SPIM3 working with EasyDMA functionality, in the same project as a working Bluetooth radio link.
The "example" code for the SPI Transcation Manager doesn't include anything which tells me how to do this.

Can Nordic please get their story straight regarding the use of NRF vs NRFX code, and tell me how I am supposed to do this. The documentation is useless and I have now wasted thousands on consultancy hours trying to get this working.

On one side, I've got you telling us to use the NRFX drivers, whilst I have Nordic's Einar Thorsrud telling me I have to use the legacy libraries if I want my project to include the SoftDevice (which uses the AppTimer, which is tied to the legacy libraries).

e.g. This exchange:

Nicholas Lee said:

I quote from your website: "For new applications, consider to use the new nrfx API."
This instruction seemed perfectly clear and unequivocal to us.
ref: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.2.0%2Fnrfx_migration_user_guide.html

I am painfully aware of the documentation suggesting that you use the nrfx API direclty. It has been reported internally and will hopefully be fixed at some point.

I need SPIM3 working with EasyDMA functionality, in the same project as a working Bluetooth radio link.
The "example" code for the SPI Transcation Manager doesn't include anything which tells me how to do this.

Can Nordic please get their story straight regarding the use of NRF vs NRFX code, and tell me how I am supposed to do this. The documentation is useless and I have now wasted thousands on consultancy hours trying to get this working.