SD CARD - UNABLE TO INTERFACE

[Srinivasan M]

Posted on March 28, 2018 at 17:00

Hello, 

We are using ST32F405ZG and ST-Nucleo with a custom board design with SD card interface provision in it.

   

We are getting an error message as shown in the snap shot attached. Please provide some help in this issue.

with regards,

Srinivasan M

[Tesla DeLorean]

Posted on March 28, 2018 at 17:14

Would seem like you've balls up something in the design or connectivity...

No design details provided. It's a custom board so no one here was involved or familiar with the design.

Make sure the Nucleo on-board target is disconnected.

Check usual issues/suspect, covered here dozens of times, 

Voltages on VDD, AVDD

Voltages on VCAP pins

Voltage on NRST pin

Accessibility of System Loader when BOOT0=High and connected to USART1 PA9/PA10

[Andrew Neil]

Posted on March 28, 2018 at 19:27

We are getting an error message as shown in the snap shot attached

Those messages are your Eclipse IDE debugger failing to connect via the ST-Link - this has nothing to do with the SD Card interfacing!

[Srinivasan M]

Posted on March 29, 2018 at 11:45

Hi, 

Thank you for the reply.

I have gone through the code examples and found that the line below was missing in my code under the file 'Logic_Config_Touch_4.cfg' :

reset_config srst_only srst_nogate

This made the program to build and upload the program to the controller.

But now the issue is SD card is not getting mounted using FATFS thirdparty library.

The program executes and skips out of the mount function stating FR_INVALID_DRIVE

now I got got stuckup at this point. Don't know what to do next...

[Andrew Neil]

Posted on March 29, 2018 at 11:56

This made the program to build

That has nothing to do with building the code - it is purely debugger configuration.

The program executes and skips out of the mount function stating FR_INVALID_DRIVE

now I got got stuckup at this point. Don't know what to do next

Look at the FatFs documentation for information about the 

FR_INVALID_DRIVE error, and what constitutes a valid drive.

Look at the code and see what are the possible causes of an 

FR_INVALID_DRIVE error.

[Srinivasan M]

Posted on March 29, 2018 at 12:43

>

>

That has nothing to do with building the code - it is purely debugger configuration.

>

I meant - 'build and upload the program to the controller' because of that line it was not uploading the program to the controller.

>

>

Look at the FatFs

documentation

for information about the 

FR_INVALID_DRIVE error, and what constitutes a

valid

drive.

>

It says:

FR_INVALID_DRIVE:

Invalid drive number is specified in the path name. A null pointer is given as the path name. (Related option: FF_VOLUMES)

We went through the check and identified that the path name is different and the SD card slot was not working. Later we changed the SD card slot and now its working fine and the file is generated.

Thanks for all your bullet fast help....