RSS Bot

Description Firmware update. Jira reference number AR-1700 How Has This Been Tested? [ ] Build test as HW is n/a Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description -- remember its not rockpi 4SE its rock 4SE now that RK3399-T friendly ddr blobs have been added, lets given this a discrete config..... and use mainline uboot with an official uboot defconfig. View the full article

odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10 u-boot; UMS works; bump kernel to 6.5-rcX odroidm1/edge (rk3568-odroid): bump to 6.4.y, update config, rebase patches to 6.4.10 odroidm1/edge (rk3568-odroid): bump to 6.5-rc6; manually fix RK808 breakage in .config; rebase patches add patch to remove Petitboot-mandated MTD partitions this way we have access to the full flash, and can write our own u-boot to it rebase all patches odroidm1/edge (rk3568-odroid): drop 6.3 and 6.4 patches odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10 u-boot; UMS works using Kwiboo's rk3568-2023.10 branch with BINMAN-handled blobs patches (defconfig unless indicated): boot usb first (rockchip-common) blink leds & keep red one one on preboot change usb_host0_xhci to otg (u-boot dtsi) enable DM_GADGET, UMS 🔥 and RockUSB usage instructions: build & burn image to SD card insert SD card into board hold the recovery (RCY) button and power on the board watch board boot de-infest Petitboot: use armbian-install to install bootloader to MTD if you don't, you'll need to hold the recovery button every boot optionally: use armbian-install to install OS to eMMC/NVMe/USB power-off board remove SD card (new u-boot always boots SD first!) boot into your newly de-infested machine boot order: USB, SD, MMC, NVME, SCSI de-infested machine can now boot (directly) from USB/SATA/NVMe: Armbian UEFI-arm64 Fedora 38 aarch64 Talos arm64 others... extra: new u-boot by Kwiboo (with GMAC patches) gives us stable MAC address although it is based on cpuid#, doesn't match the HK sticker on the board odroidm1: update DDR/BL31 blobs (this depends on https://github.com/armbian/rkbin/pull/20) View the full article

Description Enabled compilation options for the USB interface MT7921 chip driver module mt7921u. Need to work with the corresponding firmware https://github.com/armbian/firmware/pull/57 . How Has This Been Tested? [x] built and tested on nanopi-r4s The Wi-Fi is working well, Bluetooth was not tested. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description bump atf to LTS v2.8 for Rockchip64 How Has This Been Tested? Rockpro64 boots Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article

Description I thought edge would carry the fixes forward, missed 6.4 folder. How Has This Been Tested? Carryover from 6.3 Checklist: [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

Description Debian moved riscv64 into 1st class so exceptions are not needed. But ports repository is still needed in the lists file as they didn't manage to move everything. Jira reference number AR-1824 How Has This Been Tested? [x] Generated image with clean rootfs Armbian_23.08.0-trunk_Star64_sid_edge_5.15.0.img Checklist: [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] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10-rc2+gmac u-boot odroidm1/edge (rk3568-odroid): bump to 6.4.y, update config, rebase patches to 6.4.10 odroidm1/edge (rk3568-odroid): bump to 6.5-rc6; manually fix RK808 breakage in .config; rebase patches add patch to remove Petitboot-mandated MTD partitions this way we have access to the full flash, and can write our own u-boot to it rebase all patches odroidm1/edge (rk3568-odroid): drop 6.3 and 6.4 patches odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10-rc2+gmac u-boot using Kwiboo's rk3568-2023.10-gmac branch with BINMAN-handled blobs patches: boot usb first preboot pci/usb enum/scan usage instructions: build & burn image to SD card insert SD card into board hold the recovery (RCY) button and power on the board watch board boot de-infest Petitboot: use armbian-install to install bootloader to MTD if you don't, you'll need to hold the recovery button every boot optionally: use armbian-install to install OS to eMMC/NVMe/USB power-off board remove SD card (new u-boot always boots SD first!) boot into your newly de-infested machine boot order: USB, SD, MMC, NVME, SCSI (SATA) de-infested machine can now boot (directly) from USB/SATA/NVMe: Armbian UEFI-arm64 Fedora 38 aarch64 Talos arm64 others... extra: new u-boot by Kwiboo (with GMAC patches) gives us stable MAC address although it is based on cpuid#, doesn't match the HK sticker on the board odroidm1: update DDR/BL31 blobs; cleanup old Petitboot stuff this depends on https://github.com/armbian/rkbin/pull/20 View the full article

Description The command takes long time to continue and it makes it seem like the build halted, so this adds an alert to mitigate this --> (3) COMMAND: fakeroot dpkg-deb -b -Znone /armbian/.tmp/work-cfd2d6ad-1f9b-473e-80e7-cbcf9d157c68/uboot-Bd1Ms /armbian/output/packages-hashed/gl> dpkg-deb: building package 'linux-u-boot-sipeed-lichee-pi-4a-current' in '/armbian/output/packages-hashed/global/linux-u-boot-sipeed-lichee-pi-4> --> (372) INFO: Built u-boot deb OK [ linux-u-boot-sipeed-lichee-pi-4a-current 2022.07-Se092-P0000-H6f49-V9cb9-B9963-R448a ] Jira reference number [AR-9999] How Has This Been Tested? Builds on my end Checklist: [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

See rationale on https://www.shellcheck.net/wiki/SC2086 Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] How Has This Been Tested? Blind edit Checklist: [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

Got the board too and doing OSHW development for the platform View the full article

Description Enabling CPU idle can lower CPU power at low load. How Has This Been Tested? [x] Bootup test [x] Stress test Checklist: [ ] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Prior to this patch, adding a user-overlay using the script will add the filename with a space after the user-overlays=, even if there aren't any overlays present. This will result in the following: before adding: user_overlays= after adding: user_overlays= rk3588-i2c0-m1.dts with a space. This patch will add another else branch to handle this, as well as handling any additional spaces present prior. New script does this before adding: user_overlays= or user_overlays= after adding: user_overlays=rk3588-i2c0-m1.dts Adding more overlays works as intended, with a space and the name.dtbo How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Copied conditional branch part of the code, modified changes and ran all the possible situations, worked as intended. [x] Modified the script the same way on my Rock5B with Armbian Bookworm 23.5.1 install and tried adding multiple overlays, worked as intended. Checklist: [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 Not strictly required [x] I have made corresponding changes to the documentation Not required [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules Not required View the full article

meson-g12-bananapi-rtl8822cs.dtbo (M2S / M5) meson-sm1-odroid-c4-rtl8822cs.dtbo (ODROID C4) Add support for the RTL8822CS expansion board. https://wiki.banana-pi.org/Banana_Pi_BPI-M5#Wifi_.26_BT_support_via_expansion_board The overlays were tested on the BananaPi M2S and ODROID C4. Although not intended to be used on the C4, it works without issue. NOTE: Whilst further testing, I found bluetooth doesn't come back upon reboot when using Armbian on the C4. Not really a game changer, but it needs to be resolved in the future. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

extensions: image-output-oowow: creates Khadas oowow compatible images extensions: image-output-oowow: creates Khadas oowow compatible images requires KHADAS_OOWOW_BOARD_ID set in board file (see next commit) always produces xz-compressed images, so this automatically disables COMPRESS_OUTPUTIMAGE uses xze script from Khadas, forcing IN and OUT env vars so it's not confused by fd 1 to use, add EXT=image-output-oowow parameter to build to get into oowow: VIM3/VIM3L: download oowow SD card image from Khadas: VIM3: https://dl.khadas.com/products/oowow/system/vim3-oowow-latest-sd.img.gz VIM3L: https://dl.khadas.com/products/oowow/system/vim3l-oowow-latest-sd.img.gz write image to SD card, use BalenaEtcher or similar insert SD card into board (and remove NVMe if present and bootable) boot board into Upgrade mode, see https://docs.khadas.com/products/sbc/vim3/install-os/boot-into-upgrade-mode oowow should be running now recommended: go into Advanced and reset to factory defaults, so MCU, PCIe/USB3 etc is reset to defaults VIM4/VIM4N/VIM1S/Edge2: those have oowow in SPI from factory, check out the manual there's a few ways to use these images with oowow: Using External media prepare media (USB), format it with ext4 or fat, copy produced oowow.img.xz to it for ease of use, rename the image file, so it begins with the board-id (vim1s-/vim4-/edge2- etc) boot board into oowow (see oowow's manual) insert media into board exit wizard, use "Write image to eMMC", browse to "../" change from "XXXX only" to "All" if you didn't rename the image choose image file and write (remove SD card if using one) and reboot Via network (Ethernet or Wi-Fi) boot board into oowow plug in Ethernet cable or connect to Wi-Fi (see oowow's manual) set the firewall mode to "allow" in oowow's Network Settings (see oowow's manual) obtain the IP address of the board in oowow (usually shown on top of the screen, or see manual) from a remote machine, use curl to upload and write the image to oowow's eMMC, example: curl -L <ip_address>/shell/write | sh -s - <image_filename>.oowow.img.xz reboot board From the Internet (one day) when Khadas publishes Armbian oowow images to their HTTP server khadas boards: VIM1S/3/3L/4/Edge2: add KHADAS_OOWOW_BOARD_ID definition for use with oowow (EXT=image-output-oowow) View the full article

Description rkr5.1 is already synced with rkr4. Tested on rock5b. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Rock5b kernel build success [x] Kernel works on rock5b Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description licheepi-4a: add a .wip for Sipeed LicheePi 4A board The u-boot of LicheePi 4A can be updated without the need to flash the system. Users can manually update it according to the instructions provided by Sipeed's wiki when needed. The opensbi used in LicheePi 4A is not packaged within u-boot using a fit image. Therefore, it is stored in the repository as a binary file. During startup, LicheePi 4A requires loading audio and aon firmware. These two files will also be stored in the repository in binary format. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Successfully built. [x] System startup. Checklist: [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 [ ] 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

Description Some sd cards are unable to access in uboot when using miniloader. These cards are able to access when using spl instead. Spl is not related to DDR initialization so it is unlikely to introduce DDR problems. How Has This Been Tested? [x] System boots [x] 5 minutes stress test Checklist: [ ] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description As per description. Maintainer on vacations / legacy kernel. How Has This Been Tested? [x] Build test Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description legacy - 5.15.124 -> 5.15.125 current - 6.1.43 -> 6.1.45 edge - 6.4.8 -> 6.4.10 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Booted legacy, current and edge images on Orange Pi Prime (sun50i H5) [X] Booted legacy, current and edge images on NanoPi Duo2 (sun8i H3) Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Move executing check from the script. It breaks if script runs for beta and stable at the same machine. Which will be the case. Checklist: [x] My changes generate no new warnings View the full article

Description This PR Includes: update patches to make them compatible with mainlined patches fix its timeout issue update kernel to rc5 add orange pi 5 plus devicetree add some nodes to orange pi 5 devicetree How Has This Been Tested? [x] Orange Pi 5 Plus boots fine and M2-E key, USBs except type-c work Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

hashed-OCI-revisioned-debs: introduce "reversioning" of .deb packages trap-logging: just discard logs dir when ANSI_COLOR=none repo-reprepro.py: set -e & pipefail prepare_host: handle PRE_PREPARED_HOST inside prepare_host_init() so WORKDIR etc is always available kernel-debs: avoid showing tree of kernel modules if they've not been built for example EXT=nomod causes no modules to be built debs: all produced debs now get a placeholder DEBIAN/changelog and a usr/share/doc .gz changelog with hash artifacts: don't keep deb-tar's .tar after uploading to OCI they won't ever be used after this, and just accumulate trash for no reason hashed-OCI-revisioned-debs: get completely rid of artifact_prefix_version hashed-OCI-revisioned-debs: build debs in PACKAGES_HASHED_STORAGE, not DEB_STORAGE (temp commit, will be rewritten by a later commit) fakeroot_dpkg_deb_build() now only takes a single argument, the unpacked package dir kernel/tmpfs: remove usage of the kernel-specific tmpfs for temporary kernel .deb's, now build directly to packages-hashed dir uboot: drop CHOSEN_UBOOT, change deployment directory, remove uboot_name as temp_dir prefix change deployment dir to not include REVISION or ARCH get rid uboot's CHOSEN_UBOOT, REVISION and ARCH in the directory name. no two u-boot debs can be installed in the same machine anyway pipeline: output-debs-to-repo-json.py: adapt to new reversioned JSON info hashed-OCI-revisioned-debs: introduce "reversioning" of .deb packages tl-dr: maximize OCI cache hit ratio across nightlies/releases/PRs/etc; publish simple Version:'s that don't include a crazy hash in repo and images introduce output/packages-hashed directory radically change the output/debs directory structure simplify artifact's prepare_version() method for deb and deb-tar artifacts: artifact_base_dir and artifact_final_file will now be auto-calculated; thus removed from each artifact (except rootfs) artifact_deb_repo ("global", "jammy", "bookworm") is now required; "global" means common across all RELEASES artifact_deb_arch is now required, "all" is arch-independent, otherwise use ${ARCH} artifact_map_debs is now auto-calculated based on the above, and shouldn't be specified manually artifact_final_version_reversioned is optional, and can force the final version of the artifact (specific for the base-files case) artifacts that need special handling for reversioning can add function names to artifact_debs_reversion_functions array (base-files and bsp-cli cases) artifacts prepare_version() should set artifact_version, but never include it in other variables; artifact_version is now changed by framework after prepare_version() returns no longer use/refer/mention ${REVISION} when building packages. All packages should be ${REVISION}-agnostic. ${REVISION} (actually, artifact_final_version_reversioned) will be automatically swapped in the control file during reversioning fakeroot_dpkg_deb_build() now takes exactly two arguments: the directory to pack, and the deb ID (key of artifact_map_packages dict); add this change in all the artifact's code for this obtain_complete_artifact(): automatically adds -Rxxxx "revisioning-hash" to artifact_version, by hashing the revisioning functions and any artifact_debs_reversion_functions set calculates more complex subdirectory paths for both the output/packages-hashed and output/debs/output/debs-beta directories with the new subdirectories we can be sure a re-version is already done correctly and can skip it (eg, for partial download-debs re-runs) in the future we can automatically clean/remove old versions that are no longer relevant based on the dir structure exports a lot more information to JSON, including the new subdirectory paths comment-out code that implemented skip_unpack_if_found_in_caches, I'm very unsure why we had this in the first place obtain_artifact_from_remote_cache() for deb type artifacts, OCI won't preserve the subdirectory structure, so move downloaded files to the correct subdirectory manually this is not needed for deb-tar, since that can preserve the dir structure itself introduce artifacts-reversion.sh and its main function artifact_reversion_for_deployment() this has the logic for reversioning .deb's, by ar-unpacking them, changing control.tar (and possibly data.tar), handling .xz compression, etc. also handles hashing those functions, for consistency. Any changes in reversioning code actually change the artifact itself so we're not caught by surprise by default, it changes control file only: replace Version: (which is the hash-version originally) with artifact_final_version_reversioned (which is mostly just ${REVISION}) add a custom field Armbian-Original-Hash: with the original hash-version artifact_reversion_for_deployment() is called by new CLI wrapper cli_obtain_complete_artifact(), used for CLI building of specific artifact, but also for download-artifact build_artifact_for_image() used during image build armbian-bsp-cli-deb.sh: move ${REVISION} related stuff from the main package build to new reversioning functions. artifact-armbian-base-files.sh: move ${REVISION} related stuff from the main package build to new reversioning functions. kernel: add some custom fields to DEBIAN/control: Armbian-Kernel-Version: / Armbian-Kernel-Version-Family: (for future use: cleanup of usage of Source: field which should be removed) declutter the Description: field, moving long description out of the first line obtain IMAGE_INSTALLED_KERNEL_VERSION from the reversioned deb (this is still a hack and has not been fixed) uboot: declutter the Description: field, moving long description out of the first line use the reversioned .deb when deploying u-boot to the image main_default_build_packages() now stores reversioned values and complete paths to reversioned .deb's list_installed_packages() now compares custom field Armbian-Original-Hash: , and not the Version: to make sure debs in the image are the ones we want install_artifact_deb_chroot() is a new wrapper around install_deb_chroot() for easy handling of reversioned debs use it everywhere install_deb_chroot() was used in distro-agnostic.sh and distro-specific.sh main-config: allow using REVISION from env or command-line param; ensure it begins with digit pipeline: force compositor to include REVISION= just like it already did for BETA= this way the prepare step's REVISION (possibly passed via CLI parameter) is always sovereign pipeline: streamline output-debs-to-repo-json to pass down info and avoid parsing paths completely artifacts: obtain: back to using flat output/debs structure, include revisioned and hashed in filename, but no subdirectories handle the global artifact_deb_repo case specially (they go in the root, not subdir) adapt obtain_complete_artifact() and friends to new reversioned scheme; introduce UPLOAD_TO_OCI_ONLY=yes for deploying to remote cache tl-dr: only deploys to remote OCI if UPLOAD_TO_OCI_ONLY=yes; stop leaving junk behind in local cache in many situations simplify CLI artifact building parameters and behaviour ARTIFACT_USE_CACHE is now deprecated, and its behaviour is the default for any uploading to OCI to occur, UPLOAD_TO_OCI_ONLY=yes must be present; in this case, reversioning is not done FORCE_ARTIFACTS_DOWNLOAD is completely removed (use download-artifact instead) cli_obtain_complete_artifact()'s and build_artifact_for_image()'s reversioning is now moved to common obtain_complete_artifact() standard_artifact_reversion_for_deployment(): check for hashed deb existence only if reversioned does not exist touch the reversioned file if it already exists; helps to clean up junk later delete hashed version after reversioning, so we don't leave trash behind unless in download-artifact mode, which touches the hashed version we can later delete old files from packages-hashed to keep junk under control refactor obtain_complete_artifact() extract function artifact_dump_json_info() since obtain is large enough already when deploying to remote, always ignore all local and remote caches introduce artifact_is_available_in_revisioned_local_cache() if not deploying to remote, and revisioned cache exists, use it directly if deploying to remote, reversioned is not checked and not created if deploying to remote, force DEB_COMPRESS=xz if deploying to remote, completely remove the local cache base dir after upload is done (no more junk leftover) store dict of artifacts actually installed in image; use it to freeze (BSPFREEZE=yes) and check hashes without spurious errors eg: linux-headers might, or might not, be installed; same with bsp-cli transitional accidentally fixes AR-1802 start-end: undo unintentional damage done to python/python2 compatibility symlinks inside the BIN_WORK_DIR kernel: fix: when KERNEL_SKIP_MAKEFILE_VERSION=yes, use 1- prefix for artifact_version (eg odroidxu4) artifact-{bsp-cli,kernel,uboot}: fix missing vars_config_hash "variables hash" in artifact_version_reason View the full article

Description Update odroidxu4-current kernel to 5.4.253. How Has This Been Tested? [x] Reboot of my Odroid HC1 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article