problem with serial flash memory interface

RE: problem with serial flash memory interface

Naeem Maroof — Mon, 03 Jul 2023 15:07:46 GMT

Hi Paul,

That should not be a problem

You may combine spi and ble related code from relevant examples.

RE: problem with serial flash memory interface

paul0208 — Sat, 01 Jul 2023 07:21:45 GMT

Hi,

I found that nrf_drv_spi_init() in the example of /peripheral/spi, does return success result.
But my call nrf_drv_spi_init() does not return anything one, stucking in rnf_drv_spi_init().

The example of /peripheral/spi does not use softdevice, but my app use softdevice.
Is it can be a reason of stucking in nrf_drv_spi_init();?

BR
Paul

RE: problem with serial flash memory interface

Naeem Maroof — Fri, 30 Jun 2023 11:07:24 GMT

Hello Sangdo Lee,

Thank you for contacting DevZone at NordicSemi.

The spi initializer function would take the driver instance, initial configurations, handler function, and the context passed to event handler

ret_code_t nrf_drv_spi_init	(   nrf_drv_spi_t const *const 	    p_instance,
                                nrf_drv_spi_config_t const * 	p_config,
                                nrf_drv_spi_evt_handler_t 	    handler,
                                void * 	                        p_context 
                            )

The function would return the code with one of the following values:

NRF_SUCCESS	If initialization was successful
NRF_ERROR_INVALID_STATE	If the driver was already initialized
NRF_ERROR_BUSY	If some other peripheral with the same instance ID is already in use

I suggest not to put printk() and/or any kind of debugging / logging statements in the initializer function and rather check what value the function is returning in your main code.

Here is an example of checking return value in the nrf5 sdk17.1.0 in the /peripheral/spi/ sample:

APP_ERROR_CHECK(nrf_drv_spi_init(&spi, &spi_config, spi_event_handler, NULL));

BR,

Naeem