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.

AM6224A1-800, CRC errors counters in Ethernet driver

Hello,

we are trying to read CRC errors counters from Ethernet driver (registers).

In our project we are using TI Sitara AM6224A1-800 uC.

We are reaching through interfaces to the "Eth_getRxStatsRFC2819" which calls "CpswStats_getStats" in the MCALs. That should read the CRC counters from the device registers. And it does, but the counters are always equal to 0, no matter what frames are received.

  • Hello,

    And it does, but the counters are always equal to 0, no matter what frames are received.

    The register value is expected to be 0 if there are no CRC errors detected. Can you please elaborate on what do you mean by no matter what frames are received? Are you trying to force a CRC error and still seeing 0 in CPSW stat registers?

    Regards,

    Nihar Potturu. 

  • Hello,

    Yes, exactly. We have a simulation environment for the communication over Eth and we are forcing frames with CRC errors. Even when such a frame with incorrect CRC is received, there is no increase in CPSW stats registers' counters.

  • Hello,
    any progress about the topic? Are we missing something with these counters?

  • Hello,

    Apologies for the delay in getting back.

    Below is some information on how the Ethernet MCAL driver updates the CRC counters:

    "CRC errors are identified and stats counters increased at the corresponding MAC port. Stats has to be enabled on the relevant port in CPSW_STAT_PORT_EN_REG, it’s a bit mask, one bit per port. If other stats counters are increasing, then this is not the issue. The CPSW stats counters are decrement-on-write, an internal structure in the driver saves and accumulates the stats received from CPSW register."

    Could you please share more details on the simulation environment used for injecting CRC errors in your communication?

    Regards,
    Krithika