TMS320F28388D: TMS320F28388D

Hi,

By boot up time of IP stack takes 30 seconds - do you mean booting up of CPU2 and lwip initialization code ?  Or only the lwip initialization ("lwIPInit) and  UDP init ("my_udp_init"_ functions takes 30 seconds till it receives the first ping.

Best Regards

Siddharth

We are using only CPU1 & CM, the boot time is from power on till we have LINK & ping from outside is working

Hi, 

Pls provide details on the initializations done during booting up of CPU1 and CM cores.  Also, do you have more details on the time taken for each of these - Booting up of CPU1, taking CM out of rest, booting up of CM, LWIP Stack initialization?  Depending on it,  I can redirect it to the appropriate expert for guidance.  

Best Regards

Siddharth

We are using the TI example code in third party folder with rx udp, so who is taking this example and run it can see the problem with udp boot time

Hi, 

30 seconds seems to be too much, can you provide details on the steps that you are doing from power up till the UDP initialization.  It would help if you are able to narrow down on the piece of code which is taking more time.  

Also, you can take a look at the LWIP configurations (lwipopts.h) that you are using and see if those can be optimized .

Best Regards

Siddharth

What am I doing is just flash the CPU1 & CM example LWIP UDP code for receiving packet. After power on the evaluation board I send ping command from PC and measuring the time that ping is response from the evaluation board and it takes about 30 seconds.

I have been tried to change parameters in lwippots.h but with no seeing that is improve the time.

Please need example code for the evaluation board that are working and response for ping less than 1 seconds.

Any news?

Hi

We have seen that in certain setups when autonegotiation is enabled as part of link establishment , it could take few secs for the link to be established.

if you have not tried these before, can you please check if any of the following is helpful

1. Disable auto-negotiation and used fixed link speed and duplexity instead. This can be configured either on the evaluation board side or its peer (if connected to a PC or similar). 

 2. as a fallback if you cannot disable auto-negotiation, ensure link is 10/100, as gigabit auto-negotiation typically takes longer

3. Use static IP rather than DHCP for initial IP address configuration if boot time is paramount

If you have indicative split (by instrumenting the code with timestamps) for critical points in startup sequence, that will be very much helpful to narrow down further

Regards

Sriram

Hi, we also try all this with disable auto negotiation and work with fixed 100Mbbs but still the time that ping is response is 30 seconds

Any example code that are working well?