Jump to content

TobiMuc

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. I was able to solve it here. My Radxa Pi Zero boots from eMMC with USB drive attached. If someone has the same issue, here is a quick walkthrough: # login as a non-root user # Clone git from https://github.com/armbian/build#build-tools-overview git clone https://github.com/armbian/build.git # Some info: https://docs.armbian.com/Developer-Guide\_Build-Options/ # Remove the patch that we don't want: rm build/patch/u-boot/v2022.10/meson64-boot-usb-nvme-scsi-first.patch # Compile u-boot ./compile.sh build BOARD=radxa-zero BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no BUILD_ONLY=u-boot KERNEL_CONFIGURE=no RELEASE=bookworm # Somehow it compiles more than u-boot but less than without BUILD_ONLY=u-boot # Optional backup of the deb packages to a mounted drive: # sudo cp -a build/output/debs/* /mnt/radxa # install sudo dpkg -i build/output/debs/*.deb /home/tobi/build/output/debs/bookwork/*.deb # install u-boot sudo armbian-config # Select system -> Install -> Install .. on ..eMMC.. # Reboot with fingers crossed
  2. Thanks, that really looks like the reason for this. I don't get it... why do people buy a much more expensive Pi Zero with eMMC? Because they want the system on a relyable eMMC instead of USB or SD. I don't understand why there is a patch that boots from USB first. Isn't there a way to configure the order or to disable USB during the boot process? Sorry but whenever I try to find information about u-boot it is a complete mess what I get and nothing works. Compiling it sounds like many hours of try and error.
  3. Hi, I installed armbian_23.8.1_Radxa-zero_bookworm-current_6.1.50 on Radxa Pi Zero eMMC and I have an USB SSD drive connected as storage. Everything worked fine using it as a NAS but if I reboot there is an endless loop of reboots with the core message "scanning bus usb0ff5000000 for devices... Synchronous Abort handler, err 0x56000010". If I disconnect the USB drive it boots fine and when reconnect it after the boot process, the drive works fine. But I really need a system that is able to boot without temporarely disconnecting USB. I tried different combinations of USB with two different hubs or without hub. There are no boot flags on the partitions. I completely deleted all partitions on the drive and tried different kind of partitions and file systems. It does not change anything. Even without any partition it has the same error. I have another USB SSD that also causes a few pages of error messages but after that it does boot (from eMMC). Unfortunately that is the wrong USB drive and does not help. Switching too the newest kernel with armbian-setup also does not work. Finally I installed Radxa Ubuntu 20 and it boots without any issues while the USB SSD is connected. What can I do to solve this when using Armbian? Thanks Tobi
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines