BarTender

I have an C2 and an old VU7 (800x480p60hz) https://wiki.odroid.com/accessory/display/vu_series/vu7/vu7#tab__odroid-c2 that I was hoping to use for a mini kiosk. Was able to run the older Hard Kernel supplied images with the uboot boot.ini updates suggested above to change disable auto detect, fix the resolution, and set to DVI rather than HDMI mode. When I loaded the latest Focal image from Armbian when I have the screen switched on then the kernel faults and reboots. ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7b06a000, end 7bf49d63 ... OK Loading Device Tree to 000000007aff8000, end 000000007b069fff ... OK Starting kernel ... GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0; TE: 59543 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton I assume all I should need to do is update the /boot/boot.cmd, run `mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr` and the boot.scr should be updated. Also set: setenv disable_vu7 "false" But that variable isn't being used anywhere in the boot.cmd so I don't think it is being applied.

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:

Awesome Igor, much appreciated. That has saved a whole lot of time rebuilding u-boot and I completely missed that in the documentation .... and I can now see the SATA SSD: smartctl -a /dev/sda === START OF INFORMATION SECTION === Device Model: SAMSUNG MZMPA128HMFU-000H1 Fantastic, now I have plenty of storage for the Router / MITM / Docker host.

I'm trying to enable SATA support on my Clearfog Base that has an eMMC that I boot from. Had a lot of trouble getting the kwboot version that would work and get initial UART boot working with the correct 01001 DIP switch setting. But now it is working with Buster and I have a MSATA SSD that I would like to add for additional storage. In theory all I should need to do is rename the patch for sata0 : mv 'patch/u-boot/u-boot-clearfog/clearfog-pci0=msata.patch.disabled' 'patch/u-boot/u-boot-clearfog/clearfog-pci0=msata.patch' Then build it using: ./compile.sh BOARD=clearfogbase BRANCH=current BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=no The only uboot file that is built is the uart one: ./cache/sources/u-boot-armada/v2018.01-solidrun-a38x/u-boot-spl-uart.kwb So, how do I specify building the mmc target? As I am thinking if I copy the target_mmc patch into the target_uart folder and disable the target_uart that would work, but there must be a better way and is there a way to only build u-boot and not need to rebuild the whole kernel?

Also have a C1+ and happy to assist with testing, just tried to connect up an I2C RTC and aml_i2c is missing from the current released version of buster. modprobe aml_i2c modprobe: FATAL: Module aml_i2c not found in directory /lib/modules/5.10.21-meson Armbian 21.02.3 Buster with Linux 5.10.21-meson Any way I can compile the library standalone or will I need to rebuild the kernel?

Starting to get into the armbian image a whole lot more as I prefer the lightweight nature of it over ubuntu mate on the ODroid C2. One issue I ran into today is the armbian kernel isn't built from the current hardkernel C2 kernel image: https://github.com/hardkernel/linux/tree/odroidc2-3.14.y I'm trying to get the 3.5" LCD Shield running on there, naturally it works fine on ubuntu mate C2 image but the kernel used for the armbian build is a different fork. The specific fbtft customised version for the C2 sits under the kernel here: https://github.com/hardkernel/linux/blob/odroidc2-3.14.y/drivers/video/fbtft/flexfb.c I'm happy to rebuild the kernel from the hard kernel source, but was wondering which source was being used?

Hi I'm wondering why chromium is missing from the ODroid C2 image when taking the non-desktop image and then adding the necessary packages to get a minimal X working? Planning to just build it from source, but wondering why it was missing from the core armbian distro? Is there a reason?