MCF52233 Ethernet Network Problem - PHY RX and TX stopped

keithtan — Thu, 13 Nov 2014 09:44:00 GMT

Hi guys,

I am using MCF52233 with uTasker 1.3. This system Ethernet PHY layer will be down after running for a long time.

I have checked on the MIB Counters IEEE_T_FRAME_OK and IEEE_R_FRAME_OK are not incrementing anymore. The system cannot be ping yet the other peripherals are working fine.

I wish to know is there anyway to dissolves this problem or can lead me to the causes of this problem

Regards,

Keith.

Re: MCF52233 Ethernet Network Problem - PHY RX and TX stopped

TomE — Thu, 13 Nov 2014 13:09:17 GMT

Check the CPU Errata.

Search this forum for "MCF52233 FEC" and "FEC Freeze".

This post suggests running your uTasker code under an emulator on a PC:

https://community.freescale.com/message/22104#22104

How long is a "long time"? Can you make it fail faster by performing bulk data transfers, or by flood-pinging it? Flood-ping with different sized packets, up to (and beyond to cause fragmentation) the maximum size.

Do you have a memory or buffer leak? Is it running out of anything? Would you know if it did - will it try to report these errors and can you see them (in a log or on a console)?

Does it depend on certain traffic or packets? Can you run it on an isolated network with the minimum other devices?

Does it recover if you unplug the Ethernet cable and plug it in again (I have no idea if uTasker has code to handle this).

Inspect all of the FEC Registers, and the entire receive and transmit rings after it stops working. Are there any un-handled errors?

See if you can get it working again by partially or fully reinitializing the FEC.

Ask on the uTasker forums.

Tom

ColdFire/68K Microcontrollers and ProcessorsのトピックMCF52233 Ethernet Network Problem - PHY RX and TX stopped

MCF52233 Ethernet Network Problem - PHY RX and TX stopped

Re: MCF52233 Ethernet Network Problem - PHY RX and TX stopped