Elclaudio

  • Content Count

    26
  • Joined

  • Last visited

About Elclaudio

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    France
  1. 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 ?
  2. 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 4c52ad58f483bb8ce9fd767c6af9f
  3. 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(2
  4. 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.
  5. 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
  6. Damn, and this code is supposed to drive rocket into space
  7. 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 ?
  8. 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 ??
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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)