Actions
Forum Thread Details
  • Replies 3 replies
  • Subscribers 6 subscribers
  • Views 1990 views
  • Users 0 members are here
Related

STM32F4 Discovery - problem interfacing SD card

Former Member

Greetings all,

 

I am trying to make STM32F4 (on STM32F4 Discovery board) write a text file on an SD card, but with no success at all. I have tried this example by clive1 (flashing with hex/bin file directly). And also I have tried both, SPI and SDIO examples from this site. In the project from second example I placed "debugging" LED after the line: if (f_mount(&FatFs, "0:", 1) == FR_OK) And it seems the if condition isn't met, because LEDs don't turn on. Program ends in while(1) loop.

 

I believe my wiring is ok and also I am using new Micro SD card (tried also SD with SPI), but no success. Does anyone have any suggestions, please, how I could resolve the problem?

 

Thank you and kind regards,

JC

  • What tools are you using to download and debug code ?

    I think the Discovery board debugging hardware is supported by the Keil tools which have good debugging capabilities.

    If you can try to run your code in that environment you might be able to find the problem.

    Do you have access to a scope ?

     

    (It's very common that this sort of thing fails because the hardware isn't connected correctly or the IO pins are not configured correctly -  with the debugger and the scope you can resolve those issues quite quickly.)

     

    MK

  • in reply to michaelkellett

    Thank you for your reply. I am using CooCox CoIDE with ST-Link connection. It has debugging capabilities too, but I don't know how they compare to those of Keil.

    I don't have access to a scope presently, but it might happen sometime soon. What signals should I be testing with scope in my case, and what are they expected to be like?

     

    Chances are hardware isn't wired properly, but I did my best to follow the instructions/schematics for examples. The four data and clock connections in the SDIO sample are about 2cm (< 1 inch) in length. And SPI connection is quite hard to mess up with the module I have. Also, the example from the ST forum also contained a hex/bin file, which I downloaded to the MCU, so configuration should be alright.

     

    Best,

    JC

  • in reply to Former Member

    If you are downloading a hex file you don't have a chance of debugging.

     

    Unless the code you are using is too big for the 32k limit on the free version then download the free Keil tools (they can use the ST link)

     

    Use them to compile the source code.

     

    Read the help about the debugger and then check the following:

     

    Using the system viewer - is the peripheral (SDIO controller or SPI ) properly configured .

    Is the GPIO correctly set up for the pins you are using.

    Follow the code and see (if you can) where it goes wrong.

    If you have a DMM you can check that the pins on your SD card socket wiggle when you stimulate them from the debugger (you might need to halt the code and temporarily swap the GPIO configuration to normal GPIO to do this.)

    In order to debug this kind of thing you need to understand  how all the different parts work and have a tool that lets you look at  them.

     

    If you want to know what signals to expect on the SD card then you need to:

    1) Read the card spec (the free version will be adequate)

    2) Read the peripheral spec in the St reference manual

    3) Do some Googling and read a load more stuff to get some ideas.

    4) Check what your code is trying to do - is it using SPI or 4 bit SD card mode  - possible write some simple test functions to wiggle the pins or poke the peripheral directly.

     

    MK