FatFs_uSD_Standalone Example for STM32G474E_EVAL board

[Ana]

Hello,

I'm new to this community  and I'm trying to learn from different examples that are available online. I have STM32G474E-EVAL1 board and I want to include the sd card in one of my projects. So I founded the FatFs_uSD_Standalone Example that was originally for the STM32G474E-EVAL board. I was able to compile it successfully and tried to run it in the debug mode on my EVAL1 board but it fails in the 'SD_GoIdleState(void)' function. Is there any particular reason that the code wouldn't run properly on my EVAL1 board ? I've checked that the sd connector does receive 3.3 V.

Thanks in advance

[ELABI.1]

Hi @Ana ,

In fact, the STM32G474E-EVAL1 is recommended to be used for the motor control configuration board

This information is already mentioned below:

When comparing the obsolete STM32G474E-EVAL Board REV B-04 with the STM32G474E-EVAL1 board, we found that the uSD chip select pin does not fit. Therefore, the uSD chip select pin (PF8) must be fitted on the STM32G474E-EVAL1 Board.

Thank you.

ELABI.1

[Andrew Neil]

---

@Ana wrote:

Is there any particular reason that the code wouldn't run properly on my EVAL1 board ?

---

Check the schematics - are all the IOs required by the example free & available on the EVAL1 board ?

---

@Ana wrote:

I've checked that the sd connector does receive 3.3 V.

---

and what about all the other pins used by the SD-Card?

---

@Ana wrote:

it fails in the 'SD_GoIdleState(void)' function.

---

What debugging have you done to find how & why it "fails" ?

[Ana]

Hi,

Thank you so much for the reference, this board schematic is exactly what I was looking for (found on MXCube, the names of the files are a little bit confusing:

Both of them are  B04 revisions and the part number in both of the files is the obsolete STM32G474E-EVAL.)

I'll update here if this helped to solve the problem.

Thank you

[Ana]

Hi Andrew,

Thank you for the answer, I hope that the first reference will help to solve the problem. About your second reference - I have mistakenly checked the wrong board schematics, so I'll check again all the pins. About your third reference - I entered with the debugger into the hippest function and checked where and when exactly the ERROR CODE was updated, this actually happened when the SD card didn't return answer' so I suppose it's really more of a hardware problem.

I'll update here when I'll be able to fix the problem.

Thanks