lwIP fails to initialise after EMAC boot

jcm

Other Parts Discussed in Thread: AM3354

I have a StarterWare application that uses lwIP to download a file using http.

This works find if I boot the AM3354 from UART or NAND, but if I boot over the network (EMAC boot), it hangs during the CPSW initialisation in lwIP doing:

/* Enable the interrupts for channel 0 and for control core 0 */
 CPSWCPDMATxIntEnable(cpswinst->cpdma_base, 0);

(third_party/lwip-1.4.0/ports/cpsw/netif/cpswif.c)

The CPSW and interrupt sub-sysctems seem to be reset as part of the initialisation, so I'm a bit puzzled as to why there's any difference between UART/NAND and EMAC boot.

Anyone got any ideas?

Thanks,

Jonathan

over 12 years ago

0 Biser Gatchev-XID over 12 years ago

TI__Guru**** 393215 points

Hi Jonathan,

From what you explain, the difference is that during EMAC boot the processor ROM code has already initialized the CPSW, and then lwip is trying to do the same. My suggestion is that you look for "forever" loops in the initialization section of the lwip code. Also, there is a separate forum for Starterware: http://e2e.ti.com/support/embedded/starterware/default.aspx.

0 jcm over 12 years ago in reply to Biser Gatchev-XID

Prodigy 210 points

It turns out the StarterWare doesn't reset the CPSW_CPDMA sub-system, so adding:

CPSWCPDMAReset(cpswinst->cpdma_base);

in cpswif_inst_init fixes the problem.

However, if the ROM Bootloader is failing to restore the CPSW to it's reset state before starting the bootloader, surely that's a bug in the RBL rather than StarterWare.

Jonathan

Processors

Processors forum

lwIP fails to initialise after EMAC boot