Can anyone tell why Babbling error bit is set ? How can I avoid it ?
Is there any way ?
The babbling receive flag is set when the Ethernet controller receives an Ethernet frame (broadcast, multicast or unicast, depening on how your receiver is performing filtering) which is longer than the expected maximum length, as programmed in ETH_RCR.
If you are seeing this set it may be normal if there are long frames on the Ethernet connected to that are matching the filtee setting (eg. usually broadcasts are received always). Otherwise check that ETH_RCR is not set to an unexpectedly small value, meaning than it can be triggered by a lot of normal network activity.
If you still are not sure, try disabling [es experiment] promiscuous/broadcast reception so that your Ethernet controller will only receive unicast frames (which will normally not be present) and then it should never be set, since it will be rejecting all frames. If it is still set there must be a more major HW/Ethernet configuration error.
Kinetis: µTasker Kinetis support
K60: µTasker Kinetis TWR-K60N512 support / µTasker Kinetis TWR-K60D100M support / µTasker Kinetis TWR-K60F120M support
For the complete "out-of-the-box" Kinetis experience and faster time to market
I am asking with respect to ethernet peripheral of MK60.
Can anyone give me answer ?
Its very important to me.
If you require some additional information from me I will share here.
Thanks in advance.
Yes It was Major Configuration error from my side.
It has solved now.
Thanks for help.
Retrieving data ...