Elclaudio

  • Posts

    32
  • Joined

  • Last visited

Everything posted by Elclaudio

  1. 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.
  2. it's nice and handy to be able to backup our os image and restore it, just in case. The problem is that a full os backup need the root partition to be mounted read only. And some of us are running the device without any monitor attached (headless) or it's not very practical to get acces to the sdcard (for exemple, when the device is installed in the electrical cabinet) So, I had the idea of creating some kind of ramdisk with some utilities (base tools, ssh, rsync...) to backup the "offline" root partition and send it to another computer. Ultimately, this process could be started also by network boot, by U-Boot script. When you decide to backup the root partition, just go to /boot and replace the boot.scr adapted for your need and purposes and reboot. For debugging, it's best to have access to the serial console with and uart to usb or be connected locally with a monitor. as a start, I've tried 2 methods of booting, from sdcard at first, and network (which is a little more tricky but I won't talk much about it for now) boot.cmd (and boot.scr): setenv bootargs init=/bin/bash root=/dev/mmcblk1p1 ro rootwait console=ttyAML0,115200 console=tty1 setenv devtype "mmc" ext4load mmc 0 ${kernel_addr_r} /boot/uImage ext4load mmc 0 ${fdt_addr_r} /boot/dtb/${fdtfile} bootm ${kernel_addr_r} - ${fdt_addr_r} this boot the kernel but I got stuck at some point while booting, I believe that's because of the root partition. I don't want to use the root partition on the sdcard, instead I need some kind of independent ramdisk root partition (with the tools for backup) Do you have an idea of how to achieve this, how to create and boot from a "squashfs" recovery like partition ?
  3. 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.
  4. 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
  5. 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 ?
  6. Thanks Igor, I will try the next nightly soon and report back
  7. Hi Igor I don't undestand, you said that armbian use the latest stable (2021.01) but either in armbian stable or nightly, there is only 2020.10 ? or it is just the term "tend" that explain it perhaps ?
  8. I found a more recent version of U-Boot that work nicely, eth0 is working as expected and the various test I've done show that it appear stable in various situations. this U-Boot come from opensuse and is more recent that the one used in armbian, event in latest trunk, U-Boot 2021.01 (Feb 16 2021 - 19:58:28 +0000) link to the rpm archive : http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/OdroidC2/standard/aarch64/odroidc2-firmware-20170419-5.150.aarch64.rpm for your convenience, I extracted it here (md5sum 4c52ad58f483bb8ce9fd767c6af9f077 ) : u-boot.zip
  9. I'm trying to build U-Boot from official repo on github, I managed to successfully build it for odroid-c2 (U-Boot 2021.04-rc3-00133-ge4dba4ba6f (Mar 06 2021 - 182939 +0100) but the kernel isn't loaded, there is a bootloop. I copied only the file u-boot.bin to the boot sectors like before, but I may have missed something, is there any other file to copy ? also could this be due to the file bl1.bin.hardkernel which is not generated (a blob file ?) Board ID = 8 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 SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 aml log : SIG CHK : 351 for address 0x01700000 reset... GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 114007 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 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 SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 aml log : SIG CHK : 351 for address 0x01700000 reset... GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 113565 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 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 SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 aml log : SIG CHK : 351 for address 0x01700000 reset... GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 113990 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015.
  10. I've not switched to nightly in my current testing image since I've installed and configured some stuff, instead, I've downloaded the whole latest nightly image Armbian_21.05.0-trunk.37_Odroidc2_hirsute_current_5.10.20.img.xz (md5: d69704708d7d4b38991b8a6eea790c17) from 2021-03-05 09:50. Well, this image is broken, not only the ethernet does not work (embedded U-Boot 2020.10-armbian (Jan 12 2021 - 192822 +0100) but the OS itself doen't boot at all, it's stuck on (I think) uboot prompt > tested on 2 different sd card.
  11. Thats when you wished a day duration should be 48h..even then, when you do things for free, it's perfectly understandable. We all have a life
  12. Damn, and this code is supposed to drive rocket into space
  13. I don't see any suspicious change in armbian commit between thoses dates, there is commit 07447294c7a9d11301f1aecf3bac4e53ac6a6f18 in april 2020 which add C4 support, so it means the issue should be on the main U-Boot code right ?
  14. thanks you I can compare the two u-boot main source with this simple link : https://github.com/u-boot/u-boot/compare/v2020.04...v2020.10 But how do I add https://github.com/armbian/build/commits/master/patch/u-boot/u-boot-meson64 to the Mix ??
  15. Like the bootloop issue I had ? > https://forum.armbian.com/topic/17112-odroid-c2-no-eth0-with-latest-image/?do=findComment&comment=120395 Do you know how to compare the changes made to u-boot between Armbian_20.11.3 (U-Boot 2020.04-armbian (Dec 12 2020 - 000749 +0100) and Armbian_20.11.6 (U-Boot 2020.10-armbian (Jan 05 2021 - 014047 +0100), because the issue seems to be caused by a change in source code here
  16. Thanks you blacki2 for testing the latest working U-Boot, I know it's a very time consuming task I've extracted the U-Boot files from Armbian_20.11.3_Odroidc2_buster_current_5.9.14.img.xz indeed, ETH0 is still working with the U-Boot 2020.04 and my boot loop problem is gone also (tested with a few reboots, I back online each time). So, for now, this is it. U-Boot_2020.04.zip
  17. Yesterday, I was running the latest armbian image with the old U-Boot from 2019 and all was working fine until I rebooted the device, then the network didn't come back, I couldn't connect via SSH (my device is headless). Unfortunately, I didn't have have any log since I had no choice but to switch it off. So I think there really is something strange here. More testing needed. Edit: I've run a few tests with connected UART to USB in order to see it live. So, in fact eth0 is here and active, the problem reside elsewhere, I've got a boot loop in U-Boot whith messages like it can't mount the filesystem Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Full log of the boot loop: INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State OFF INFO: AffInst: Level 0, MPID 0x2, State OFF INFO: AffInst: Level 0, MPID 0x3, State OFF bl31 reb▒GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 114072 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 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 SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0 Sending bl30........................................OK. Run bl30... Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000018c0 Wait bl30...Done Sending bl301.......OK. Run bl301... , 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 SD, src: 0x00034200, des: 0x01000000, size: 0x00080f90 ef be ad de d f0 ad ba ef be ad de not ES chip [0.228833 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 2019.07-armbian (Sep 02 2019 - 01:17:47 +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 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 7159 bytes read in 2 ms (3.4 MiB/s) ## Executing script at 08000000 186 bytes read in 2 ms (90.8 KiB/s) ** fs_devread read error - block ** fs_devread read error - block ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 13869975 Bytes = 13.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7d222000, end 7df5c397 ... OK Loading Device Tree to 000000007d1b0000, end 000000007d221fff ... OK Starting kernel ... "Synchronous Abort" handler, esr 0x02000000 elr: ffffffffb63e7000 lr : 00000000010023a4 (reloc) elr: 0000000035350000 lr : 000000007ff6b3a4 x0 : 000000007d1b0000 x1 : 0000000000000000 x2 : 0000000000000000 x3 : 0000000000000000 x4 : 0000000034000000 x5 : 0000000000000001 x6 : 0000000000000008 x7 : 0000000000000000 x8 : 000000007df976a0 x9 : 0000000000000002 x10: 000000000a200023 x11: 0000000000000002 x12: 0000000000000002 x13: 000000007df66e0e x14: 000000007df5df3c x15: 000000007ff6aa60 x16: 0000000000000000 x17: 0000000000000020 x18: 000000007df66df8 x19: 000000007ffe4f48 x20: 0000000000000000 x21: 0000000000000000 x22: 0000000000000003 x23: 000000007df96df8 x24: 000000007ffd1c18 x25: 0000000000000000 x26: 000000007ff6b3cc x27: 0000000000000000 x28: 0000000000000400 x29: 000000007df5e010 Resetting CPU ... resetting ... INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State OFF INFO: AffInst: Level 0, MPID 0x2, State OFF INFO: AffInst: Level 0, MPID 0x3, State OFF bl31 reb▒GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 162131 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 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 SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0 Sending bl30........................................OK. Run bl30... Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000018c0 Wait bl30...Done Sending bl301.......OK. Run bl301... 0x10100000, size: 0x0001113020200, des --- 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: ef be ad de d f0 ad ba ef be ad de not ES chip [0.317743 Inits done] secure task start! high task start! low task start! Load bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x00080f90 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 2019.07-armbian (Sep 02 2019 - 01:17:47 +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 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 7159 bytes read in 3 ms (2.3 MiB/s) ## Executing script at 08000000 186 bytes read in 2 ms (90.8 KiB/s) ** fs_devread read error - block ** fs_devread read error - block ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 13869975 Bytes = 13.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7d222000, end 7df5c397 ... OK Loading Device Tree to 000000007d1b0000, end 000000007d221fff ... OK Starting kernel ... "Synchronous Abort" handler, esr 0x02000000 elr: ffffffffb63e7000 lr : 00000000010023a4 (reloc) elr: 0000000035350000 lr : 000000007ff6b3a4 x0 : 000000007d1b0000 x1 : 0000000000000000 x2 : 0000000000000000 x3 : 0000000000000000 x4 : 0000000034000000 x5 : 0000000000000001 x6 : 0000000000000008 x7 : 0000000000000000 x8 : 000000007df976a0 x9 : 0000000000000002 x10: 000000000a200023 x11: 0000000000000002 x12: 0000000000000002 x13: 000000007df66e0e x14: 000000007df5df3c x15: 000000007ff6aa60 x16: 0000000000000000 x17: 0000000000000020 x18: 000000007df66df8 x19: 000000007ffe4f48 x20: 0000000000000000 x21: 0000000000000000 x22: 0000000000000003 x23: 000000007df96df8 x24: 000000007ffd1c18 x25: 0000000000000000 x26: 000000007ff6b3cc x27: 0000000000000000 x28: 0000000000000400 x29: 000000007df5e010 Resetting CPU ... resetting ... INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State OFF INFO: AffInst: Level 0, MPID 0x2, State OFF INFO: AffInst: Level 0, MPID 0x3, State OFF bl31 reb▒GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 162134 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 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 SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0 Sending bl30........................................OK. Run bl30... Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000018c0 Wait bl30...Done Sending bl301.......OK. Run bl301... 0x10100000, size: 0x0001113020200, des --- 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: ef be ad de d f0 ad ba ef be ad de not ES chip [0.317751 Inits done] secure task start! high task start! low task start! Load bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x00080f90 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 2019.07-armbian (Sep 02 2019 - 01:17:47 +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 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 7159 bytes read in 3 ms (2.3 MiB/s) ## Executing script at 08000000 186 bytes read in 2 ms (90.8 KiB/s) ** fs_devread read error - block ** fs_devread read error - block ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ** fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 13869975 Bytes = 13.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7d222000, end 7df5c397 ... OK Loading Device Tree to 000000007d1b0000, end 000000007d221fff ... OK Starting kernel ... "Synchronous Abort" handler, esr 0x02000000 elr: ffffffffb63e7000 lr : 00000000010023a4 (reloc) elr: 0000000035350000 lr : 000000007ff6b3a4 x0 : 000000007d1b0000 x1 : 0000000000000000 x2 : 0000000000000000 x3 : 0000000000000000 x4 : 0000000034000000 x5 : 0000000000000001 x6 : 0000000000000008 x7 : 0000000000000000 x8 : 000000007df976a0 x9 : 0000000000000002 x10: 000000000a200023 x11: 0000000000000002 x12: 0000000000000002 x13: 000000007df66e0e x14: 000000007df5df3c x15: 000000007ff6aa60 x16: 0000000000000000 x17: 0000000000000020 x18: 000000007df66df8 x19: 000000007ffe4f48 x20: 0000000000000000 x21: 0000000000000000 x22: 0000000000000003 x23: 000000007df96df8 x24: 000000007ffd1c18 x25: 0000000000000000 x26: 000000007ff6b3cc x27: 0000000000000000 x28: 0000000000000400 x29: 000000007df5e010 Resetting CPU ... resetting ... INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State OFF INFO: AffInst: Level 0, MPID 0x2, State OFF INFO: AffInst: Level 0, MPID 0x3, State OFF bl31 reb▒GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 162130 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 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 SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0 Sending bl30........................................OK. Run bl30... Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000018c0 Wait bl30...Done Sending bl301.......OK. Run bl301... 0x10100000, size: 0x0001113020200, des --- 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: ef be ad de d f0 ad ba ef be ad de not ES chip [0.317742 Inits done] secure task start! high task start! low task start! Load bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x00080f90 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 2019.07-armbian (Sep 02 2019 - 01:17:47 +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 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 At first, we may think there an issue with the SDCARD, but this boot loop appen ONLY WHEN REBOOTING THE DEVICE, THE FIRST BOOT (while connecting power) IS ALWAYS SUCCESSFULL. then, I connect to ssh and type : reboot and Here we go. I Can't load the OS WITHOUT UNPLUGGING POWER FIRST May be a compatibilty problem between U-Boot and the latest kernel ...
  18. Backup the current u-boot: (md5 checked against original u-boot.bin file match) the count value my be different on yours dd if=/dev/mmcblk0 of=/tmp/installed_uboot.bin skip=97 count=1376 And check it's version : strings /tmp/installed_uboot.bin | grep "U-Boot 20" Indeed if you have a 2019.xx version you are ok apparently
  19. If I hex edit the file u-boot.bin (from both versions), I only have 1 occurence of "u-boot 20", just before it, there is the string : GPT: last_usable_lba incorrect: %llX > %lx
  20. You could plug in standard dupond wires in the white serial header with forcing a bit, it works perfectly well, I did it last time to see the bootloader
  21. I know it's weird but hex viewing the sectors show it, the working version I installed is U-Boot 2019.07-armbian (Sep 02 2019 - 01:17:47 +0200) VS the one preinstalled which doesn't work : U-Boot 2021.01-armbian (Feb 04 2021 - 00:08:45 +0100)
  22. Elclaudio

    Elclaudio

  23. OK I FOUND THE CULPRIT ! the issue come from UBOOT like I imagined. After installing older uboot ETH0 worked straight away Since I couldn't find the uboot .deb used in my old armbian 5.95 in https://imola.armbian.com/apt/pool/main/l/ I took the uboot files from my WORKING armbian version kernel 4.19.69 in /usr/lib/ linux-u-boot-next-odroidc2_5.95_arm64 there should be 2 files : bl1.bin.hardkernel and u-boot.bin copy them wherever you want on the latest armbian (currently in test : Armbian 21.02.2 Buster with Linux 5.10.16-meson64,) Linux odroidc2 5.10.16-meson64 #21.02.2 SMP PREEMPT Sun Feb 14 21:50:52 CET 2021 aarch64 GNU/Linux I backed up the original files in the same directory with .ORI extension Then I run the commands here If you do it beware with dd it could crash your partition if missused, also adapt the paths and filename to your particular case. #!/bin/bash # install older uboot from armbian kernel 4.19.69 dd if=/root/uboot/bl1.bin.hardkernel.OLD of=/dev/mmcblk0 bs=1 count=442 conv=fsync > /dev/null 2>&1; dd if=/root/uboot/bl1.bin.hardkernel.OLD of=/dev/mmcblk0 bs=512 skip=1 seek=1 conv=fsync > /dev/null 2>&1; dd if=/root/uboot/u-boot.bin.OLD of=/dev/mmcblk0 bs=512 seek=97 conv=fsync > /dev/null 2>&1 # restore original uboot #dd if=/root/uboot/bl1.bin.hardkernel.ORI of=/dev/mmcblk0 bs=1 count=442 conv=fsync > /dev/null 2>&1; #dd if=/root/uboot/bl1.bin.hardkernel.ORI of=/dev/mmcblk0 bs=512 skip=1 seek=1 conv=fsync > /dev/null 2>&1; #dd if=/root/uboot/u-boot.bin.ORI of=/dev/mmcblk0 bs=512 seek=97 conv=fsync > /dev/null 2>&1 It would be nice now to debug what's gone wrong with uboot code...
  24. Could anyone tell me where is the u-boot file(s) on the image, I couldn't identify where it is stored. Is it possible to try another u-boot version without breaking things ?
  25. Hi, What is your hardware revision ? The ethernet is not working BEFORE the kernel even load, at the u-boot stage, the message says No ethernet found. So I seriously doubt this has something to do with the kernel