• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 365 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

AM5728: SATA errata criticality

AM5728: SATA errata incidence rate

Daisuke Maeda
Guru 20205 points
Part Number: AM5728

Daisuke Maeda said:

Our customer has not solved the issue discussed in the previous thread. The issue that SATA controller not detects an attached drive occurs on boards of about 250, but the rate of incidence on each board is very low. Our customer is concerned that some of the errata (i783, i807, i808, i809) for SATA may be left in the SATA driver, but wants to apply minimal modifications to the software because the board is in mass production.

The issue does not occur on many in 10K units.

Can the incidence rate of each errata (i783, i807, i808, i809) vary by device or lot?

Our customer will not modify the software until they understand that the issue may be due to errata.

Best regards,

Daisuke

  • 0
    Guru 20205 points

    Hi,

    Daisuke Maeda said:

    Can the incidence rate of each errata (i783, i807, i808, i809) vary by device or lot?

    Is there not any information for the incidence rate of each errata?

    Best regards,

    Daisuke

  • 0
    TI__Expert 4005 points

    Daisuke, 

    If the issue is being seen before disk spin-up during initial HDD detection, then this eliminates several of the link level erratas.  I need some more information to be able to make that distinction.   Few follow up questions:

    1) Is there a temperature dependency? 

    2) Is the HDD a GEN3, GEN2, or GEN1?

    3)  How does the customer know the device is not detected?  Is data not being moved or does console print out an error message during initial detection?

    4) Is there a mode dependency: power-up or  wakeup from sleep?

    5) What version of the SDK is the customer using - are they using TI provided drivers? 

  • 0 in reply to Y. Yang
    Guru 20205 points

    Hi Y. Yang-san,

    Thank you for your reply.

    Y. Yang said:

    If the issue is being seen before disk spin-up during initial HDD detection, then this eliminates several of the link level erratas.  I need some more information to be able to make that distinction.

    SATA is connected to NAND flash controller.

    Y. Yang said:

    1) Is there a temperature dependency?

    The issue occurs when the AM5728 is cooled, not when heated.

    Y. Yang said:

    3)  How does the customer know the device is not detected?  Is data not being moved or does console print out an error message during initial detection?

    When an issue occurs, SATA_PxSSTS[3:0].DET indicates 0 or 1, which often indicates 1.

    Y. Yang said:

    4) Is there a mode dependency: power-up or  wakeup from sleep?

    The issue occurs after initialization after power-up. A sleep is not used.

    Y. Yang said:

    5) What version of the SDK is the customer using - are they using TI provided drivers?

    The SDK drivers provided by TI are not used. OS is WEC7.

    Best regards,

    Daisuke