- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
I have built the starterware software example "enet_echo" for the LCDK6748 development kit. The app runs correctly on the LCDK6748 hardware.
The LCDK6748 hardware uses a MII implementation for the EMAC interface.
errUDP = udp_bind(pcb, &addrLocal, UDP_PORT_LOCAL); returns with OK
errUDP = udp_connect(pcb, &addrRemote, UDP_PORT_REMOTE); returns with OK
errUDP = udp_send(udpMY, &Buffer); returns OK and the UDP message correctly arrives at the destination.
A ping message from the destination address succeeds.
I have built a C6748 board that uses a RMII implementation for the EMAC interface.
In RMII mode:
errUDP = udp_bind(pcb, &addrLocal, UDP_PORT_LOCAL); returns with OK
errUDP = udp_connect(pcb, &addrRemote, UDP_PORT_REMOTE); returns with OK
errUDP = udp_send(udpMY, &Buffer); returns OK but the UDP message does NOT arrive at the destination.
I have checked all the clocks and they appear to be correct.
Wirehark does not pickup any incoming packets on the destination side.
The LED lights on the LAN switch and/or LAN router blink, indicating a received packet.
A ping message from the destination address fails.
TCP is enabled and returns OK.
I have stepped through the udp_send() all the way to the end and the message is built in the driver without any error returns.
There are numerous debug messages in the EMAC driver. How can I easily turn these on I can't find the documentation on how to do this.
John
