SD Card, FATFS, nRF52832 -> Can't initialize if first initialization fails.

RE: SD Card, FATFS, nRF52832 -> Can't initialize if first initialization fails.

DGraham — Fri, 01 Feb 2019 17:55:58 GMT

This solved the problem. I should've mentioned I'm currently using SDK 14.2.0, but I found the corresponding lines to fix (nrf_drv_spi.c -> nrf_drv_spi_uninit and diskio_blkdev.c-> disk_initialize).

Thank you.

Edit: It stopped working a few days later and it took me a little while to figure out why. The SD card isn't the only peripheral on the bus, and at some point the pull configuration changed. In the sdk_config.h you need to set the NRF_SPI_DRV_MISO_PULLUP_CFG flag to 3 (pullup). If you use NOPULL or PULLDOWN it won't work.

RE: SD Card, FATFS, nRF52832 -> Can't initialize if first initialization fails.

Einar Thorsrud — Fri, 01 Feb 2019 14:02:40 GMT

Hi,

I have reproduced this on my side as well using DK 15.2. It seems the internal state of nrf_block_dev_sdc.c (m_active_sdc_dev) becomes invalid, as it is not uninitialized. Therefore, it will always return NRF_ERROR_BUSY after the first unsuccessful attempt. The following two minor diffs shows what seems like a quick fix:

devzone.nordicsemi.com/.../diskio_5F00_blkdev.c.diff

devzone.nordicsemi.com/.../nrfx_5F00_spim.c.diff

I will report this internally as a bug.