Honored Contributor
Honored ContributorMore information... and more help request
I think it is definitely a tse device issue. Infact this is what I discovered: I directly inspected the tse statistic counters (tse base address + 0x60 to 0xe0) after sending 14 packets which were looped back by my external test device. aFramesTransmittedOK = 14 aFramesReceivedOK = 9 aFrameCheckSequenceErrors = 0 aAlignmentErrors = 0 ifInErrors = 5 ifOutErrors = 0 etherStatsJabbers = 0 etherStatsFragments = 5 This data matches with my application result: only 9 packets received out of 14. The etherStatsFragments counter tells me the 5 lost packets were too short frames with crc error. How can this happen? I'm not an ethernet guru and I don't know the mac and phy internal processes. Could it be that the part of rx frame data which overlaps with a tx frame will eventually get lost? As if the device was working in a half duplex mode (which is not the case) How can I overcome the problem? Is there any special configuration in the tse I'm missing? Thank you for any help
