No Ethernet Connection despite Logs

Installing and Using OpenWrt Network and Wireless Configuration
1

I am currently using a imx6ul like board (its a vendor's board that it similar to the imx6ul 14-14 evk). I have built the device tree according to the vendor's schematics and it has booted and given the following logs during start up.

However, there is still no ethernet connection between the device and my laptop. Is there anything I am missing?

Logs in question

[   21.179946] device eth0 entered promiscuous mode
[   21.393132] Generic PHY 20b4000.ethernet-1:02: attached PHY driver (mii_bus:phy_addr=20b4000.ethernet-1:02, irq=POLL)
[   27.370969] fec 20b4000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[   27.378958] br-lan: port 1(eth0) entered blocking state
[   27.384316] br-lan: port 1(eth0) entered forwarding state
[   27.451854] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready

& /etc/config/network

root@OpenWrt:/# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

I'm fairly new to the whole kernel and firmware side of things so I am not sure if my devicetree is fully correct.
Some troubleshooting I have done:
Laptop's ethernet is set to 192.168.1.10.
eth0 is up, br-lan is up

2

what is the output of:

ubus call system board

Also...

Please don't post screenshots... instead, use the "Preformatted text </>" button for logs, scripts, configs and general console output (copy/paste).
grafik
Please edit your post accordingly. Thank you! :slight_smile:

3

Thanks, sorry I'm not quite familiar with how these works, I have editted my post.

This is the output of ubus call system board

root@OpenWrt:/# ubus call system board
{
        "kernel": "5.15.167",
        "hostname": "OpenWrt",
        "system": "ARMv7 Processor rev 5 (v7l)",
        "model": "Freescale i.MX6 UltraLite 14x14 EVK Board",
        "board_name": "fsl,imx6ul-14x14-evk",
        "rootfs_type": "ext4",
        "release": {
                "distribution": "OpenWrt",
                "version": "23.05.5",
                "revision": "r24106-10cc5fcd00",
                "target": "imx/cortexa7",
                "description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
        }
}
4

Where did the firmware come from? I don't see this device supported by the official OpenWrt project.

5

I'm working on this for my company which is using a Chinese device, that I believe is based off the imx6ul-14-14-evk board. Its sold with openwrt built upon it but its using Chaos Calmer instead

6

Ah... so it is indeed not from the official project.

Because of the fact that there are obviously many major customizations made by the vendor to support their device (relative to the official OpenWrt firmware), you need to ask the vendor for help. We have no idea what they have done to the firmware -- only they would know.

7

That makes sense, I have asked the vendor before however they aren't very helpful so I am not quite sure if they can help in this aspect as well. However from the logs, is it safe to assume that at least the hardware is working as intended?

8

We have no way to know if the hardware is working properly and thus it is a firmware issue or vice versa (or both).

This forum is for the official OpenWrt project and doesn't support forks because of the fact that they are effectively black-boxes to us.

9

Alright, thanks for taking your time!

10

You're welcome. Good luck!

11

This topic was automatically closed after 30 hours. New replies are no longer allowed.