Zynq Ethernet driver

Davide Viti zinosat at tiscali.it
Wed Dec 2 09:07:43 UTC 2015

Hi Sebastian,

To run the application, I'm using a recent version of upstream uboot, which
assigns a random mac address:

Warning: Gem.e000b000 (eth0) using random MAC address - c6:4c:58:c9:e6:c4

the dhcp01.exe application, seems to correctly inherit such address from
the boot:

info: dhcpcd: version 6.2.1 starting
info: dhcpcd: DUID 00:01:00:01:e9:6d:a1:80:c6:4c:58:c9:e6:c4

and also the wireshark traces show that the mac address is used during the
DHCP negotiation.
I compared the working setup (qemu) with the microzed setup and noticed the

miibus0: <MII bus> on cgem0
devctl: ? at phyno=0 oui=0xac2 model=0x1d rev=0x1 on miibus0

does that '?' mean that the network card is not recognized?

Regarding the crash, here is what appens when I run the application:

zynq-uboot> bootelf
data abort
pc : [<3ff960bc>]       lr : [<f8c90314>]
reloc pc : [<040350bc>]       lr : [<bcd2f314>]
sp : 3f33dd3c  ip : f1b83000     fp : 3f352440
r10: 00000001  r9 : 3f340ef8     r8 : 00000000
r7 : 00000028  r6 : 00000004     r5 : 00000000  r4 : 001b27a8
r3 : d0030f00  r2 : d0030f00     r1 : f1b83000  r0 : f8c90318
Flags: NzCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

resetting ...

I managed to narrow down a little bit the problem:
as I said previously, if I remove the definition of DEFAULT_NETWORK_SHELL
the problem does not happen; I've noticed that this is the relevant part:

  &bsp_interrupt_shell_command, \
  &rtems_shell_BSD_Command, \
  &rtems_shell_HOSTNAME_Command, \
  &rtems_shell_PING_Command, \
  &rtems_shell_ROUTE_Command, \
  &rtems_shell_NETSTAT_Command, \

"bsp_interrupt_shell_command" and "rtems_shell_BSD_Command" do not cause
any issue, but whenever I include any of the other commands I see the
problem happening: which leads me to guess that there's something related
with the inclusion of the commands of the "net" category (happens only on
the target board and not on qemu)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20151202/24b28a5d/attachment-0002.html>

More information about the users mailing list