TMS570LC4357: LwIP example not working on HDK

HI Suthan,

Did you check V5 and G3 for MCLK and MDIO? Those two pins are used for MibSPI by default.

Yes, both are changed to MDIO and MDCLK

Suthan Sivamayam said:

After sometimes hdkif_hw_init fails in

I was getting the same failures in hdkif_hw_init(), after powered on the TMS570LC4357 HDK (or Launchpad).

In the hdkif_hw_init() adding a __delay_cycles() call by changing from:

  EMACInit(hdkif->emac_ctrl_base, hdkif->emac_base);

  MDIOInit(hdkif->mdio_base, MDIO_FREQ_INPUT, MDIO_FREQ_OUTPUT);
  while(delay--);

To:

  EMACInit(hdkif->emac_ctrl_base, hdkif->emac_base);

  /* Wait at least 167 milliseconds with the MDIO signal to the DP83630 PHY pulled-up with hardware before initialising
   * the MDIO interfaces.
   *
   * The DP83630 PHY datasheet parameters T2.1.1 "Post Power Up Stabilization time prior to MDC preamble for register
   * accesses" T2.1.2 "Hardware Configuration Latch-in Time from power up" parameters are both 167 milliseconds.
   *
   * Without this delay, on both a TMS570LC43x HDK and LAUNCHXL2-570LC43 after a powerup the Dp83640IDGet() function
   * failed to read the Phy ID.
   */
  __delay_cycles (PLL1_FREQ * 167000);

  MDIOInit(hdkif->mdio_base, MDIO_FREQ_INPUT, MDIO_FREQ_OUTPUT);
  while(delay--);

Made the code reliable

Chester,

Thank you, unfortunately solution is not working. Also tried with longer time delays.

Suthan Sivamayam said:

Thank you, unfortunately solution is not working.

OK, in my case when was using the LwIP application rather than Ethernet bootloader, the failures to get the Phy ID (before the delay was added) were only seen to occur after a power up. After a reset then worked.

Is there any pattern to when your Ethernet bootloader fails to read the Phy ID, or does the failure appear "random"?

This issue is very similar to mine: https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/571146/rm48l952-lwip-example-not-working-on-hercules-dev-kit-rev-e?tisearch=e2e-sitesearch

Always it fails

Hi Suthan,

Please refer to this app note for configuration:

https://www.ti.com/lit/an/spna239/spna239.pdf

Hi QJ,

I just followed all steps, but still getting the same error (see below)

1. Under the ‘Driver Enable’ tab, enable EMAC Driver and SCI1 Driver.

2. Under ‘VIM RAM’ add the names of the ISRs for EMAC Transmit and Receive Interrupts (Channels 77 and 79, respectively).

3. Enable these interrupts under the ‘VIM Channel 64-95’ tab.

4. Under the ‘PLL’ tab, change the multiplier for both PLLs to a value of 150, such that the output frequency in both cases is 300.00 MHz.

5. Under the ‘GCM’ tab, change the value of the VCLK1, VCLK2 and VCLK3 Dividers to 1 and VCLKA4 Divider to 2, such that the output of VCLKA4_DIV is 37.50 MHz.

6. Under the ‘PINMUX’ tab, enable RMII/MII, under Pin Muxing. Under Input Muxing, enable MDIO(G3), MII_COL(F3), MII_CRS(B4), MII_RX_DV(B11), MII_RX_ER(N19), MII_RXCLK(K19), MII_RXD[0], MII_RXD[1], MII_RXD[2], MII_RXD[3], MII_TX_CLK.

7. Under the ‘EMAC’ tab, change the EMAC address to the correct address (the default one in the example is mentioned above). The physical address is 1 by default. 8. Generate the system initialization and HAL Code.

Also I tried example described in SPNA239 and got the same error. 

It would be great if you can be able to provide a working example - Tested with TMS570LC HDK.