openSUSE/SLE/Mainline U-boot for some not-yet-supported ARM64 boards
an idea by ldevulder
Updated about 3 years ago. 7 hacker ♥️. 1 follower. Has no hacker: grab it!

The Khadas VIM (http://khadas.com/vim/) is an arm64 DIY Set-Top-Box based on Amlogic P212 reference board that use S905X SoC.

As Odroid-C2 (based on S905 SoC) is in the mainline U-boot, it should be possible to adapt it for the Khadas VIM (of course a lot of work are needed!). It's also possible to try using the Amlogic code found in the 2015.01 version of U-Boot.

Also, Khadas VIM is supported in the mainline kernel, so when we will have a working U-Boot, installation and boot of openSUSE Tumbleweed with EFI should be possible.

The upgrade version, the VIM2, is based on an Amlogic S912 SoC, which is an upgraded version of the S905X SoC. Both are now supported in mainstream Linux Kernel (4.12 for Khadas VIM and next 4.14 for Khadas VIM2).

For me, the goal of this project is to better understand how U-boot and Amlogic SoCs are working (and also others boards!).

I'm pretty sure that my U-Boot version will not not work at the end of the week, but I hope that my knowledge of it will be improved!

Goal for HackWeek 19: - Refresh my U-Boot knowledge (didn't had enough spare time since the last HackWeek...) - Try to add openSUSE wiki page for AML-S805X-AC (first quick tests shown that TW is not booting, need to check why) - Try to work on ROC-RK3328-CC support (U-Boot and TW) - Help on packaging official BL31 ATF firmware for GXL (GXM supported?)

Goal for HackWeek 18: - Fix the USB U-Boot issue on VIM2 board (EDIT: done upstream) - Add other ARM64 boards: work on ROC-RK3328-CC (EDIT: still lot of issues...)

Update of 14 February 2020: - Patches to add ROC-RK3328-CC support in U-Boot done! Latest TW version doesn't boot correctly, I need to check why - Some tests has been done with AML-S805X-AC board: TW kernel boots but there are some kernel oops/panic on version 5.4. Bug created and I need to test later with kernel 5.5

Update of 13 July 2018: - Khadas VIM is working well with latest U-Boot version (a patch is still needed for USB boot) and latest openSUSE TW. Wikipage as been created for it and also for another SBC with pretty much the same hardware, the Libretech-CC. - My work will now focus on Khadas VIM2 board: U-boot is working with patches from BayLibre (apart USB), I found an issue with MMU initialization in U-Boot and I was able to fix it. Patch has been sent to Neil Armstrong of BayLibre for inclusion in his VIM2 patches.

Update for July 2018: - Board is working with official U-Boot and openSUSE TW. I will try to create add u-boot support for that board for TW and create and wiki page for openSUSE during HackWeek 17.

Update of 24 Octobre 2017: - Minimal U-Boot is booting on VIM board and EFI boot works, as openSUSE TW installation iso boots. I need to add needed modules to be able to install it.

Update of 12 October 2017: - U-Boot support is on a good way for P212 board, see https://patchwork.ozlabs.org/cover/825135/. Thanks to BayLibre guys! So I will use these patches to see if VIM can boot. First I will have a look at the code to better understand U-boot :)

No Hackers yet

Join this project

Looking for hackers with the skills:

khadas vim aarch64 arm64 arm u-boot uboot kernel

This project is part of:

Hack Week 16 Hack Week 17 Hack Week 18 Hack Week 19

Activity

  • about 5 years ago: aplanas liked this project.
  • almost 6 years ago: acho liked this project.
  • over 6 years ago: pgonin liked this project.
  • over 6 years ago: dmdiss liked this project.
  • over 7 years ago: michals liked this project.
  • over 7 years ago: a_faerber liked this project.
  • over 7 years ago: mbrugger liked this project.
  • over 7 years ago: ldevulder disliked this project.
  • over 7 years ago: ldevulder liked this project.
  • over 7 years ago: ldevulder added keyword "khadas" to this project.
  • over 7 years ago: ldevulder added keyword "vim" to this project.
  • over 7 years ago: ldevulder added keyword "aarch64" to this project.
  • over 7 years ago: ldevulder added keyword "arm64" to this project.
  • over 7 years ago: ldevulder added keyword "arm" to this project.
  • over 7 years ago: ldevulder added keyword "u-boot" to this project.
  • over 7 years ago: ldevulder added keyword "uboot" to this project.
  • over 7 years ago: ldevulder added keyword "kernel" to this project.
  • over 7 years ago: ldevulder originated this project.


    • Comments

    • a_faerber
      over 5 years ago by a_faerber | Reply

      AFAIK we're still lacking an Open Source toolchain to build a bootable image for VIM (gxl) and VIM2 (gxm?). Maybe you could contribute to extending my meson-tools to allow more people to contribute to and benefit from your efforts?

      Also, you might want to help package and test the new upstream BL31 in arm-trusted-firmware.

      • ldevulder
        about 5 years ago by ldevulder | Reply

        Thx, I will try to work on BL31 packaging for HackWeek 19.

    • ldevulder
      about 5 years ago by ldevulder | Reply

      Remi Pommarel also created a toolchain for gxl/gxm called gxlimg.

      As for upstream BL31 I tested it and yes I could try to help packaging it, could be for the next HackWeek 19 :-)

    Similar Projects

    Investigate non-booting Forlinx OKMX8MX-C board (aarch64) by a_faerber

    Description

    In the context of a SUSE customer inquiry last year, a Forlinx OKMX8MX-C arm64 board had been relayed to me from China that a customer was not successful booting SUSE Linux Micro on. Typically this happens when the vendor's bootloader (e.g., U-Boot) is not configured properly (e.g., U-Boot's distro boot) to be compliant with Arm SystemReady Devicetree (formerly IR) band. Unfortunately I could not immediately get it to emit any output, to even diagnose why it wasn't working. There was no public documentation on the vendor's website to even confirm I was checking the right UARTs.

    Earlier this year (2024) I happened to meet the ODM/OEM, Forlinx, at Embedded World 2024 in Nuremberg and again the Monday before Hackweek 24 at Electronica 2024 in Munich. The big puzzle was that the PCB print "OKMX8MX-C" does not match any current Forlinx product, there being OKMX8MM-C and OKMX8MP-C products with the Mini and Plus variants of NXP i.MX 8M family instead. One suggestion from Forlinx staff was to double-check the DIP switches on the board for boot mode selection.

    Goals

    Double-check the board name and investigate further what may be wrong with this board.

    Resources

    none

    Progress

    • The board name is indeed as spelled above, not matching any product on forlinx.net.
    • The DIP switches were set to boot from microSD.
    • Changing the DIP switches to eMMC boot did result in UART1 RS-232 output! (although at times garbled with the cable supplied and USB adapter used)
    • As feared, it did not automatically load our GRUB from USB.
    • Booting our GRUB manually from USB (via eMMC U-Boot commands fatload+bootefi) was unsuccessful, with partially Chinese error messages.
    • This confirmed the initial suspicion, already shared with Forlinx at Embedded World 2024, that the Forlinx System-on-Module's boot firmware was not Arm SystemReady Devicetree compliant and that a firmware update would be necessary to remedy that.
    • The microSD card turned out not to contain a bootable image but to only include Chinese-language board documentation (dated 20220507) and BSP files. They used a diverging name of OKMX8MQ-C.

    Improve various phones kernel mainline support (Qualcomm, Exynos, MediaTek) by pvorel

    Similar to previous hackweeks ( https://hackweek.opensuse.org/projects/improve-qualcomm-soc-msm8994-slash-msm8992-kernel-mainline-support, https://hackweek.opensuse.org/projects/test-mainline-kernel-on-an-older-qualcomm-soc-msm89xx-explore-mainline-kernel-qualcomm-mainlining) try to improve kernel mainline support of various phones.

    Result

    In the end I concentrated again to msm8994:

    Investigate non-booting Forlinx OKMX8MX-C board (aarch64) by a_faerber

    Description

    In the context of a SUSE customer inquiry last year, a Forlinx OKMX8MX-C arm64 board had been relayed to me from China that a customer was not successful booting SUSE Linux Micro on. Typically this happens when the vendor's bootloader (e.g., U-Boot) is not configured properly (e.g., U-Boot's distro boot) to be compliant with Arm SystemReady Devicetree (formerly IR) band. Unfortunately I could not immediately get it to emit any output, to even diagnose why it wasn't working. There was no public documentation on the vendor's website to even confirm I was checking the right UARTs.

    Earlier this year (2024) I happened to meet the ODM/OEM, Forlinx, at Embedded World 2024 in Nuremberg and again the Monday before Hackweek 24 at Electronica 2024 in Munich. The big puzzle was that the PCB print "OKMX8MX-C" does not match any current Forlinx product, there being OKMX8MM-C and OKMX8MP-C products with the Mini and Plus variants of NXP i.MX 8M family instead. One suggestion from Forlinx staff was to double-check the DIP switches on the board for boot mode selection.

    Goals

    Double-check the board name and investigate further what may be wrong with this board.

    Resources

    none

    Progress

    • The board name is indeed as spelled above, not matching any product on forlinx.net.
    • The DIP switches were set to boot from microSD.
    • Changing the DIP switches to eMMC boot did result in UART1 RS-232 output! (although at times garbled with the cable supplied and USB adapter used)
    • As feared, it did not automatically load our GRUB from USB.
    • Booting our GRUB manually from USB (via eMMC U-Boot commands fatload+bootefi) was unsuccessful, with partially Chinese error messages.
    • This confirmed the initial suspicion, already shared with Forlinx at Embedded World 2024, that the Forlinx System-on-Module's boot firmware was not Arm SystemReady Devicetree compliant and that a firmware update would be necessary to remedy that.
    • The microSD card turned out not to contain a bootable image but to only include Chinese-language board documentation (dated 20220507) and BSP files. They used a diverging name of OKMX8MQ-C.

    Create openSUSE images for Arm/RISC-V boards by avicenzi

    Project Description

    Create openSUSE images (or test generic EFI images) for Arm and/or RISC-V boards that are not yet supported.

    Goal for this Hackweek

    Create bootable images of Tumbleweed for SBCs that currently have no images available or are untested.

    Consider generic EFI images where possible, as some boards can hold a bootloader.

    Document in the openSUSE Wiki how to flash and use the image for a given board.

    Boards that I have around and there are no images:

    • Rock 3B
    • Nano PC T3 Plus
    • Lichee RV D1
    • StartFive VisionFive (has some image needs testing)

    Hack Week 22

    Hack Week 21

    Resources

    Create DRM drivers for VESA and EFI framebuffers by tdz

    Description

    We already have simpledrm for firmware framebuffers. But the driver is originally for ARM boards, not PCs. It is already overloaded with code to support both use cases. At the same time it is missing possible features for VESA and EFI, such as palette modes or EDID support. We should have DRM drivers for VESA and EFI interfaces. The infrastructure exists already and initial drivers can be forked from simpledrm.

    Goals

    • Initially, a bare driver for VESA or EFI should be created. It can take functionality from simpledrm.
    • Then we can begin to add additional features. The boot loader can provide EDID data. With VGA hardware, VESA can support paletted modes or color management. Example code exists in vesafb.

    Modularization and Modernization of cifs.ko for Enhanced SMB Protocol Support by hcarvalho

    Creator:
    Enzo Matsumiya ematsumiya@suse.de @ SUSE Samba team
    Members:
    Henrique Carvalho henrique.carvalho@suse.com @ SUSE Samba team

    Description

    Split cifs.ko in 2 separate modules; one for SMB 1.0 and 2.0.x, and another for SMB 2.1, 3.0, and 3.1.1.

    Goals

    Primary

    Start phasing out/deprecation of older SMB versions

    Secondary

    • Clean up of the code (with focus on the newer versions)
    • Update cifs-utils
    • Update documentation
    • Improve backport workflow (see below)

    Technical details

    Ideas for the implementation.

    • fs/smb/client/{old,new}.c to generate the respective modules
      • Maybe don't create separate folders? (re-evaluate as things progresses!)
    • Remove server->{ops,vals} if possible
    • Clean up fs_context.* -- merge duplicate options into one, handle them in userspace utils
    • Reduce code in smb2pdu.c -- tons of functions with very similar init/setup -> send/recv -> handle/free flow
    • Restructure multichannel
      • Treat initial connection as "channel 0" regardless of multichannel enabled/negotiated status, proceed with extra channels accordingly
      • Extra channel just point to "channel 0" as the primary server, no need to allocate an extra TCPServerInfo for each one
    • Authentication mechanisms
      • Modernize algorithms (references: himmelblau, IAKERB/Local KDC, SCRAM, oauth2 (Azure), etc.

    Contributing to Linux Kernel security by pperego

    Description

    A couple of weeks ago, I found this blog post by Gustavo Silva, a Linux Kernel contributor.

    I always strived to start again into hacking the Linux Kernel, so I asked Coverity scan dashboard access and I want to contribute to Linux Kernel by fixing some minor issues.

    I want also to create a Linux Kernel fuzzing lab using qemu and syzkaller

    Goals

    1. Fix at least 2 security bugs
    2. Create the fuzzing lab and having it running

    The story so far

    • Day 1: setting up a virtual machine for kernel development using Tumbleweed. Reading a lot of documentation, taking confidence with Coverity dashboard and with procedures to submit a kernel patch
    • Day 2: I read really a lot of documentation and I triaged some findings on Coverity SAST dashboard. I have to confirm that SAST tool are great false positives generator, even for low hanging fruits.
    • Day 3: Working on trivial changes after I read this blog post: https://www.toblux.com/posts/2024/02/linux-kernel-patches.html. I have to take confidence with the patch preparation and submit process yet.
      • First trivial patch sent: using strtruefalse() macro instead of hard-coded strings in a staging driver for a lcd display
      • Fix for a dereference before null check issue discovered by Coverity (CID 1601566) https://scan7.scan.coverity.com/#/project-view/52110/11354?selectedIssue=1601566
    • Day 4: Triaging more issues found by Coverity.
      • The patch for CID 1601566 was refused. The check against the NULL pointer was pointless so I prepared a version 2 of the patch removing the check.
      • Fixed another dereference before NULL check in iwlmvmparsewowlaninfo_notif() routine (CID 1601547). This one was already submitted by another kernel hacker :(
    • Day 5: Wrapping up. I had to do some minor rework on patch for CID 1601566. I found a stalker bothering me in private emails and people I interacted with me, advised he is a well known bothering person. Markus Elfring for the record.

    • Wrapping up: being back doing kernel hacking is amazing and I don't want to stop it. My battery pack is completely drained but changing the scope gave me a great twist and I really want to feel this energy not doing a single task for months.

      I failed in setting up a fuzzing lab but I was too optimistic for the patch submission process.

    The patches

    1

    Improve various phones kernel mainline support (Qualcomm, Exynos, MediaTek) by pvorel

    Similar to previous hackweeks ( https://hackweek.opensuse.org/projects/improve-qualcomm-soc-msm8994-slash-msm8992-kernel-mainline-support, https://hackweek.opensuse.org/projects/test-mainline-kernel-on-an-older-qualcomm-soc-msm89xx-explore-mainline-kernel-qualcomm-mainlining) try to improve kernel mainline support of various phones.

    Result

    In the end I concentrated again to msm8994:

    Officially Become a Kernel Hacker! by m.crivellari

    Description

    My studies as well my spare time are dedicated to the Linux Kernel. Currently I'm focusing on interrupts on x86_64, but my interests are not restricted to one specific topic, for now.

    I also "played" a little bit with kernel modules (ie lantern, a toy packet analyzer) and I've added a new syscall in order read from a task A, the memory of a task B.

    Maybe this will be a good chance to...

    Goals

    • create my first kernel patch

    Resources

    Achivements