Luigi Calligaris

  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Luigi Calligaris's Achievements

  1. Thank you @SteeMan. I'm starting to get a grasp on how the full build process is done: you run Yocto on the backend of the build scripts to generate a U-Boot image. Right now I'm having a look at the meta-meson upstream repo. This is likely going to be painful...but "no pain no gain," and I'd like to learn to use Yocto as it is supposed to be used, without Xilinx's customizations in between like in PetaLinux
  2. Dear all, I own a 4G/64G H96 MAX X3, and I have tried using the pre-compiled Armbian_20.07_Arm-64_focal_current_5.7.8_desktop.img multiplatform Armbian Focal image together with the DTB by @root-stas with very good success (it seemed to work quite well in my usage, I noticed some instability in the Chromium browser, I'm aware the graphics support was not yet ready). I tried the new 2020.10, so far without GUI and I see that it boots correctly, giving me a terminal on the UART terminals I soldered on the PCB (I kept the wires tidy, and hope those pads last). I have some experience with building a Linux kernel, creating a simple kernel module, and some marginal knowledge of configuring U-Boot on Zynq Ultrascale+ SoCs, but this is a different workflow from the Armbian one, on which I'm quite ignorant. I would like take the opportunity with my TV box to learn to walk on my own legs and build Armbian from source. I followed the Armbian build documentation, cloned the Armbian build repo, ran the compile script with the options below, chose the Odroid-C4 as the target board in menuconfig, and let the script and gcc crunch their way to the end. ./compile.sh KERNEL_ONLY="no" KERNEL_CONFIGURE="yes" BUILD_DESKTOP="yes" INSTALL_HEADERS="yes" EXTERNAL_NEW="prebuilt" EXPERT="yes" USE_MAINLINE_GOOGLE_MIRROR="yes" AUFS="yes" BRANCH="current" RELEASE="focal" BOARD="odroidc4" By mounting the output image, I noticed that the boot directory does not match the one of the official image. I expect this, since I only target the S905X3 on an Odroid-C4, but some features like the U-Boot environment vars in extlinux/extlinux.conf is not there. I would like to be able to build an image in synch with the current releases, especially regarding the U-Boot configuration. Can someone give me a tip on how should I change my build workflow? Thanks! Luigi
  3. So, I confirm that on Focal with Kernel 5.7.8 HDMI audio works out of the box (even with eMMC installs). While backing up the (unmounted and not in use) original eMMC prior to flashing I noticed the entire system would freeze for many seconds, to the point it would cease to respond to pings. I would expect this to happen to the dd process trying to access the eMMC for reading, but having it happening to the entire system is a surprise. Any idea? I learned the hard way (I bricked the eMMC install and had to re-install from SD card) that updating the kernel to a new stable version via apt-get will break the system (frozen on green screen before even seeing the kernel log). Which is the recommended way to do so? Is this a known issue or should it be subject to more study? If it is a known issue, what is failing there?
  4. Hello, this is to report that I just tested the latest version of Armbian Focal 20.04 on H96 MAX X3 Armbian_20.07_Arm-64_focal_current_5.7.8_desktop.img.xz together with the DTB from @root-stas h96max-x2-test-bus80-gpu-volt.dtb (question, why the "x2" in the filename? Is it derived from/common to the S905X2 DTB or is a typo?) It seems to work great: so far I tested WiFi, HDMI audio, Ethernet. I could connect an USB webcam and use it for videoconferencing (Vidyo web-based client). I just noticed some instability in chromium (it rarely crashes when loading a new page), but this could be an issue with chromium itself. I have't yet flashed to eMMC and when I do so I'll check if I experience the issue with HDMI audio as well. Thanks to all for the great work! Luigi