Jump to content

DavidJS

Members
  • Posts

    31
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am using the rockpi-s board(with rockchip rk3308 soc), and want to change the console serial of the uboot. According to https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-patches, I tried: rm userpatches/u-boot/u-boot-rockchip64-v2022.04/u-boot-rockchip64-edge.patch ./compile.sh uboot-patch BOARD=rockpi-s BRANCH=edge RELEASE=bullseye BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,img EXTRAWIFI=n After I modified what I want in the uboot source code, I continue to copy the path to the userpatches path: cp output/patch/u-boot-rockchip64-edge.patch userpatches/u-boot/u-boot-rockchip64-v2022.04/ And compile the whole image: ./compile.sh BOARD=rockpi-s BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes COMPRESS_OUTPUTIMAGE=sha,img EXTRAWIFI=no KERNEL_CONFIGURE=no RELEASE=bullseye Everything seems to be fine, after compiled, I flashed the image to my EMMC flash, but it could not boot. And even if I don't make any meaningful changes, as long as I use this method to patch u-boot, the system will not start. As long as there is no this patch, it can be started. So I wonder if there is something wrong with this method?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines