Odroid C2 : no eth0 with latest image

[Elclaudio]

12 hours ago, Igor said:

Aaaaah. I forgot something important  Sorry. We don't rebuild u-boot in nightly builds by default since it takes a lot of time and changes here are extremely rare ... that's why packaged versions are the same.

 

Enabled now for next builds. 

Edit: but also doesn't work. Keep looking ...

Edit: fixed by attaching to this tag https://github.com/u-boot/u-boot/releases/tag/v2021.04-rc3 @Elclaudio Will update images and repository later today.

 

Thanks Igor, I will try the next nightly soon and report back

[guidol]

@Igor @Elclaudio

My C2 did already work/reboot with 

U-Boot 2021.01-armbian (Mar 03 2021 - 14:32:21 +0300) odroid-c2

 

But today I compiled the new u-boot

U-Boot 2021.04-rc3-armbian (Mar 08 2021 - 18:12:26 +0300) odroid-c2

which does also work/reboot fine on my C2

System diagnosis information has been uploaded to http://ix.io/2SaS

 

[EDIT]

does also work with newer dev-kernel

FROM Linux 5.10.19-meson64 TO Linux 5.11.4-meson64

System diagnosis information has been uploaded to http://ix.io/2SaU

 

 

# dd if=/dev/mmcblk0 of=/tmp/installed_uboot.bin skip=97 count=1376
1376+0 Datensätze ein
1376+0 Datensätze aus
704512 bytes (705 kB, 688 KiB) copied, 0,0525366 s, 13,4 MB/s

# strings /tmp/installed_uboot.bin | grep "U-Boot 20"
U-Boot 2021.01-armbian (Mar 03 2021 - 14:32:21 +0300) odroid-c2

# dpkg -i ./linux-u-boot-dev-odroidc2_21.05.0-trunk_arm64.deb


cd /usr/lib/linux-u-boot-dev-odroidc2_21.05.0-trunk_arm64
dd if=./bl1.bin.hardkernel of=/dev/mmcblk0 bs=1 count=442 conv=fsync > /dev/null 2>&1;
dd if=./bl1.bin.hardkernel of=/dev/mmcblk0 bs=512 skip=1 seek=1 conv=fsync > /dev/null 2>&1;
dd if=./u-boot.bin of=/dev/mmcblk0 bs=512 seek=97 conv=fsync > /dev/null 2>&1 

[reboot]

# dd if=/dev/mmcblk0 of=/tmp/installed_uboot.bin skip=97 count=1376
1376+0 Datensätze ein
1376+0 Datensätze aus
704512 bytes (705 kB, 688 KiB) copied, 0,04659 s, 15,1 MB/s

# strings /tmp/installed_uboot.bin | grep "U-Boot 20"
U-Boot 2021.04-rc3-armbian (Mar 08 2021 - 18:12:26 +0300) odroid-c2

 

linux-u-boot-dev-odroidc2_21.05.0-trunk_arm64.deb

[Elclaudio]

something is really strange here.

I kept my "working armbian 21.0.2" test image on an sdcard with U-Boot 2021.01 on it.

Last time, I checked, it worked great, eth0 active on each boot, no apparent issue. Because I've haven't configured all things on it (I have FHEM, mosquitto, a webserver, cellular dongle, wifi ap etc) I'm still running the old armbian with kernel 4.19.69-meson64 as a daily driver, which is rock solid.

Now, in order to test the latest U-boot version, I've put the 21.0.2 test image card back in and guess what : eth0 doesn't work anymore. I've changed anything to this image since last time I checked. So I put the latest U-boot 2021.04-rc3 in it : same thing, still no eth0.

 

I then put back my old sd with kernel 4.19.69-meson64 : all works as it should.

 

The main difference I see is that the old image is using "legacy boot" so to speak as it's refered in boot.cmd vs modern boot in latest armbian. Also, the old armbian doesn't output anything on connected hdmi screen before kernel is booted while latest armbian show U-boot messages. But this different boot method doesn't explain why it worked before and not anymore.

 

@guidol : it's possible, while, I'm not sure of it, that it work for you because you're on a 100Mbps link ? I've heard some reports that eth0 used to work on 100M but not on 1G in the past. Or it could be the environnement, connected usb device at boot, power supply. I don't recall also if your using an emmc or an sdcard ?

[guidol]

1 hour ago, Elclaudio said:

@guidol : it's possible, while, I'm not sure of it, that it work for you because you're on a 100Mbps link ?

I've heard some reports that eth0 used to work on 100M but not on 1G in the past.

Or it could be the environnement, connected usb device at boot, power supply.

I don't recall also if your using an emmc or an sdcard ?

@Elclaudio I have only power (Single-USB-Power 5V/1A from an old "Palm"-Power-Supply (PSU 157-10108-00))

and ethernet (100MBit) connected.

 

For you  I switched a short time my C2 to the 1GBit-Switch rebooted/tested - works also:
 

[87945.551990] meson8b-dwmac c9410000.ethernet eth0: Link is Down
[87967.818374] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
[88095.093734] meson8b-dwmac c9410000.ethernet eth0: Link is Down
[88097.665953] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
root@odroid-c2-3(192.168.6.3):~# reboot

[    2.190284] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found
[    2.190304] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found
[    2.190399] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[    2.193291] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37
[    2.193319] meson8b-dwmac c9410000.ethernet:         DWMAC1000
[    2.193326] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported
[    2.193331] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported
[    2.193336] meson8b-dwmac c9410000.ethernet: COE Type 2
[    2.193340] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported
[    2.193345] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported
[    2.193683] meson8b-dwmac c9410000.ethernet: Normal descriptors
[    2.193695] meson8b-dwmac c9410000.ethernet: Ring mode enabled
[    2.193700] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    6.964191] meson8b-dwmac c9410000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=46)
[    6.968309] meson8b-dwmac c9410000.ethernet eth0: No Safety Features support found
[    6.968332] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW
[    6.968697] meson8b-dwmac c9410000.ethernet eth0: configuring for phy/rgmii link mode
[   10.263501] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx

 

On some GBit devices I use sometimes the ethtool to set speed to 100MBit but the C2 does it right on a 100MBit-Port:

.# /etc/rc.local
# for a 100MBit device - comment out for 1GBit
# ethtool -s eth0 speed 100 autoneg off

 

Here is the reboot with 1GBit on eth0 of my C2 (5-Port DLINK GBIt Switch):
System diagnosis information has been uploaded to http://ix.io/2Sh8

[Elclaudio]

1 hour ago, guidol said:

@Elclaudio I have only power (Single-USB-Power 5V/1A from an old "Palm"-Power-Supply (PSU 157-10108-00))

and ethernet (100MBit) connected.

 

For you  I switched a short time my C2 to the 1GBit-Switch rebooted/tested - works also:
 

[87945.551990] meson8b-dwmac c9410000.ethernet eth0: Link is Down
[87967.818374] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
[88095.093734] meson8b-dwmac c9410000.ethernet eth0: Link is Down
[88097.665953] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
root@odroid-c2-3(192.168.6.3):~# reboot

[    2.190284] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found
[    2.190304] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found
[    2.190399] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[    2.193291] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37
[    2.193319] meson8b-dwmac c9410000.ethernet:         DWMAC1000
[    2.193326] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported
[    2.193331] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported
[    2.193336] meson8b-dwmac c9410000.ethernet: COE Type 2
[    2.193340] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported
[    2.193345] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported
[    2.193683] meson8b-dwmac c9410000.ethernet: Normal descriptors
[    2.193695] meson8b-dwmac c9410000.ethernet: Ring mode enabled
[    2.193700] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    6.964191] meson8b-dwmac c9410000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=46)
[    6.968309] meson8b-dwmac c9410000.ethernet eth0: No Safety Features support found
[    6.968332] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW
[    6.968697] meson8b-dwmac c9410000.ethernet eth0: configuring for phy/rgmii link mode
[   10.263501] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx

 

On some GBit devices I use sometimes the ethtool to set speed to 100MBit but the C2 does it right on a 100MBit-Port:

.# /etc/rc.local
# for a 100MBit device - comment out for 1GBit
# ethtool -s eth0 speed 100 autoneg off

 

Here is the reboot with 1GBit on eth0 of my C2 (5-Port DLINK GBIt Switch):
System diagnosis information has been uploaded to http://ix.io/2Sh8

 

thanks for your tests. I also tried different power supply (usb vs jack) and forced 100M with an old switch, booting without any usb device attached, it doesn't change anything

[rizo]

Also having similar issues and using an external Apple 100Mbps ethernet USB dongle I have laying around from work:

 

root@odroidc2:~# dmesg |grep -i eth0
[   38.250881] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[   38.251632] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   38.326577] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[   38.327349] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   38.353188] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[   38.353954] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   38.379975] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[   38.384302] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   38.405938] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[   38.406693] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
root@odroidc2:~# ip a
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: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:1e:06:33:ab:5d brd ff:ff:ff:ff:ff:ff
3: enx086d41e4bdc7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:6d:41:e4:bd:c7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.124/25 brd 192.168.0.127 scope global dynamic noprefixroute enx086d41e4bdc7
       valid_lft 312sec preferred_lft 312sec
    inet6 fe80::5797:150:76db:3068/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
root@odroidc2:~# uname  -a
Linux odroidc2 5.10.21-meson64 #21.02.3 SMP PREEMPT Mon Mar 8 07:22:00 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

 

[lanefu]

Providing logs with 

armbianmonitor -u

 helps with troubleshooting and significantly raises chances that issue gets addressed.

[Elclaudio]

Despite efforts in trying to resolve the issue myself and since none of the latest armbian work ootb, I've ordered a raspberry pi 4 and planning to move my entire home automation on it asap. That's a real problem for all theses board, if you manage to get your hands on one, software support is generaly poor (I don't talk about armbian but the manufacturer, in this case, hardkernel). At least with a pi, we still have updates even for old boards. As a side note, I've heard a pi 4 if powerfull enough to act as a 1GB router, so I will also try the latest openwrt snapshot on it and may be move my x86 router on a pi 4 if all goes well.

[rizo]

root@odroidc2:~# armbianmonitor -u
System diagnosis information will now be uploaded to http://ix.io/2U0G
Please post the URL in the forum where you've been asked for.

 

http://ix.io/2U0G

Quote

Despite efforts in trying to resolve the issue myself and since none of the latest armbian work ootb, I've ordered a raspberry pi 4 and planning to move my entire home automation on it asap. That's a real problem for all theses board, if you manage to get your hands on one, software support is generaly poor (I don't talk about armbian but the manufacturer, in this case, hardkernel). At least with a pi, we still have updates even for old boards.

Agree, have two raspi 4 4GB and support is much better but have had the C2 for years. Wanted to add it to my microk8s cluster and is now with the network dongle but may just sell it and replace it with another raspi 4 for longer term support.

[Elclaudio]

On 3/26/2021 at 5:58 PM, rizo said:

root@odroidc2:~# armbianmonitor -u
System diagnosis information will now be uploaded to http://ix.io/2U0G
Please post the URL in the forum where you've been asked for.

 

http://ix.io/2U0G

Agree, have two raspi 4 4GB and support is much better but have had the C2 for years. Wanted to add it to my microk8s cluster and is now with the network dongle but may just sell it and replace it with another raspi 4 for longer term support.

 

Hey rizo, thats right. the c2 is pretty stable with older kernel. He's been running 24/24 for a few years without much glitch here. Power consumption is pretty low also. It lacks usb3 which make it unsuitable for a home router and with latter kernel I had also issues with usb. That's why I starting to phasing it out. My RPI4 has arrived and I spend most of the week end building, configuring and testing it under Openwrt and I must say I'm impressed, it managed to drive GB fiber without problem. Now I'm starting to think it may be a good idea to just buy another one for home automation purposes, especialy since I've just recently find out that you can activate 5 uart in total, that's a blessing for what I've in mind.

[zimme]

I just wanted to write an update on this issue as I've ran into it also, but I figured out a way to make it work.

My board was in a "broken" state where the network card wasn't working with any of the latest versions of Armbian using a newer u-boot like 21.04-rc3.
I compiled my own versions to test the latest edge and using u-boot 21.04-rc4, etc. but nothing worked.

I got it working by accident and I wasn't sure how but then I flashed the sdcard again with a different version and got into the broken state again.

This lead me down an evening of frantically testing a bunch of things and that's when I discovered a way to get out of this broken state with a newer
version of u-boot (21.04-rc or later).

Grab the latest stable image which uses u-boot 21.04-rc3, flash it to an sdcard and boot the board and wait 5 min or something to make sure the board has actually booted (I'm running headless so no monitor connected).
Once you're sure the board has booted, unplug the network cable and reconnect it. Then wait for a couple of minutes and then power cycle the board and that made the network card work again for me every time I
got into this broken state.

Hope it helps someone else and if not I guess that something else made my network card work again.

[Muadiv]

On 4/2/2021 at 9:47 PM, zimme said:

I just wanted to write an update on this issue as I've ran into it also, but I figured out a way to make it work.

My board was in a "broken" state where the network card wasn't working with any of the latest versions of Armbian using a newer u-boot like 21.04-rc3.
I compiled my own versions to test the latest edge and using u-boot 21.04-rc4, etc. but nothing worked.

I got it working by accident and I wasn't sure how but then I flashed the sdcard again with a different version and got into the broken state again.

This lead me down an evening of frantically testing a bunch of things and that's when I discovered a way to get out of this broken state with a newer
version of u-boot (21.04-rc or later).

Grab the latest stable image which uses u-boot 21.04-rc3, flash it to an sdcard and boot the board and wait 5 min or something to make sure the board has actually booted (I'm running headless so no monitor connected).
Once you're sure the board has booted, unplug the network cable and reconnect it. Then wait for a couple of minutes and then power cycle the board and that made the network card work again for me every time I
got into this broken state.

Hope it helps someone else and if not I guess that something else made my network card work again.

 

Hey Zimme, I had something similar. I have the NanoPi K2, and I had exactly this problem with the eth0. 

But, also playing around, I installed the Armbian_21.05.0-trunk.70_Nanopik2-s905_hirsute_edge_5.11.11.img , was not working as expected, and I decide to give it a try to Debian Armbian_21.02.3_Nanopik2-s905_buster_current_5.10.21.img , and suddendly, the eth0 was there, working almost perfect. I did some updates, and bla bla, and because I fucked up with users and other things, I decide to flash it again and start from scratch, now that the eth0 is working... and again... not working again. 

 

Now I'm trying what you said, also entering on armbian-config and updating the boot (not sure if this should be done there or not, I'm kind of newbie in Linux). But, still without good results. @zimme Could you please tell me which image you used to get it working again ? 

 

Thanks in advance. 

 

Also, if anyone can tell me how to push another u-boot that works on (with commands for dumb people like me), will be great !! I can do any test, but I need full instructions .. no idea how to change the u-boot, etc.

 

Muadiv.

[blacki2]

By now I tried the latest stable (Armbian_21.02.3_Odroidc2_buster_current_5.10.21.img) plus several nightly builds on my ODROID-C2, none of them has working eth0 ootb for me.

 

So I'll stick with the latest image including old but working "U-Boot 2020.04-armbian": (Armbian_20.11.3_Odroidc2_buster_current_5.9.14.img). 

 

You can install all updates (apt-get update && apt-get upgrade is no problem) as long you DON'T upgrade u-boot on the eMMC/SD-card through armbian-config
 

[lioka]

Had same problem, can confirm that rollback to u-boot 2020.04 helps.

Also, picking c183c406c4321 from linux into u-boot where applicable works for me too,

at least on 2021.04.

 

[zimme]

Based on the commit message in c183c406c4321 it seems this would fix the problem.

Using kernel 5.12-rc8 or later for odroidc2 would be the best solution going forward it seems from my perspective.

Nice find @lioka

[SK_D]

Hello,

 

how can it get internal ethernet back to work?

I've downloaded linux-u-boot-dev-odroidc2_21.05.0-trunk_arm64.deb and installed. But it is still not working.

 

root@Odroid-C2:~# strings /tmp/installed_uboot.bin | grep "U-Boot 20"
U-Boot 2021.04-armbian (May 06 2021 - 18:07:14 +0000) odroid-c2
root@Odroid-C2:~#

 

Edited June 6, 2021 by SK_D
Shell-Output

[SK_D]

I've switched to nightly and uboot can't find kernel image, but network seams to work. So I try to find my emmc2SD adapter and check fs.

[guidol]

Today my C2 is running fine (booted from MicroSD) and with working ethernet using the "bleeding edge" version of armbian buster

 

cd /usr/lib/linux-u-boot-edge-odroidc2_21.05.1_arm64
dd if=./bl1.bin.hardkernel of=/dev/mmcblk0 bs=1 count=442 conv=fsync > /dev/null 2>&1;
dd if=./bl1.bin.hardkernel of=/dev/mmcblk0 bs=512 skip=1 seek=1 conv=fsync > /dev/null 2>&1;
dd if=./u-boot.bin of=/dev/mmcblk0 bs=512 seek=97 conv=fsync > /dev/null 2>&1

dd if=/dev/mmcblk0 of=/tmp/installed_uboot.bin skip=97 count=1376

strings /tmp/installed_uboot.bin | grep "U-Boot 20"
U-Boot 2021.04-armbian (May 06 2021 - 18:07:48 +0000) odroid-c2

  ___      _           _     _    ____ ____
 / _ \  __| |_ __ ___ (_) __| |  / ___|___ \
| | | |/ _` | '__/ _ \| |/ _` | | |     __) |
| |_| | (_| | | | (_) | | (_| | | |___ / __/
 \___/ \__,_|_|  \___/|_|\__,_|  \____|_____|

Welcome to Armbian 21.05.2 Buster with bleeding edge Linux 5.12.6-meson64

package bsp-kernel[21.05.2] u-boot[21.05.1] dtb   [21.05.2]
firmware          [21.05.2] config[21.05.3] branch[edge]


dmesg |grep -i ether
[    1.757833] igb: Intel(R) Gigabit Ethernet Network Driver
[    2.235419] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found
[    2.235437] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found
[    2.235529] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[    2.244419] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37
[    2.244444] meson8b-dwmac c9410000.ethernet:         DWMAC1000
[    2.244451] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported
[    2.244456] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported
[    2.244461] meson8b-dwmac c9410000.ethernet: COE Type 2
[    2.244466] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported
[    2.244471] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported
[    2.244556] meson8b-dwmac c9410000.ethernet: Normal descriptors
[    2.244562] meson8b-dwmac c9410000.ethernet: Ring mode enabled
[    2.244567] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    5.120227] meson8b-dwmac c9410000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=46)
[    5.134367] meson8b-dwmac c9410000.ethernet eth0: No Safety Features support found
[    5.134391] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW
[    5.134734] meson8b-dwmac c9410000.ethernet eth0: configuring for phy/rgmii link mode
[    6.791266] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx

 

[uncleremus]

I just came here via web search. I'm not using armbian but openSUSE. Like others here, I found that u-boot 2020-10 and later (tried up to 2021-04) do not detect my ethernet hardware (more precisely, the PHY). u-boot 2020-01 and 2020-04 work for me (like 2020-01). I'm using a 5.3 kernel. So far I suspect commit dd5f2351. Has anyone tried to revert this yet?

[uncleremus]

This issue is fixed in upstream u-boot by commit a246e21 ("arm64: dts: meson: odroidc2: readd PHY reset properties"), which is included in u-boot  v2021.07-rc1. The regression was caused by the backport of a kernel commit that had change a reset timing too aggressively, and first went into u-boot v2020.07. See upstream discussion, openSUSE bug 1187095.

[newsera]

```
root@odroidc2:~# strings /dev/mmcblk1 | grep 'U-Boot 20'
U-Boot 2020.04-armbian (Dec 12 2020 - 00:07:49 +0100) odroid-c2

 

root@odroidc2:~# cat /etc/*-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=odroidc2
BOARD_NAME="Odroid C2"
BOARDFAMILY=meson-gxbb
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=b9814056
DISTRIBUTION_CODENAME=focal
DISTRIBUTION_STATUS=supported
VERSION=20.11.3
LINUXFAMILY=meson64

```

How can I upgrade the U-Boot to U-Boot 2021.04-rc3-armbian (Mar 08 2021 - 18:48:25 +0100) odroid-c2?
I tried sudo apt get & sudo apt upgrade -y but it didn't update the U-boot.

[guidol]

27 minutes ago, nwesera said:

How can I upgrade the U-Boot to U-Boot 2021.04-rc3-armbian (Mar 08 2021 - 18:48:25 +0100) odroid-c2?
I tried sudo apt get & sudo apt upgrade -y but it didn't update the U-boot.

 

 

Find yout U-Boot path ins /usr/lib/ and do something like this?

Find your actual U-Boot-Binary (serach for a path like this):
cd /usr/lib/linux-u-boot-edge-odroidc2_21.05.1_arm64

Flash the new U-Boot:
dd if=./bl1.bin.hardkernel of=/dev/mmcblk0 bs=1 count=442 conv=fsync > /dev/null 2>&1;
dd if=./bl1.bin.hardkernel of=/dev/mmcblk0 bs=512 skip=1 seek=1 conv=fsync > /dev/null 2>&1;
dd if=./u-boot.bin of=/dev/mmcblk0 bs=512 seek=97 conv=fsync > /dev/null 2>&1

Create a binary File which contains the signature:
dd if=/dev/mmcblk0 of=/tmp/installed_uboot.bin skip=97 count=1376

Read out the signature:
strings /tmp/installed_uboot.bin | grep "U-Boot 20"
U-Boot 2021.04-armbian (May 06 2021 - 18:07:48 +0000) odroid-c2

 

[Igor]

If u-boot package is installed on the system -> nand-sata-install -> update bootloader + reboot.

[BarTender]

Just had the same problem as well, was running Buster without an issue on my C2 and needed to move to Focal for a few annoying reasons using the non desktop download https://redirect.armbian.com/region/AS/odroidc2/Focal_current and can see I also have the same issue with uboot failing to find the network adapter. I can pull the version out of the running Bionic image and then dd it onto the eMMC.

I eventually got my host working by taking the uboot from Bionic:

wget https://armbian.systemonachip.net/archive/odroidc2/archive/Armbian_20.02.8_Odroidc2_bionic_current_5.4.28_desktop.7z
7z e Armbian_20.02.8_Odroidc2_bionic_current_5.4.28_desktop.7z
dd if=Armbian_20.02.8_Odroidc2_bionic_current_5.4.28_desktop.img of=bionicuboot.bin bs=512 seek=1 skip=1 count=4096

then put onto the emmc:

dd if=bionicuboot.bin of=/dev/sdb bs=512 seek=1 skip=1

 

Further edit.. I am going to search for my serial console tonight when I get home to help debug the root cause. I am also running the same C2 board revision as @guidol as per this post: 

 

[SK_D]

Hello

Eth0 is mostly (after some power cutoff it works) not working here:

 

Zitat

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
TE: 181220
no sdio debug board detected

BL2 Built : 11:44:26, Nov 25 2015.
gxb gfb13a3b-c2 - jcao@wonton

Board ID = 6
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from eMMC, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK.
Run bl30...
Load bl301 from eMMC, src: 0x0001c200, des: 0x01000000, size: 0x000018c0
Wait bl30...Done
Sending bl301.......OK.
Run bl301...
eMMC, src: 0x00020200, des: 0x10100000, size: 0x00011130

--- UART initialized after reboot ---
[Reset cause: unknown]
[Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04]
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: Load bl33 from eMMC, src: 0x00034200, des: 0x01000000, size: 0x000a09c0
ef be ad de d f0 ad ba ef be ad de not ES chip
[0.296375 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):4d2e34d
NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9

U-Boot 2021.04-armbian (Jul 24 2021 - 14:52:47 +0000) odroid-c2

Model: Hardkernel ODROID-C2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (0:1)
DRAM:  2 GiB
MMC:   mmc@72000: 0, mmc@74000: 1
In:    serial
Out:   serial
Err:   serial
Net:   Could not get PHY for ethernet@c9410000: addr -1
No ethernet found.

Hit any key to stop autoboot:  0
=>

 

A new SD-Card with Armbian_21.05.4_Odroidc2_buster_current_5.10.43.img is also not working.

 

Best regrads,

Stefan

Edited July 31, 2021 by SK_D
Next try with new SD.

[gechu]

On 6/14/2021 at 9:43 AM, uncleremus said:

This issue is fixed in upstream u-boot by commit a246e21 ("arm64: dts: meson: odroidc2: readd PHY reset properties"), which is included in u-boot  v2021.07-rc1. The regression was caused by the backport of a kernel commit that had change a reset timing too aggressively, and first went into u-boot v2020.07. See upstream discussion, openSUSE bug 1187095.

 

Installed Armbian_21.05.4_Odroidc2_hirsute_edge_5.12.10.img.xz, and flashed uboot using armbian config tool, and manually using instructions in this thread, none worked.

 

I take from what you write @uncleremus that the fix for some Armbian users will be when Armbian includes u-boot  v2021.07-rc1 (or later).

[klippe]

23 hours ago, gechu said:

 

Installed Armbian_21.05.4_Odroidc2_hirsute_edge_5.12.10.img.xz, and flashed uboot using armbian config tool, and manually using instructions in this thread, none worked.

 

I take from what you write @uncleremus that the fix for some Armbian users will be when Armbian includes u-boot  v2021.07-rc1 (or later).

I've recently reinstalled Armbian - my previous version faced the eth issue discussed here but after some reboots and network restarts it usually started to work. But then at some point network died completely and I wasn't able to connect to a network at all. So I've installed latest "Armbian 21.05.6 Buster with Linux 5.10.43-meson64". I can see (cd /usr/lib/linux-u-boot[tab]) that it runs "linux-u-boot-odroidhc4-current_21.08.1_arm64" and you know what... the issue is still there. I've just restarted my odroid-hc4 and have no network. Since the u-boot 21.08.1 is newer than aforementioned 2021.07-rc1 it looks that the issue is still not resolved :(. 

[blacki2]

Am 1.8.2021 um 23:22 schrieb klippe:

Since the u-boot 21.08.1 is newer than aforementioned 2021.07-rc1 it looks that the issue is still not resolved :(. 

 

21.08.1 does not refer to the u-boot version here.

 

I just tested the image "Armbian_21.08.1_Odroidc2_buster_current_5.10.60.img", which comes with u-boot 2021.04 and does not work:

Zitat

 

U-Boot 2021.04-armbian (Aug 08 2021 - 16:06:00 +0200) odroid-c2

Model: Hardkernel ODROID-C2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (0:1)
DRAM:  2 GiB
MMC:   mmc@72000: 0, mmc@74000: 1
In:    serial
Out:   serial
Err:   serial
Net:   Could not get PHY for ethernet@c9410000: addr -1
No ethernet found.

Hit any key to stop autoboot:  0

 

 

On the other hand the current nightly build "Armbian_21.11.0-trunk.23_Odroidc2_hirsute_edge_5.14.9.img", which comes with u-boot 2021.07 works just fine for me:

Zitat

 

U-Boot 2021.07-armbian (Sep 29 2021 - 20:36:41 +0000) odroid-c2

Model: Hardkernel ODROID-C2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (0:1)
DRAM:  2 GiB
MMC:   mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@c9410000

Hit any key to stop autoboot:  0

 

 

 

[sebek]

For info, still an issue with "Armbian_21.08.1_Odroidc2_focal_current_5.10.60"

 

Resolved by:

apt-get install linux-u-boot-odroidc2-current=21.02.3 # downgrade uboot

nand-sata-install # flash new uboot

apt-mark hold linux-u-boot-odroidc2-current # keep current uboot, until confirmed resolved

[Igor]

19 hours ago, sebek said:

For info, still an issue with "Armbian_21.08.1_Odroidc2_focal_current_5.10.60"

 

Resolved by:

apt-get install linux-u-boot-odroidc2-current=21.02.3 # downgrade uboot

nand-sata-install # flash new uboot

apt-mark hold linux-u-boot-odroidc2-current # keep current uboot, until confirmed resolved

 

Such troubles could be preventable with: