[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Network problem when using arm machine mcimx6ul-evk/cortex-a7
From: |
Benjamin |
Subject: |
Network problem when using arm machine mcimx6ul-evk/cortex-a7 |
Date: |
Wed, 15 Jan 2020 14:19:30 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
Hello list,
I have sucessfully built Linux kernel 4.14 armv7 and bootet Qemu using
machine type mcimx6ul-evk + my base system.
[snip]
qemu-system-arm \
-M mcimx6ul-evk \
-cpu cortex-a7 \
-m 512M \
-kernel ./boot/4.14.146-armv7-x29.zImage \
-dtb ./boot/imx6ul-14x14-evk.dtb \
-serial mon:stdio \
-display none \
-append "console=ttymxc0 loglevel=8 bootmem-debug root=/dev/mmcblk1p1 rw
boot_mode=normal" \
-drive file=./disk/mmcblk1.raw,format=raw,id=disk1\
-device sd-card,drive=disk1
[snap]
After boot, I am presented with 2 network interfaces eth0 and eth1.
In Qemu console I can, if I don't specify anything special, see the SLIRP
networking.
[snip]
(qemu) info network
hub 0
\ hub0port1: user.0: index=0,type=user,net=10.0.2.0,restrict=off
\ hub0port0: imx.enet.0:
index=0,type=nic,model=imx.enet,macaddr=52:54:00:12:34:56
imx.enet.1: index=0,type=nic,model=imx.enet,macaddr=52:54:00:12:34:57
[snap]
Other networking options work too bridge/tap, but the result is the same.
Unfortunately both interfaces have NO-CARRIER, link stays down, even though I
have up'ed the interface.
[snip]
root@imx6ul:~# ip link set up dev eth0
root@imx6ul:~# ip link set up dev eth1
root@imx6ul:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state
DOWN group default qlen 1000
link/ether 52:54:00:12:34:57 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state
DOWN group default qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
[snap]
A full dmesg can be seen here http://paste.debian.net/1126093/.
Has anyone managed to boot a mcimx6ul-evk arm machine with functional network?
Am I missing some PHY, dmesg
is reporting a Generic PHY (is that an issue?). I tried quite a lot, but
finally ran out of ideas..
Thank a lot in advance.
Kind regards,
Benjamin
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Network problem when using arm machine mcimx6ul-evk/cortex-a7,
Benjamin <=