• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 325 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:

AM6526: Impact of i2022 errata on AM65xx

AM6526: Few more questions about i2022 errata of AM65xx

Hideaki Matsumoto
Genius 9130 points
Part Number: AM6526

Hi,

 

Let me confirm the related questions to the following thread,

e2e.ti.com/.../765272 user:10509

Typically there are different controls for addr/ctr and data, because layout topologies are different.

You’ve recommended a 34.3ohm driver setting in the EMIF tool and following the DDR4 Layout Design Guidelines and the High Speed Interface Layout Guidelines for avoiding the errata i2022 of AM65xx.

 

However, user should follow these guidelines regardless of whether this errata exists or not. Therefore, only 34.3ohm driver setting is workaround for this errata, right ?

In the AM65x/DRA80xM DDR Board Design and Layout Guidelines SPRACI2,

Is there any notice or caution in “CK and ADDR_CTRL Topologies and Routing Guidance” and “Data Group Topologies and Routing Guidance” by this errata ?

There is no change in these guidance for this errata ?

 

Do you have a plan to fix this errata in future ? If this errata was fixed, the layout should be modified ?

Thanks and regards,

Hideaki 

  • 0
    TI__Guru* 86820 points

    Hi Hideaki, there is no change in the routing guidelines because of errata i2022.  Customers should continue to follow the guidelines as written.  The workaround is the best common driver impedance setting for both data and addr/ctrl.  We realize this is not as optimal as having the ability to set different impedances for data and addr/ctrl, but we have determined the workaround to be adequate for proper functionality.

    Errata i2022 is planned to be fixed in the next revision of the device

    Regards,

    James