mfreudenberg

So, i was able to resovle my issue by setting the appropriate combination of kernel and u-boot version in my `userpatches/lib.conf`: Kernel = v5.15.82 U-Boot = v2022.07 In addition to that, i'm checking out the branch `v22.11` to build the image.

Hi, thanks for the tip. Unfortunately, that seem not to work. I have done the following: Switched to branch "v22.11" by setting it in the LIB_TAG variable of `config-default.conf` I have forced my GitLab CI process to checkout the v22.11 tag by including git clone -b v22.11 ... into the script I have set the BUILD_ONLY="" to empty (as recommended by the script) I have installed another VM, with a gitlab-runner and attached this gitlab-runner to my instance. I have removed any caching from my ci pipeline as i thought this might cause the issue. previously i had a three stage build process, that had a checkout, build and cleanup stage. the checkout stage, did the cloning of the armbian-build repo and stored it into a gitlab cache the build stage used this cache and moved the userpatches folder to the build subfolder. The existing userpatches folder gets deleted every time. the cleanup stage, deleted any built images from the cache to preserve some disk space, before storing the cache I'm not sure, what happend, that my build suddenly fails. Right now, i'm falling back to building it semi-manual. I'm cloning my repo (containing the customization scripts) on a VM and merge it with a freshly cloned armbian-build repo.

Hi, my current CI build fails, and i cannot make up, whats wrong with it. It was working previously until i moved my project within the GitLab instance to another folder. Now i'm getting the following errors: tail output.log OBJCOPY lib/efi_loader/dtbdump.efi CC lib/vsprintf.o CC lib/strto.o CC lib/abuf.o OBJCOPY lib/efi_loader/initrddump.efi CC lib/date.o CC lib/rtc-lib.o CC lib/elf.o AR lib/built-in.o [ error ] ERROR in function compile_uboot [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:261 -> functions/main/build-tasks.sh:128 -> functions/compilation/uboot.sh:131 -> functions/logging/traps.sh:0 ] [ error ] U-boot compilation failed [ o.k. ] Process terminated # somewhere in the middle of the compilation.log CC cmd/sf.o AR drivers/nvme/built-in.o AR drivers/power/battery/built-in.o AR drivers/power/fuel_gauge/built-in.o CC cmd/sysboot.o drivers/net/phy/phy.c: In function ‘get_phy_driver’: drivers/net/phy/phy.c:652:15: error: ‘YT_8531C_PHY_ID’ undeclared (first use in this function) 652 | if(phy_id == YT_8531C_PHY_ID) | ^~~~~~~~~~~~~~~ drivers/net/phy/phy.c:652:15: note: each undeclared identifier is reported only once for each function > AR drivers/power/mfd/built-in.o make[3]: *** [scripts/Makefile.build:254: drivers/net/phy/phy.o] Error 1 make[2]: *** [scripts/Makefile.build:394: drivers/net/phy] Error 2 make[2]: *** Waiting for unfinished jobs.... CC drivers/pinctrl/pinctrl-uclass.o CC drivers/power/pmic/pmic-uclass.o CC drivers/power/regulator/regulator-uclass.o tail compilation.log CC drivers/video/panel-uclass.o CC drivers/video/simple_panel.o TTF drivers/video/u_boot_logo.S OBJCOPY lib/efi_loader/initrddump.efi CC drivers/video/dw_hdmi.o AR lib/built-in.o AS drivers/video/u_boot_logo.o AR drivers/video/rockchip/built-in.o AR drivers/video/built-in.o make: *** [Makefile:1894: drivers] Error 2 I have tried to switch the repo mirrors, or different tags. I even deleted the entire checked out directory (build) and checked it out again. After cloning the repo and running the compile script with my config-default.config i'm ending up with the same error. Any idea, what could be wrong? I already checked the permissions (actually I'm running the compile script as root). It seems there is some issue with the network driver? my config-default.conf # Read build script documentation https://docs.armbian.com/Developer-Guide_Build-Options/ # for detailed explanation of these options and for additional options not listed here # leave empty to select each time, set to "yes" or "no"> KERNEL_ONLY="no" # leave empty to select each time, set to "yes" or "no" to skip> KERNEL_CONFIGURE="no" # comma-separated list of clean targets: "make" = make clean for select> # "debs" = delete packages in "./output> # "alldebs" = delete all packages in ".> # "cache" = delete "./output/cache", "s> # "oldcache" = remove old cached rootfs> CLEAN_LEVEL="make,debs,cache" # yes: use kernel config file from previous compilation for the same branch, device family and version # no: use default or user-provided config file KERNEL_KEEP_CONFIG="yes" # comma-separated list of core modules which will be installed > # "u-boot", "kernel", "bsp", "armbian-config", "armbian-firmwar> # leave empty to build from sources or use local cache REPOSITORY_INSTALL="" BUILD_DESKTOP="yes" DEST_LANG="de_DE.UTF-8" # advanced # compile and install or install prebuilt additional packages EXTERNAL_NEW="prebuilt" # change to "branchname" to use any branch currently available. LIB_TAG="v22.08" # additions to compile 'unattended' DESKTOP_ENVIRONMENT="xfce" DESKTOP_APPGROUPS_SELECTED="editors, internet" DESKTOP_ENVIRONMENT_CONFIG_NAME="config_base" # additions to compile for the rock-pi4 BOARD="rockpi-4b" BRANCH="current" RELEASE="bullseye" # yes: will stop the script and prompt for adding userpatches (kernel, u-boot) CREATE_PATCHES="no" # creates logs in output/debug PROGRESS_LOG_TO_FILE="yes" # set to yes, to prevent cloning from git OFFLINE_WORK="no" # provides a faster download USE_MAINLINE_GOOGLE_MIRROR="yes" USE_GITHUB_UBOOT_MIRROR="yes" # create compressed archive with image file and GPG signature f> # yes - compatibility shorcut for sha,gpg,7z COMPRESS_OUTPUTIMAGE="yes"

Awesome! Thanks a lot!

Hi, i'd like to know if it's possible to disable the first run wizard (set up of root password, timezone locale etc) via armbian build framework? I have build my own image, and set the parameter DEST_LANG="de_DE.UTF-8" , but still the wizard shows up after flashing and asks me for the locale. Can i do this type of customization in the customize-image.sh? (sorry if that's a too stupid or obvious question). This is my customize-image.sh script (i have truncated it). #!/bin/bash # arguments: $RELEASE $LINUXFAMILY $BOARD $BUILD_DESKTOP # # This is the image customization script # NOTE: It is copied to /tmp directory inside the image # and executed there inside chroot environment # so don't reference any files that are not already installed # NOTE: If you want to transfer files between chroot and host # userpatches/overlay directory on host is bind-mounted to /tmp/overlay in chroot # The sd card's root path is accessible via $SDCARD variable. echo "add user rock" useradd -s /bin/bash -m -c "rock" rock -p rock echo "set hostname" hostname -b "myrockpi" echo "update armbianEnv" ARMBIANENV="/boot/armbianEnv.txt" if grep -q "console=" "$ARMBIANENV"; then sed -i 's/console=.*/console=display/g' $ARMBIANENV else echo "console=display" >> $ARMBIANENV fi Michael

I'd love to do that. But at this point I'm afraid i still lack deeper knowledge of the armbian build framework. I might think of providing some documentation on that. When i look into some other merge requests, it seems to be a regular thing to use these files to configure the u-boot. https://github.com/armbian/build/pull/2086/commits/174fcf76db573886ac6bd5310be8c593dfec37dd

So this solution didn't work out on my Rock-PI. I got the following errors: => coninfo List of available devices: serial@ff1a0000 00000007 IO serial 00000003 IO stdin stdout stderr nulldev 00000003 IO => printenv stdin ## Error: "stdin" not defined => setenv stdin usbkbd ## Error inserting "stdin" variable, errno=22 BUT, fideling around a bit with the u-boot console i was able to set the bootdelay environment variable via the u-boot console. After a reboot, the console did not react anymore to any random keys i was sending via console 👍. The command i used was: => setenv bootdelay -2 => saveenv Saving Environment to SPIFlash... Erasing SPI flash...Writing to SPI flash...done OK => boot Interestingly, after reflashing a different U-Boot without the bootdelay mod, i wasn't able get back to the u-boot console. It seems, that this is kind of permanent? Just wondering, not that it would be an issue for me 🙃.

That seems to be the guy, that does the trick. After setting the option in that file, and flashing the compiled u-boot i was able to resolve my issue. The boot does not hang anymore, when i "spam" the console via keyboard. That's the least location, where i would expect to put my changes 😁. That slightly brings me back to the original topic of this thread. I wanted to apply a userpatch, but it doesn't work as described by the "manual". Wouldn't this be worth a bug in github? Nevertheless, thanks a lot for your hints and the support @usual user @Igor!!!

Where do i set that varibale? I tried to set it in the following files - config-default.conf - config/boards/rockpi-4b.conf - build/config/bootscripts/boot-rockchip64.cmd (yes, i know i shouldn't edit this one) Interestringly, i cannot add bootdelay=-2 to the armbianEnv.txt. That doesn't seem to work.

Hi, if you mean this snipplet # CONFIG_AUTOBOOT=y CONFIG_BOOTDELAY=0 # CONFIG_AUTOBOOT_KEYED is not set # CONFIG_AUTOBOOT_USE_MENUKEY is not set # CONFIG_USE_BOOTARGS is not set # CONFIG_BOOTARGS_SUBST is not set CONFIG_USE_BOOTCOMMAND=y CONFIG_BOOTCOMMAND="run distro_bootcmd" # CONFIG_USE_PREBOOT is not set CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-rock-pi-4b.dtb" # # Console # CONFIG_MENU=y # CONFIG_CONSOLE_RECORD is not set # CONFIG_DISABLE_CONSOLE is not set CONFIG_LOGLEVEL=4 CONFIG_SPL_LOGLEVEL=4 That's not a patch. That's the config file i am extracting from the compiled u-boot*.deb to chek if the patch was applied. If i run the script with a working patch i get this log output: [ o.k. ] * [l][c] rk3399-disable-hdmi.patch [ o.k. ] * [l][c] rk3399-enable-stable-mac.patch [ o.k. ] * [l][c] rk3399-populate-child-node-of-syscon.patch [ o.k. ] * [u][c] rk3399-set-bootdelay.patch [ o.k. ] * [l][c] sdmmc-force-fifo-mode-in-spl.patch [ o.k. ] * [l][c] u-boot-rk-rk3399-usb-start-firefly-rk3399.patch [ o.k. ] * [l][c] u-boot-rk-rk3399-usb-start-nanopc-t4.patch [ o.k. ] * [l][c] u-boot-rk-rk3399-usb-start.patch [ o.k. ] * [l][c] u-boot-rk3399-set-bootdelay.patch [ warn ] Make your changes in this directory: [ /home/michael/ws/build/cache/sources/u-boot/v2022.04 ] [ warn ] Press <Enter> after you are done [ waiting ] I guess that means, that my patch (rk3399-set-bootdelay.patch) was applied. Not sure what [u][c] means - I guess it stands for userpatch? The point is when i continue with <enter>, at that state of the script, i get the log output below. I must have missed it the whole time, i guess. [ warn ] No changes found, skipping patch creation I have checked the script source here and as it seems, the first branch of the if clause is not executed. I always end up in the else branch with the display_alert warning. I just don't understand why? Do i have to apply the userpatches, when the script halts? To try an alternative way, i have placed my patch in patch/u-boot/u-boot-rockchip64. The script runs fine, i get no warnings whatsoever, but as soon as i unzip the compiled deb-file i see that CONFIG_BOOTDELAY is still set to 0, allthough the patch was applied. I don't understand why?

Hi, thanks for the reply. Did you just replaced the local source folders of your armbian-build-framework repo? Like cp to cache/sources/u-boot? I'm still struggeling with flashing the bootloader. I have compiled my own u-boot, but as soon as i flash it (no matter if RKDevTool or dd via linux) the Rock does not boot. Update: I have figured out, how to see whats going on on my serial console during boot. I just needed to set my baudrate to 1500000 and switch off flow control. Afterwards, i can see this: U-Boot TPL 2022.07-dirty (Sep 15 2022 - 08:41:28) sdram_init: LPDDR3 - 800MHz failed! rk3399_dmc_init DRAM init failed -22 Any idea, what that means? I'm getting this when flashing my self-built u-boot-rockchip.bin.

Small update. Meanwhile i have started to building u-boot according to the manual from u-boot directly. What i can determine is, that there is a difference between the u-boot.bin, that is contained in the *.deb file i am creating with the armbian-build-framework and the u-boot-bin that i create with the u-boot sources. The armbian u-boot is exaclty 4MB in size. If i flash it, my Rock-PI does not boot. The "original" compiled u-boot is around 8,9MB (the same size, that you @usual user) have sent me. Unfortunately, if i flash it, the rock-pi does not boot. I compiled it with no specific settings - it's all defaults for the rk3399 platform. Btw.: I was able to flash your u-boot by using the RKDevTool. I just had to setup two "items" in the tool - The loader itself - The u-boot binary with an offset of 0x00000040 (i took the hint from your linux-command decimal offset of 64 is 0x40 in hex ;-)).

Success! I was able to get this nice screen: In addition to that, i could not disrupt the boot with the serial console. So my question would be, which parameter did you set to get the serial console not to react on my "random" keys?

so this is my layout: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1 179:0 0 28,9G 0 disk └─mmcblk1p1 179:1 0 28,6G 0 part / mmcblk1boot0 179:32 0 4M 1 disk mmcblk1boot1 179:64 0 4M 1 disk zram0 252:0 0 1,9G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log I'm bit confused as i'm not sure which of the three "disk" type partitions i should use. I'd probably go with one of the mmcblk1boot* disks, but you wrote, that it's between the MBR and the first partition, so i guess i go for mmcblk1.

Hi, so did the following flashing your u-boot image using linux and dd with the provided command This seemed not to work, as i wasn't sure which device i should use for flashing. I used the fourth of the /dev/mmcblk devices (sorry, don't have the exact name for it as i'm currently reflashing my rock with RKDevTool). lsusb listed this blockdevice labeled with BOOT, so i used this one. After rebooting the Rock-PI didn't boot. I saw some characters popping up in my serial console (USB-to-serial connected to a RS485-HAT). flashing you u-boot image using RKDevTool on Windows. This seemed to work as the RKDevTool indicated a success. But still, after rebooting the Rock-PI, there was no Screen, and the boot seemingly halted. What i can say is, that there were way more "characters" popping up in my serial console as with the "stock-u-boot" from armbian. Michael

Out of curiosity i have unpacked the compiled linux-u-boot-current-rockpi-4b_22.08.0-trunk_arm64.deb. In the folder /usr/lib/u-boot i have found a rock-pi-4-rk3399_defconfig. Looking into it i could see, that neither CONFIG_BOOTDELAY nor CONFIG_DISABLE_CONSOLE were set, allthough the build script claimed the patches were successfully accapted. See also my logs and patches: patching.log ... Processing file /home/michael/ws/build/userpatches/u-boot/u-boot-rockchip64/rk3399-disable-console.patch Processing file /home/michael/ws/build/patch/u-boot/u-boot-rockchip64/rk3399-disable-hdmi-roc-pc.patch Processing file /home/michael/ws/build/patch/u-boot/u-boot-rockchip64/rk3399-disable-hdmi.patch Processing file /home/michael/ws/build/patch/u-boot/u-boot-rockchip64/rk3399-enable-stable-mac.patch Processing file /home/michael/ws/build/patch/u-boot/u-boot-rockchip64/rk3399-populate-child-node-of-syscon.patch Processing file /home/michael/ws/build/userpatches/u-boot/u-boot-rockchip64/rk3399-set-bootdelay.patch ... extracted rock-pi-4-rk3399_defconfig # CONFIG_AUTOBOOT=y CONFIG_BOOTDELAY=0 # CONFIG_AUTOBOOT_KEYED is not set # CONFIG_AUTOBOOT_USE_MENUKEY is not set # CONFIG_USE_BOOTARGS is not set # CONFIG_BOOTARGS_SUBST is not set CONFIG_USE_BOOTCOMMAND=y CONFIG_BOOTCOMMAND="run distro_bootcmd" # CONFIG_USE_PREBOOT is not set CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-rock-pi-4b.dtb" # # Console # CONFIG_MENU=y # CONFIG_CONSOLE_RECORD is not set # CONFIG_DISABLE_CONSOLE is not set CONFIG_LOGLEVEL=4 CONFIG_SPL_LOGLEVEL=4 my patches: # rk3399-disable-console.patch --- a/configs/rock-pi-4-rk3399_defconfig 2022-09-08 13:11:36.338776585 +0000 +++ a/configs/rock-pi-4-rk3399_defconfig 2022-09-09 07:57:35.991434703 +0000 @@ -89,2 +89,3 @@ CONFIG_SPL_TINY_MEMSET=y CONFIG_ERRNO_STR=y +CONFIG_DISABLE_CONSOLE=y # rk3399-set-bootdelay.patch --- a/configs/rock-pi-4-rk3399_defconfig 2022-09-09 09:46:19.898147074 +0000 +++ b/configs/rock-pi-4-rk3399_defconfig 2022-09-09 09:46:19.898147074 +0000 @@ -89,3 +89,4 @@ CONFIG_SPL_TINY_MEMSET=y CONFIG_ERRNO_STR=y CONFIG_DISABLE_CONSOLE=y +CONFIG_BOOTDELAY=-2 run of compile.sh [ o.k. ] * [l][c] rk3399-always-init-rkclk.patch [ o.k. ] * [u][c] rk3399-disable-console.patch [ o.k. ] * [l][c] rk3399-disable-hdmi-roc-pc.patch [ o.k. ] * [l][c] rk3399-disable-hdmi.patch [ o.k. ] * [l][c] rk3399-enable-stable-mac.patch [ o.k. ] * [l][c] rk3399-populate-child-node-of-syscon.patch [ o.k. ] * [u][c] rk3399-set-bootdelay.patch [ o.k. ] * [l][c] sdmmc-force-fifo-mode-in-spl.patch [ o.k. ] * [l][c] u-boot-rk-rk3399-usb-start-firefly-rk3399.patch [ o.k. ] * [l][c] u-boot-rk-rk3399-usb-start-nanopc-t4.patch [ o.k. ] * [l][c] u-boot-rk-rk3399-usb-start.patch

Hi @Igor, thanks for this hint! I didn't knew that, but it seems logical to me, that the NAND somehow has to be updated. When i run the nand-sata-installer i get two screens and no other options: 1. Install/Update the bootloader on SD/eMMC 2. Writing Bootloader. Done It seems to work, but somehow it doesn't solve my actual issue. The 1st reboot of the Rock-PI works fine. When i do my "spamming" during the second reboot, the rockpi stops booting - so it seems nothing has changed. But maybe that's offtopic for this thread.

Hi @usual user, thanks for the hint. I'll try it out. Just to make sure i'm not making another mistake: For installing the U-Boot, do i just need to install the *.deb from the output/debs folder? Or do i have to do somehting else? Currently, I'm just installing the Packages linux-u-boot-current-rockpi-4b_*-trunk_arm64.deb and linux-image-current-rockchip64_*-trunk_arm64.deb. Thanks

Update on that thread: I was playing around with make menuconfig as advised in this thread. I have created several u-boot patches, that should have disabled the serial console during boot. But none of them succeeded. I'm still able to stop the boot process by "spamming random characters" through a serial console, during boot. I'm wondering, if i'm following the correct approach. My last patch for u-boot is as follows: --- a/.config 2022-09-08 13:11:36.338776585 +0000 +++ b/.config 2022-09-09 07:57:35.991434703 +0000 @@ -407,7 +409,7 @@ # CONFIG_MENU=y # CONFIG_CONSOLE_RECORD is not set -# CONFIG_DISABLE_CONSOLE is not set +CONFIG_DISABLE_CONSOLE=y CONFIG_LOGLEVEL=4 CONFIG_SPL_LOGLEVEL=4 CONFIG_TPL_LOGLEVEL=4 This patch should just disable the console, but apparently it doesn't.

Hi, i was successfully able to run menuconfig. I spent the last two days playing around with the settings and creating different patches. But somehow, i am not able to disable the console in u-boot. Every time i reboot i can stop the Rock-PI from booting, by spamming a connected serial console with random characters from my keyboard. But that's maybe offtopic. I have a seperate thread for that. I guess, this one can be marked as solved (is there such a feature in this forum?).

Small update from my side. I was able to successfully compile the kernel and u-boot, but i wasn't able to resolve my initial issue. Although, i was able to change the serial port from stdout-path = "serial2:1500000n8"; to stdout-path = "serial4:1500000n8"; I am still able to interrupt the boot process using an RS485 hat with an USB-to-Serial adapter. I just open a serial terminal (PyTTY) and spam the keyboard, while the board is rebooting. I can see, that the hat is receiving data (as the RX LED is flashing). I am also receiving some data (that i cannot interpret with PuTTY), when i "do the spamming": I maybe should add some background story to my thread. We are using the Rock-PI 4B to read out this weather sensor. The sensor is connected through an RS485-hat from zihatec. The hat uses serial port 2 via GPIO, which is hardwired so we cannot change it. Sometimes when we have to reboot the Rock-PI from remote, it doesn't reappear again. After checking the Board we can see, that it is stuck in the U-Boot. We assume, that the sensor is sending some data through the RS485 hat, just at the moment, when the Rock-PI reboots, thus interrupting the boot process. While looking for a solution, i stumbled upon this thread in this forum. Here OP is seemingly able to change the serial port of the u-boot, by doing almost the same as i do. In addition OP is setting the UART status to "okay". I'm wondering, why the uart is still enabled on my board, as the file "./arch/arm64/boot/dts/rockchip/rk3399.dtsi" clearly shows that the uart status for port 2, 3 and 4 is "disabled".

Hi, sorry for the late response. I was busy compiling 😄. How do you run make menuconfig? Do you run it from the root of the build repo?

Hi @usual user, thanks a lot for the hint. I would never thought, that this is the way of disabling a Kconfig option. Still it seems i cannot run the compile script successfully. I have changed the patch to the following: diff --git a/configs/rock-pi-4-rk3399_defconfig b/configs/rock-pi-4-rk3399_defconfig index be07b16bae..63d04ced6e 100644 --- a/configs/rock-pi-4-rk3399_defconfig +++ b/configs/rock-pi-4-rk3399_defconfig @@ -13,7 +13,7 @@ CONFIG_DEBUG_UART_CLOCK=24000000 CONFIG_SPL_SPI_FLASH_SUPPORT=y CONFIG_SPL_SPI=y -CONFIG_DEBUG_UART=y +# CONFIG_DEBUG_UART is not set CONFIG_SYS_LOAD_ADDR=0x800800 # CONFIG_ANDROID_BOOT_IMAGE is not set CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-rock-pi-4b.dtb" but i still get the same error as listed above. If i disable, the patch by moving it to a non-patch file. The compiling runs without any issues. Anything else that i can check? Thanks a lot!

Hi, i'm trying to compile an u-boot for my Rock-PI 4B. I wanted to apply a userpatch, that disables the uart debug console in u-boot. I seem to have an issue when using the Rock-PI together with a weather-sensor via RS485-Hat. Here is my patch: diff --git a/configs/rock-pi-4-rk3399_defconfig b/configs/rock-pi-4-rk3399_defconfig index be07b16bae..63d04ced6e 100644 --- a/configs/rock-pi-4-rk3399_defconfig +++ b/configs/rock-pi-4-rk3399_defconfig @@ -13,7 +13,7 @@ CONFIG_DEBUG_UART_CLOCK=24000000 CONFIG_SPL_SPI_FLASH_SUPPORT=y CONFIG_SPL_SPI=y -CONFIG_DEBUG_UART=y +CONFIG_DEBUG_UART=n CONFIG_SYS_LOAD_ADDR=0x800800 # CONFIG_ANDROID_BOOT_IMAGE is not set CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-rock-pi-4b.dtb" When i run the compile script, the patch is applied successfully, but something goes wrong and i cannot find a hint what could be the issue. This is my config-default.conf # Read build script documentation https://docs.armbian.com/Developer-Guide_Build-Options/ # for detailed explanation of these options and for additional options not listed here KERNEL_ONLY="yes" # leave empty to select each time, set to "yes" or "no" to skip dialog prompt KERNEL_CONFIGURE="no" # leave empty to select each time, set to "yes" or "no" to skip dialog prompt CLEAN_LEVEL="make,debs,oldcache,cache" # comma-separated list of clean targets: "make" = make clean for selected ke> # "debs" = delete packages in "./output/debs" for current branch and family, # "alldebs" = delete all packages in "./output/debs", "images" = delete "./o> # "cache" = delete "./output/cache", "sources" = delete "./sources" # "oldcache" = remove old cached rootfs except for the newest 8 files REPOSITORY_INSTALL="" # comma-separated list of core modules which will be installed from reposito> # "u-boot", "kernel", "bsp", "armbian-config", "armbian-firmware" # leave empty to build from sources or use local cache DEST_LANG="en_US.UTF-8" # sl_SI.UTF-8, en_US.UTF-8 # advanced EXTERNAL_NEW="prebuilt" # compile and install or install prebuilt additional packages INSTALL_HEADERS="" # install kernel headers package LIB_TAG="master" # change to "branchname" to use any branch currently available. USE_TORRENT="no" # use torrent network for faster toolchain and cache download DOWNLOAD_MIRROR="" # set to "china" to use mirrors.tuna.tsinghua.edu.cn CARD_DEVICE="" # device name /dev/sdx of your SD card to burn directly to the card when done # additions to compile for the rock-pi4 CREATE_PATCHES="yes" BOARD="rockpi-4b" BRANCH="current" RELEASE="bullseye" PROGRESS_LOG_TO_FILE="yes" OFFLINE_WORK="no" USE_MAINLINE_GOOGLE_MIRROR="yes" USE_GITHUB_UBOOT_MIRROR="yes" LIB_TAG="v22.05.3" userpatch log [ o.k. ] Started patching process for [ u-boot rockchip64-rockpi-4b-current ] [ o.k. ] Looking for user patches in [ userpatches/u-boot/u-boot-rockchip64 ] [ o.k. ] * [l][c] add-board-clockworkpi-a06.patch ... [ o.k. ] * [l][c] u-boot-rk-rk3399-usb-start-nanopc-t4.patch [ o.k. ] * [l][c] u-boot-rk-rk3399-usb-start.patch [ o.k. ] * [u][c] u-boot-rk_rk3399-disable-uart-debug.patch [ warn ] Make your changes in this directory: [ /home/michael/ws/build/cache/sources/u-boot/v2022.04 ] [ warn ] Press <Enter> after you are done [ waiting ] compilation aborts with AR spl/drivers/built-in.o LD spl/u-boot-spl OBJCOPY spl/u-boot-spl-nodtb.bin SYM spl/u-boot-spl.sym CAT spl/u-boot-spl-dtb.bin COPY spl/u-boot-spl.bin [ error ] ERROR in function compile_uboot [ main.sh:588 -> main.sh:481 -> compilation.sh:240 -> general.sh:0 ] [ error ] U-boot compilation failed [ o.k. ] Process terminated i found this in the compilation.log /home/michael/ws/build/cache/sources/u-boot/v2022.04/drivers/ram/rockchip/sdram_common.c:232: undefined reference to> /home/michael/ws/build/cache/toolchain/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-> /home/michael/ws/build/cache/sources/u-boot/v2022.04/drivers/ram/rockchip/sdram_common.c:349: undefined reference to> CC spl/drivers/mmc/sdhci.o CC spl/drivers/core/syscon-uclass.o make[1]: *** [scripts/Makefile.spl:509: tpl/u-boot-tpl] Error 1 make: *** [Makefile:2112: tpl/u-boot-tpl.bin] Error 2 make: *** Waiting for unfinished jobs.... CC spl/drivers/mmc/rockchip_sdhci.o CC spl/drivers/core/of_extra.o CC spl/drivers/core/ofnode.o But i cannot makeup, what could be the issue?

Hi @belfastraven, thanks for the help. After moving my patch to the userpatches/kernel folder i was able to compile it with the patch enabled! Thanks a lot!