This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MMC_write (CSL) timeout on 5509

Hi There,

I am attempting to make my application somewhat bulletproof and I wanted to handle a situation where someone pulls the memory card without closing the card. 

I tried setting some values in MMC_InitObj for memory clocks before response timeout and memory clocks before data timeout and MMC_write simply will not return. Does this work or am I missing something? 

Here are my settings. 

MMC_InitObj Init={ 0,0,0,1,7,5,100,20000,512};

Thanks in advance! 

Cam

  • Hi,

    Team is working on and will provide an update on the same shortly.

    Thanks & regards,

    Sivaraj K

  • Hi,

       The values passed to init function are correct and looks fine.

       As per the spec SPRU593 section - 3.5.

       Set the Time-Out Period for a Response -

    •    Set 0 -  Do not check for a response time-out condition.
    •    n = 1−255 If there is no response from the memory card in n CLK cycles, record a time-out condition

     Set the Time-Out Period for a Data Operation

    • Set 0  - Do not check for a data-read time-out condition
    • n = 1−65535 If no data is received from the memory card in n CLK cycles, record a time-out condition.

    The values you are passing are 100 and 20000 for Response timeout and Data timeout. These are well within the specification.

    Regards

     Vasanth

  • Hmm I wonder why it never returns. Do you always get a timeout return in your test?

  • Hi,

      On your Question - Do you always get a timeout return in your test?

      I haven't created an example code to run on 5509 platform. Basically I confirmed the value that you passed to the function was correct. 

    Regards

     Vasanth

     

  • Thanks Vasanth.

    Would you be able to just verify that the timeout does work with a simple program? Since all my settings are correct, it would be nice to have verification that the library function actually works as documented. I've found a number of inconsistencies between the documentation and reality.