Jump to content

mfreudenberg

Members
  • Posts

    27
  • Joined

  • Last visited

  1. 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.
  2. 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.
  3. 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"
  4. 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
  5. 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
  6. 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 🙃.
  7. 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!!!
  8. 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.
  9. 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?
  10. 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.
  11. 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 ;-)).
  12. 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?
  13. 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.
  14. 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
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines