• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 353 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: i818 - SATA PHY Reset Required Following SATA PLL Unlock

AM5728: SATA errata criticality

Daisuke Maeda
Guru 20205 points
Part Number: AM5728

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.

What is the priority order that should be fixed in errata (i783, i807, i808, i809)?

What is the rate of incidence for each errata (i783, i807, i808, i809)?

Best regards,

Daisuke

  • 0
    TI__Mastermind 27890 points

    Maeda-san,

    For priority, I think that needs to be determined by the customer based on their particular use case. As for rate of incidence, we do not have this data.

  • 0 in reply to -DK-
    Guru 20205 points

    Hi -DK- -san

    Thank you for your reply.

    In what use cases does the issue by each errata occur?

    I understand as follows:

     For i783, the issue only occurs on system using the PARTIAL or SLUMBER low-power state with the aggressive power management.
     
     For i807, if DMA mode is used the issue only occurs when negotiating at system startup or waking up from low power mode.
     
     For i808, the issue can occur with the interface fatal error status in all use cases.
     
     For i809, the issue can occur with the FIS length exceeds 64 bytes in all use cases but does NOT occur with the FIS length of 64 bytes or less.

    Is my understanding correct?

    Best regards,

    Daisuke