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.

AM3505: eMMC goes into INACTIVE state

Part Number: AM3505

Hi All

Are there any known cases of the eMMC chip to go into INACTIVE state

We are using AM3505 and eMMC from different vendors, in some units it looks like the eMMC has changed state into INACTIVE mode after have being initialized correctly.

A power cycle is required to get the system back to normal again, a reset of the eMMC does not bring the eMMC back to normal state only a power cycle.

What could cause the eMMC chip to go into INACTIVE state? 

Thanks

Rodney

  • Rodney

    I am checking, but so far no one has encountered this issue.

    There could be many possible factors, anything from voltage issues to eMMC compatibility.  

    Do you only see the issue on one make/model of eMMC? Have you traced the interface traffic to see if there is any command that could be the cause?

    --Paul  

  • Thanks Paul

    The issue is extremely rare, seen in some logs but so far not reproduced in the lab.

    Engineer has looked into many possible factors, Voltage to the eMMC is one of them. So far nothing there.

    The issue occurs with eMMCs from different vendors and models.

    Under what condition would the AM3505 issue a CMD15 (GO_INACTIVE)?

    Thanks

    Rodney

  • Rodney

    I don't see any indication that the CMD15 is automatically set by hardware. I have asked our s/w support to comment.  I assume you are using Linux?