• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 31 subscribers
  • Views 975 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.

Error registers incrementing

Wes Byers
Prodigy 410 points
Other Parts Discussed in Thread: HALCOGEN, LAUNCHXL2-570LC43, DP83630

We are having an issue with the Hercules TMS570LS12x Launchpad Development Kit.

The main issue is that when we are connected at 100M, we get occasional dropped packets on the receive side. There are no such dropped packets when connected at 10M. By observing EMAC registers, I can see that RXCRCERRORS and RXALIGNCODEERRORS both increment at a slow but steady rate, which causes packets to be dropped. Also when, observing PHY registers, I see similar error counters being incremented (False carrier sense counter, reg 0x14, and Receive error counter, reg 0x15).

 

we tried swapping cables, swapping Ethernet ports, and swapping development boards, but none of these seem to make a difference. It's starting to look like a hardware issue.

 

we also tried:

 

* Restart auto-negotation after boot

* Disable auto-negotiation and force to 100M full duplex

 

But those also did not make a difference.

 

The only things connect to our development board are the USB for JTAG/serial/power, and the Ethernet cable. We are using lwip 1.4.1 for our network stack. HALCoGen was used to generate the HAL. I've got a Code Composer project I could send you that exhibits the issue if it will help. 

 

For now, we're just limiting to 10M, but this is not a good long-term solution for us. Please let me know what information you need.

  • 0
    TI__Guru 72500 points
    I am forwarding your question to an EMAC module expert.
  • 0 in reply to Bob Crosby
    TI__Prodigy 410 points

    Hi Bob,

    I still have not heard back on this, can you please put me in touch with the expert?

  • 0 in reply to Wes Byers
    TI__Guru 68920 points
    Wes,

    Not sure I understand. The Launchpad for TMS570LS12x doesn't have an ethernet jack. Is it something that you added?
  • 0 in reply to Anthony F. Seely
    TI__Prodigy 410 points
    Yes we added the ethernet jack, we will be using ethernet as our primary means of communication for this project.
  • 0 in reply to Wes Byers
    TI__Guru 68920 points
    Ok so you need to really scrub the:
    a) pcb layout of the ethernet phy and jack that you added.
    b) check the signal integrity on the MII or RMII lines

    Couple more questions:
    - what does the connection look like? (is it flying wires or is it a board to board stack)?
    - are you using MII or RMII mode?

    I think in any case the launchpad isn't necessarily the best platform to add a phy and jack because the MII and RMII are fairly high speed, and the booster pack (worst) and proto

    -Anthony
  • 0 in reply to Anthony F. Seely
    TI__Prodigy 410 points
    The connection is the RJ45 port on the dev kit, standard CAT6 cable, to RJ45 port on my develoment PC. On the board, MII mode is used.

    a) We are using an off-the-shelf TI Hercules Launchpad development kit (LAUNCHXL2-570LC43). The ethernet phy, pcb layout, etc, is unchanged - we didn't add anything.
    b) Have not looked closely at signal integrity, but we have tried swapping cables, swapping boards, etc with no improvement.
  • 0 in reply to Wes Byers
    TI__Guru 68920 points
    Wes,

    Ok so I am just confused on which launchpad.

    First post says "We are having an issue with the Hercules TMS570LS12x Launchpad Development Kit."
  • 0 in reply to Anthony F. Seely
    TI__Guru 68920 points

    So looking back at your first post again, if the phy is flagging errors too, then I would start investigating there.

    If you are using the LC4357 launchpad not the LS1224 launchpad, then the
    phy is a TI phy and we did review the layout w. the DP83630 team. But I can't say we really stressed the design so I'm not terribly surprised if you see some low error rate.

    The best thing to do might be to post to the Ethernet forum and ask what types of issues might cause:
    (False carrier sense counter, reg 0x14, and
    Receive error counter, reg 0x15).
    With the DP83630 phy.

    Just to make sure though - this device has a spread spectrum PLL for better EMC performance. If you turned that on then I could see it causing a problem for Ethernet because we clock the phy from the MCU. And if you did that there is a 2nd PLL that can be used to create the clock for just the phy and this doesn't have the spread spectrum mode..

    It's not a normal thing for people to turn on the PLL spread spectrum right away but it is exposed in HalCoGen which is why I'd ask.


    BTW in your post on the Ethernet forum please  type @Anthony... until it pops up:   ''

    This will keep me in the loop on the discussion and I'm the right person from the LaunchPad standpoint.

  • 0 in reply to Anthony F. Seely
    TI__Prodigy 410 points
    Thanks very much Anthony, we will check in with the PHY group to see what they have to say.