• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 32 subscribers
  • Views 405 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.

AM2431: How to apply Errata i2329 workaround in old SDK (08.03.00.18)

Koichiro Tashiro
Mastermind 22945 points

Part Number: AM2431
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I have a question from my customer. Please answer below.

==============
I would like to confirm about Errata i2329 (MDIO interface corruption).
I believe this Errata has been fixed in the latest SDK version. However, due to product development reasons, we are using old versions of SDK(08.03.00.18) and SysConfig(ver.1.12.1)
and cannot upgrade to newer versions.

The product is embedded with reference to Enet Lwip CPSW Example.
As shown in the workaround,
CPSW_MDIO_CONTROL_REG:ENABLE=0,
MDIO_POLL_REG:MANUALMODE=1
, and MDIO_MANUAL_IF_REG:MDIO_MDCLK_O/MDIO_OE/MDIO_PIN
are used to manually control MDIO.
Although the read/write of PHY register is succeeded, link up/down is not detected even if Ether is connected as shown in the log of the following sample program.


Is there anything I need to set or change other than the MANUALMODE setting and manual control for the Enet Lwip CPSW Example?
I would appreciate if you could advise me where I should refer to in the latest SDK.
==============

Thanks and regards,
Koichiro Tashiro

  • 0
    TI__Mastermind 36173 points

    Hey Koichiro,

    Koichiro Tashiro said:
    However, due to product development reasons, we are using old versions of SDK(08.03.00.18) and SysConfig(ver.1.12.1)
    and cannot upgrade to newer versions.

    It is highly recommended by TI to use the latest version of SDK. There are many bugs that have been resolved since the 8.03 release and we cannot provide further support for older out-of-date SDK versions as this is implemented in the form of new SDK releases. Is there any specific reason why you are unable to upgrade to the newest version?

    Best Regards,

    Zackry Fleenor