• State Answer Suggested
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 1231 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

RM57L843: LAUNCHXL No TX_EN signal to PHY, RM48 and RM57 EMAC Differences?

stomp
Genius 4675 points
Part Number: RM57L843
Other Parts Discussed in Thread: DP83640, DP83630, HALCOGEN

Hi,

I'm trying to get our software stack we've used on RM48 operating on RM57.  Specifically the RM48 EMAC to DP83640 stack.

On the LAUNCHXL2-RM57 I have link established, 25 MHz ECLK from the RM57, I have MII_TX_CLK and MII_RX_CLK's at 25 Mhz also. I have PinMux configured and MII enabled, MDIO works well and the DP83630 negotiates a link, etc.

Using the same test cases for the RM48 EMAC I do not see a TX_EN signal from the RM57's EMAC.  Likewise, despite traffic visible between PHY and RM57 EMAC I get no receive interrupts.

Both the RM48 EMAC and RM57 EMAC seem to have the same silicon ID and revision level, so I would assume they are functionally the same. 

Does anyone know of any subtle differences between RM57 EMAC and RM48 EMAC that would prevent any sort of transmit or receive operation?.  The only thing I can think of is the VCLK4 region, but if this was incorrect I assume I would not even be able to access the EMAC registers.

Thanks

Stomp!.

  • 0
    TI__Guru 59540 points
    Hello Stomp,

    I have forwarded you post to one of our EMAC experts so they can help work through the issue you are seeing.
  • 0 in reply to Chuck Davenport
    TI__Guru**** 196916 points

    Hello Stomp,

    Please download the lwip demo v03 which supports TMS570LC43x and RM57x devices:

    The instructions to modify the HALCoGen drivers for RM57x launchpad:

    The EMAC module on RM48 and RM57 are the same.

    Regards,

    QJ

  • 0 in reply to QJ Wang
    Genius 4675 points
    Hi QJ,

    Thanks for the help.

    I managed to catch a unique case where wireshark captured a RARP my RM57L was sending as all 0x00. It led me to look closely at the MPU settings, and while I do not really know what the differences are in terms of EMAC memory, once I changed my mpu assembly code to that of the LaunchXL2_RM57L Lwip Demo the EMAC started working fine.

    A default MPU configuration for the RM57 LaunchXL from HalCoGen and the LWIP differ some what, especially with the "Enable MPU background Region setting and some other regions especially region 13 configured for 0xFC000000 (which 0xFC520000 is the descriptor list)

    So I'll mark this as solved, and maybe HalCoGen team could add an option in the future if you are using the EMAC to also enable the MPU settings?

    Thanks again
    Stomp!