hi
this is saida
i am working on Sabre Smart Device board (i.mx6 dual )
i am doing Ethernet testing, for that i have taken code from SDK and building from licensed armds-5 environment.
the loopback at MAC level is working in RGMII mode.
but its not working at phy level which is setting loop back option in phy zero register.
i am checking receiving of packet by following way
1. i am running code in board side and waiting for a packet and it is running in promicous mode
2. from linux ubuntu pc side i am entering command in hyper terminal is
arping -I eth0 -c 10 10.0.0.2
but i am not receiving any packet
what could be the problem ?
please any one can help in this regard it is urgent
other wise if any one have standalone bare metal code for ethernet testing,
one can send it to me
thanks and reagrds
Saida Safavath
Hi igorpadykov
Yes as i expected you only respond immediately, thanks for your reply.
but the test procedure what i am doing is correct or not
if it is not correct can you give me some guideline how to test step by step the extracted ethernet driver from u-boot
i thought that if i sent arping command from linux pc, the driver should receive the message so that i can confirm at least receive is working
i am also trying to send arp packet and capturing in wireshark ? (to confirm sending part)
please if possible give your valuable suggestions
thanks and regards
Saida
Hi Saida
uboot fec driver can be found on
fec_mxc.c\net\drivers - uboot-imx - i.MX U-Boot
also may be useful to look at enet drivers in SDK for i.MX Cortex-M on
Best regards
igor
Hi igorpadykov
i will try it and come back to you
thanks
saida
hi
igorpadykov
i am working with fec driver in u-boot
i am unable to ping in u-boot
my ip(custom board) is 10.0.0.8 and host side is 10.0.0.6
i am capturing packets with tcpdump
its looks like u-boot is able to send packets but not receiving the packets
tcpdump results are: for ping 10.0.0.6
"request who has 10.0.0.6 tell to 10.0.0.8" 48 bytes
"reply 10.0.0.6 is at 00:1c:11:1:3:4 with some mac address" 28 bytes
from this i confirmed that packet is sending properly but not receiving
i think there is problem on hardware side ?
how can i solve this receiving part in hardware
is there any signal to verifr this in hardware
thanks and regards
Saida
Hi Saida
yes for uboot this may be correct behaviour, please check :
[U-Boot] Q on expected u-boot behavior on ping response
Best regards
igor
hi igorpadykov
may be i am not conveyed message properly
i am doing ping in u-boot only
this is working on sabresd board which i purchased
but the custom board which i have designed is not working for ping command
for that i have checked with tcpdump, packed is transmitted but not receiving the packet
i have verified signals RX_DV and RX_CLK with scope these are coming like sine waves
still i am not understanding why packet is not received
thanks and regards
Saida
as described on suggested link:
"u-boot only starts the network driver when it
needs to use it (i.e. to send a ping or download something over tftp).
After it has finished the network driver is stopped. Any traffic on
the network will be ignored if u-boot isn't actively trying to perform a network operation, even if it is addressed to the device."
it is working on i.mx6 sabre board why not my custom board
regards and thanks
saida
Hi Saida
yes unfortunately baremetal sdk has issues with ethernet driver (known issue),
may be recommended to use uboot codes:
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------