libbsd.txt "test runner" realview_pbx_a9_qemu

Chris Johns chrisj at rtems.org
Wed Jun 10 03:53:11 UTC 2015


On 10/06/2015 1:39 pm, Gene Smith wrote:
> On 06/08/2015 10:57 PM, Chris Johns wrote:
> 
>>
>> I am not sure. Running qemu with '-M realview-pbx-a9 -net model=help'
>> does not show the SMCS LAN9118 device.
>>
>> I do not know what is happening here. There could be patches missing to
>> enabled SMC support for the realview machine in qemu.
>>
>> I am playing with the Zynq at the moment. It at least runs but I am
>> having issues getting my network to talk to it.
>>
> 
> With realview_c.patch from Sebastian now applied [1] I am getting better
> results. The ping is attempted but it fails. (I also added "-net nic" to
> the qemu command line or else I get the similar result as w/o the patch.)

Great.

> 
> ---------------
> [gene at hplt ping01]$ sudo LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
> /home/gene/rtems/install/4.11/qemu/bin/qemu-system-arm -M
> realview-pbx-a9 -m 256M -no-reboot -monitor none -serial stdio
> -nographic -net nic -net vde,sock=/tmp/myswitch -kernel ping01.exe
> audio: Could not init `oss' audio driver
> *** LIBBSD PING 1 TEST ***
> nexus0: <RTEMS Nexus device>
> smc0: <SMSC LAN91C110FD or LAN91C111FD> on nexus0  [2]
> devctl: !system=IFNET subsystem=smc0 type=ATTACH
> smc0: Ethernet address: 3537304
> devctl: +smc0 at   on nexus0
> devctl: +nexus0 at   on root0
> devctl: !system=IFNET subsystem=lo0 type=ATTACH
> add host 192.168.1.1: gateway smc0
> add net default: gateway 192.168.1.1
> PING 192.168.1.1 (192.168.1.1): 56 data bytes
> 
> --- 192.168.1.1 ping statistics ---
> 3 packets transmitted, 0 packets received, 100.0% packet loss
> assertion "exit_code == EXIT_SUCCESS" failed: file
> "testsuite/ping01/test_main.c", line 57, function: test_ping

I am seeing this with the Zynq without the cadence_gem patch. I am
seeing IP header check sum errors. I suggest you check the stats for the
receiving end of your ping. My trace is:

# tcpdump -i bridge0 -vvvv ip host 10.10.5.15




tcpdump: listening on bridge0, link-type EN10MB (Ethernet), capture size
65535 bytes
12:42:23.262116 IP (tos 0x0, ttl 64, id 58748, offset 0, flags [none],
proto ICMP (1), length 84, bad cksum 0 (->7708)!)
    10.10.5.15 > 10.10.5.2: ICMP echo request, id 256, seq 0, length 64

> ------------------
> 
> [1] Also applied the cadence_gem_c.patch but probably n/a for realview bsp.

Yeap.

> [2] Waits after printing this line for 30-60 seconds before moving on.

I do not see this. That period is weird. I wonder is this is something
in the PHY when attempting to create a link. Also could it be in the
host side related to opening the tap interface and maybe a DNS type issue.

Chris


More information about the users mailing list