• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 29 subscribers
  • Views 162 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS570LC4357: TMS570LC4357: EMAC NetStat TX registers are all zeroes

Richa Sahasrabudhe1
Prodigy 100 points
Part Number: TMS570LC4357

Hi 

I am using the EMAC NetStat registers to monitor EMAC network statistics on TMS570LC4357. (Reference:32.5.50 Network Statistics Registers in the TRM)

I noticed that sometimes the TX related counters do not increment even when there is TX traffic being sent from the microcontroller. While this happens - I am able to receive these packets at their destination(a host computer). 

POResetting the TMS570LC4357 resolves this issue. 

Can you please explain why this happens to TX network counter registers?

  • 0
    Prodigy 100 points

    To provide some more info -  the following TX counters are zeroes

    #define EMAC_TXGOODFRAMES       (0x234U)
    #define EMAC_TXBCASTFRAMES      (0x238U)
    #define EMAC_TXMCASTFRAMES      (0x23CU)
    #define EMAC_TXPAUSEFRAMES      (0x240U)
    #define EMAC_TXDEFERRED         (0x244U)
    #define EMAC_TXCOLLISION        (0x248U)
    #define EMAC_TXSINGLECOLL       (0x24CU)
    #define EMAC_TXMULTICOLL        (0x250U)
    #define EMAC_TXEXCESSIVECOLL    (0x254U)
    #define EMAC_TXLATECOLL         (0x258U)
    #define EMAC_TXUNDERRUN         (0x25CU)
    #define EMAC_TXOCTETS           (0x264U)


    while the TXCARRIERSENSE is non-zero

    #define EMAC_TXCARRIERSENSE     (0x260U)

    What do these carrier sense errors indicate? How would this affect the ethernet communication?

  • +1 in reply to Richa Sahasrabudhe1
    Guru 92251 points
    Richa Sahasrabudhe1 said:
    What do these carrier sense errors indicate?

    The TRM says:

    Richa Sahasrabudhe1 said:
    How would this affect the ethernet communication?

    I think it means the TMS570LC4357 EMAC considers the transmission failed because the carrier was not present during any or all of the transmission attempts.

    Suspect this is cause by some sort of duplex-mismatch, in that the TMS570LC4357 EMAC is configured as half-duplex but the Phy or other end of the link is configured as full-duplex.

    Are you using a TI launchpad / EVM or a custom board?