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.
I am running the ethernet example code as part of the Enet Lwip TCP Client Example.
I am able to see the UART terminal output successfully displaying the messages like link up / down when the network cable is connected but permanently stuck printing
Waiting for network UP ...
Waiting for network UP ...
Waiting for network UP ...
I tried changing other example codes under "networking/lwip" and all examples exhibit the same issue.
The home router has DHCP server running and can successfully assign IP address using DHCP to some other embedded device to test the router integrity.
Hi Prasanna,
This is not the expected behavior. I confirmed that networking examples and DHCP is working fine on AM263x on my end.
Can you please answer the following questions:
1. What version of the SDK you are on?
2. What version of Syscfg and CCS are you on?
3. How long do you let the example run and let it "wait for network up"? Sometimes if the DHCP server is slow in assigning an IP address, it takes some time to get an IP address.
4. What boot mode are you using to run the application
5. Is the example you are running out-of-box or some modifications in code or syscfg were made.
Based on your replies to the above, we'll be able to root cause it better.
Regards,
Shaunak
1. MCU+ SDK for AM263x Latest (currently 09.01.00.41)
2. Code Composer Studio Version: 12.5.0.00007 ,
3. Its several tens of minutes when the 'wait for network up' kept scrolling thro
4. Default QSPI Flash / External Host as well as tried changing to external host UART both same result.
5. The example is out of the box , no changes and utilizing the sysconfig that was part of example as well. "enet_cpsw_tcpclient_am263x-cc_r5fss0-0_freertos_ti-arm-clang"
The behavior is same even if I used other example codes, say client server.
There are couple additional data points below
a. The Enet CPSW Loopback Example test passes when configured for internal loopback
b. I am able to see the UART terminal output successfully displaying the messages like link up / down when the network cable is connected/disconnected as mentioned previously
Hi Prasanna,
For the CPSW Loopback test, both the MAC and the PHY loopback pass? The expected output should be as shown here:
AM263x MCU+ SDK: Enet CPSW Loopback Example (ti.com)
AM263x MCU+ SDK: Enet CPSW Loopback Example (ti.com)
Regards,
Shaunak
correct , recall similar for MAC internal , external didn't try . Can get logs and post here
The issue at our end was the router running DHCP had privilege's limited and once enabled all good to . Thanks again for the timely responses !!