RSS Bot Posted September 14, 2023 Share Posted September 14, 2023 REVIEWERS: Squash using GitHub UI with message from the first commit beaglev-ahead: Official support Adds community support for the board Includes a kernel config for thead edge thus the high count of changes Description Implement a community support for BeagleV-Ahead Depends on changes from https://github.com/armbian/build/pull/5689 Progress from https://github.com/armbian/build/pull/5684 The original work is on https://github.com/Kreyren/armbian-build-kreyren/compare/6cd581c96c0b7b800b6549afe23112d4a662d2a0..811288169004dccacab964129ecaf8cfe891b22d i tried to shorten it as much as possible for the easy merge request review The image boots and seems to work without major issues If the fans doesn't work then invoke following from userland: echo 1 > /sys/class/pwm/pwmchip0/export echo 1000000 > /sys/class/pwm/pwmchip0/pwm1/period echo 1000000 > /sys/class/pwm/pwmchip0/pwm1/duty_cycle echo 1 > /sys/class/pwm/pwmchip0/pwm1/enable Making fans to spin is implemented in the DTS and they should work, mentioned just in case to avoid overheating of the chip The audio has issues with playback e.g. crab rave from youtube has lot of popping sounds on both the HDMI output and headphones through JACK, same observed on the official image Tracked in https://github.com/armbian/build/issues/5692 for the optimized toolchain UEFI was not implemented and i try to submit that in next patch, TODO tracking Complains about: [π³|π¨] ===================== WARNING ====================== [π³|π¨] This board does not use CONFIG_DM_USB. Please update [π³|π¨] the board to use CONFIG_DM_USB before the v2019.07 release. [π³|π¨] Failure to update by the deadline may result in board removal. [π³|π¨] See doc/driver-model/MIGRATION.txt for more info. [π³|π¨] ==================================================== [π³|π¨] ===================== WARNING ====================== [π³|π¨] CONFIG_OF_EMBED is enabled. This option should only [π³|π¨] be used for debugging purposes. Please use [π³|π¨] CONFIG_OF_SEPARATE for boards in mainline. [π³|π¨] See doc/README.fdt-control for more info. [π³|π¨] ==================================================== I try to address it in next merge request The GPU and NPU are not usable, context in Figure out the GPU and NPU https://github.com/ryan4yin/nixos-licheepi4a/issues/11.. blame the manufacturer GNOME doesn't compile as it's currently broken for riscv64 in debian repositories I didn't work on ubuntu compatibility, @chainsx seems to be better option for that as it seems to be his main distro and the OS configuration is shared from SiPeed LicheePi 4A Debian claims that bookworm will never support riscv so should be flagged Trixie doesn't build because: [π³|πΈ] Could not find package filename for 'base-files' in 'https://packages.debian.org/bookworm/riscv64/base-files/download' [ looking for base-files ] Debian upstream informed and working on the issue, i try to submit patch if they take long time Complains about: [ 2.563670] [ 2.565219] ******************************************************************** [ 2.572714] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE ** [ 2.580204] ** ** [ 2.587680] ** WRITEABLE clk DebugFS SUPPORT HAS BEEN ENABLED IN THIS KERNEL ** [ 2.595150] ** ** [ 2.602619] ** This means that this kernel is built to expose clk operations ** [ 2.610105] ** such as parent or rate setting, enabling, disabling, etc. ** [ 2.617589] ** to userspace, which may compromise security on your system. ** [ 2.625091] ** ** [ 2.632561] ** If you see this message and you are not debugging the ** [ 2.640030] ** kernel, report this immediately to your vendor! ** [ 2.647498] ** ** [ 2.654967] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE ** [ 2.662433] ******************************************************************** [ 2.669998] random: fast init done I try to address that in upcoming merge, TODO tracking The flashing is not implemented and needs to be done manually as i and the riscv community ware unable to find any documentation or data on how to make it bootable through the sdcard, needs to be flashed through fastboot: Hold the BOOT button and connect the USB-C cable to your system Verify that the Android Downloader shows up in # dmesg Verify that fastboot can see the device with # fastboot devices Invoke: # fastboot flash rom ./path/to/uboot/binary # Flash the binary in the tempfs so that we can flash it # fastboot reboot # Reboot the device to the binary # fastboot flash uboot ./path/to/uboot/binary # Flash the uboot on the board # fastboot flash root ./path/to/rootfs.tar # Flash the rootfs Remove the USB-C and try to boot the device, you should be greeted with armbian Jira reference number: Ehwww jira How Has This Been Tested? By a community member on his device As a part of https://github.com/armbian/build/pull/5689 and https://github.com/armbian/build/pull/5714 Built using: $ ./compile.sh build BOARD=beaglev-ahead BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes EXPERT=yes KERNEL_CONFIGURE=no RELEASE=sid Checklist: [X] git revert https://github.com/armbian/build/pull/5691 [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] I have commented my code, particularly in hard-to-understand areas [X] I have made corresponding changes to the documentation [X] My changes generate no new warnings [X] Any dependent changes have been merged and published in downstream modules View the full article Link to comment Share on other sites More sharing options...
Recommended Posts