MX RT1064 TCPIP Auto Negotiation timeouts

[dmckeever]

This is an extract from the lwip fsl_phy.c for the rt1064:

if (((bssReg & PHY_BSTATUS_AUTONEGCOMP_MASK) != 0) && (ctlReg & PHY_LINK_READY_MASK))
                        {
                            /* Wait a moment for Phy status stable. */
                            for (timeDelay = 0; timeDelay < PHY_TIMEOUT_COUNT; timeDelay ++)
                            {
                                __ASM("nop");
                            }
                            break;
                        }

The "wait a moment" time delay loop for Phys status stable seems rather long, given that PHY_TIMEOUT_COUNT is set to 0x3FFFFFFU

Any suggestions for a more reasonable loop limit?

[kerryzhou]

Hi Damien McKeever,

   Do you mean the fsl_phy.c under this link:

SDK_2.6.1_EVK-MIMXRT1064\components\phyksz8081 ?

  I think this piece code need to also associated with the above code:

You can see that code is used as delay, wait a moment for the next round checking.

About the PHY_TIMEOUT_COUNT, I don't know where you find it is 0x3FFFFFFU, in my sdk2.6.1, it is

So, if the clock is very quick, the delay time is not very long.

If you are not using the newest SDK, you can check the newest SDK which can be downloaded from this link:

Welcome | MCUXpresso SDK Builder 

If you still have questions about  it, please kindly let me know.

Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[dmckeever]

 Hi Kerry

Thank you for your helpful reply.

I had been using version 2.4.1 of the SDK; in that version, PHY_TIMEOUT_COUNT is defined as 0x3FFFFFFU

I have now downloaded the latest SDK version 2.6.1 .

Unforunately, the Change Log is no longer included in the documentation file :
   MCUXpresso SDK Release Notes Supporting EVK-MIMXRT1064.pdf

   (  MCUXSDKMIMXRT1064CYPRESSWIFIRN  User's Guide Rev 0, 06/2019 )

The Change log  was contained in the corresponding file in version 2.4.1

Since the Change Log would be most useful, could you point me to where I can find it?

Thanks

Damien

[kerryzhou]

Hi Damien,

   So, after you download the newest SD2.6.1, do you check the PHY_TIMEOUT_COUNT data?

   I also didn't find the change log document, could you tell me which folder in the SDK you find document :MCUXSDKMIMXRT1064CYPRESSWIFIRN user's guide?

Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[dmckeever]

Hi Kerry

Thanks for your reply.

Yes, the value of PHY_TIMEOUT_COUNT in 2.6.1 is indeed 100000

The SDK release notes etc are contained in a separate docs zip

archive that can be downloaded: SDK_2.6.1_EVK_MIMX1064_doc.zip

The pdf files are in the docs folder of this zip archive.

Just FYI, adding the 2.6.1 SDK "broke" my MCUXPRESSO IDE: it could no

longer program the flash.

It appears there is an incompatibility, so I had to upgrade to the

latest version 11 of MCUXPRESSO

( And this version 11 had issues with the debug controls being

messed up; but these are now "miraculously" fixed after a restart! )

So I am now back to my original task of implementing POP3 under lwip.

Thanks for your help.

Damien

[kerryzhou]

Hi Damien McKeever,

  Thanks a lot for your updated information.

  When the tool meet the abnormal problems, it is really a headache, but your operation is correct, restart it or install the newest IDE version.

   So, now do you still have question about this topic?

   If you still have questions about it, please kindly let us know, thank you!

Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------