• State Suggested Answer
  • Replies 17 replies
  • Answers 1 answer
  • Subscribers 70 subscribers
  • Views 11821 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 125950
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

sd card example not working fine

YASH

Hi All,

I am working on fatfs example from sdk 12.2.0 on pca10040, nrf52 dk, nrf52832. And i did not change anything in the code but it seems that my sd card is not getting initialized as i am getting following message on putty:-

APP:INFO: FATFS example.

APP:INFO:Initializing disk 0 (SDC)...

APP:INFO:Disk initialization failed.

and on debug, my code goes into this if condition in diskio_blkdev.c file:- Line no.-81

if (m_drives[drv].config.wait_func == NULL)
{
    m_drives[drv].config.wait_func = default_wait_func;
}

can anyone help me understand the reason behind why this is happening and how i should deal with it?

Thank in advance.

Regards

  • 0 in reply to NickH

    Have you double-checked the connections to the SD card? I have tested this example multiple times with different SD cards and have not experienced issues when the connections are correct. Please also test with different SD cards and sockets if you have made sure everything else is correct.

    If nothing of this helps, please post a new case where you describe your issue in detail, along with all debugging steps you have tried.

  • 0 in reply to NickH

    Hi there, I also experienced issues with the SD card.

    This worked for me:

    - Set all pins to PULLUP or NOPULL

    - Place a 20K resistor between 3.3V and MISO (basically an external pullup)

    I also experienced a problem where if I have certain NRF pins set as one of the SD pins, the SD example would freeze and not proceed past a certain point, even with nothing connected to the board. (Example being setting P0.09 to SD SPI CLK will freeze, but changing to P0.20 works even though nothing is connected to the board. (This appears to be an SDK bug)

Related