Skip to main content ↑ ↓
Topic: Custom installed ARMtix on RPi4. Stuck on U-boot. (Read 235 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Custom installed ARMtix on RPi4. Stuck on U-boot.

Like the title says. Now it's u-boot that I'm stuck on.



The boot folder is a bit messy though. Maybe I would need to delete some of it,
but I don't know what.

Code: [Select]
$ ls -lha
total 324M
drwxr-xr-x  4 root root 8,0K  1 jan  1970 .
drwxr-xr-x  1 root root  260  8 dec 22:45 ..
-rwxr-xr-x  1 root root  32K 22 jan 17:49 bcm2710-rpi-2-b.dtb
-rwxr-xr-x  1 root root  34K 22 jan 17:49 bcm2710-rpi-3-b.dtb
-rwxr-xr-x  1 root root  35K 22 jan 17:49 bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x  1 root root  32K 22 jan 17:49 bcm2710-rpi-cm3.dtb
-rwxr-xr-x  1 root root  33K 22 jan 17:49 bcm2710-rpi-zero-2.dtb
-rwxr-xr-x  1 root root  33K 22 jan 17:49 bcm2710-rpi-zero-2-w.dtb
-rwxr-xr-x  1 root root  55K 22 jan 17:49 bcm2711-rpi-400.dtb
-rwxr-xr-x  1 root root  55K 22 jan 17:49 bcm2711-rpi-4-b.dtb
-rwxr-xr-x  1 root root  56K 22 jan 17:49 bcm2711-rpi-cm4.dtb
-rwxr-xr-x  1 root root  38K 22 jan 17:49 bcm2711-rpi-cm4-io.dtb
-rwxr-xr-x  1 root root  53K 22 jan 17:49 bcm2711-rpi-cm4s.dtb
-rwxr-xr-x  1 root root  80K 22 jan 17:49 bcm2712d0-rpi-5-b.dtb
-rwxr-xr-x  1 root root  80K 22 jan 17:49 bcm2712-rpi-500.dtb
-rwxr-xr-x  1 root root  80K 22 jan 17:49 bcm2712-rpi-5-b.dtb
-rwxr-xr-x  1 root root  80K 22 jan 17:49 bcm2712-rpi-cm5-cm4io.dtb
-rwxr-xr-x  1 root root  80K 22 jan 17:49 bcm2712-rpi-cm5-cm5io.dtb
-rwxr-xr-x  1 root root  52K 11 apr 15:15 bootcode.bin
-rwxr-xr-x  1 root root  687 14 apr 10:15 boot.scr
-rwxr-xr-x  1 root root  616 14 apr 10:42 boot.txt
-rwxr-xr-x  1 root root  126 14 apr 00:48 cmdline.txt
-rwxr-xr-x  1 root root   14 22 jan 17:49 config.txt
drwxr-xr-x 18 root root 4,0K  7 dec 18:48 dtbs
drwxr-xr-x 18 root root 4,0K  4 apr 00:08 dtbs-lts
-rwxr-xr-x  1 root root 3,2K 11 apr 15:15 fixup4cd.dat
-rwxr-xr-x  1 root root 5,4K 11 apr 15:15 fixup4.dat
-rwxr-xr-x  1 root root 8,3K 11 apr 15:15 fixup4db.dat
-rwxr-xr-x  1 root root 8,3K 11 apr 15:15 fixup4x.dat
-rwxr-xr-x  1 root root 3,2K 11 apr 15:15 fixup_cd.dat
-rwxr-xr-x  1 root root 7,2K 11 apr 15:15 fixup.dat
-rwxr-xr-x  1 root root  11K 11 apr 15:15 fixup_db.dat
-rwxr-xr-x  1 root root  11K 11 apr 15:15 fixup_x.dat
-rwxr-xr-x  1 root root  39M 15 feb 12:45 Image
-rwxr-xr-x  1 root root  15M 15 feb 12:45 Image.gz
-rwxr-xr-x  1 root root  87M 13 apr 22:13 initramfs-linux-fallback.img
-rwxr-xr-x  1 root root 7,5M 13 apr 22:05 initramfs-linux.img
-rwxr-xr-x  1 root root  87M 13 apr 22:04 initramfs-linux-lts-fallback.img
-rwxr-xr-x  1 root root 7,7M 13 apr 21:55 initramfs-linux-lts.img
-rwxr-xr-x  1 root root 7,5M 14 apr 10:41 initramfs-linux.uimg
-rwxr-xr-x  1 root root 666K 22 jan 17:49 kernel8.img
-rwxr-xr-x  1 root root  39M 15 feb 16:14 ltsImage
-rwxr-xr-x  1 root root  15M 15 feb 16:14 ltsImage.gz
-rwxr-xr-x  1 root root  239 22 jan 17:49 mkscr
-rwxr-xr-x  1 root root 796K 11 apr 15:15 start4cd.elf
-rwxr-xr-x  1 root root 3,6M 11 apr 15:15 start4db.elf
-rwxr-xr-x  1 root root 2,2M 11 apr 15:15 start4.elf
-rwxr-xr-x  1 root root 2,9M 11 apr 15:15 start4x.elf
-rwxr-xr-x  1 root root 796K 11 apr 15:15 start_cd.elf
-rwxr-xr-x  1 root root 4,7M 11 apr 15:15 start_db.elf
-rwxr-xr-x  1 root root 2,9M 11 apr 15:15 start.elf
-rwxr-xr-x  1 root root 3,6M 11 apr 15:15 start_x.elf
-rwxr-xr-x  1 root root  304  1 jan  2000 ubootefi.var

config.txt
Code: [Select]
enable_uart=1

boot.txt
Code: [Select]
# After modifying, run ./mkscr

# Set root partition to the second partition of boot device
part uuid ${devtype} ${devnum}:2 uuid

setenv bootargs console=tty1 root=PARTUUID=${uuid} rw rootwait smsc95xx.macaddr="${usbethaddr}"

if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /Image; then
  if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /dtbs/${fdtfile}; then
    if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /initramfs-linux.uimg; then
      booti ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
    else
      booti ${kernel_addr_r} - ${fdt_addr_r};
    fi;
  fi;
fi

cmdline.txt
Code: [Select]
console=tty1,115200 earlyprintk=serial,tty1,115200 root=/dev/mmcblk0p2 rw rootwait smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0

Re: [Solved] Custom installed ARMtix on RPi4. Stuck on U-boot.

Reply #1 –
This post is marked as Solved but I don't see how this is solved. I had problems with stock boot.txt so I replaced it with my own:
Code: [Select]
setenv bootargs root=[your root path] rw rootwait console=serial0,115200 console=tty1 fsck.repair=yes
load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /[Your image file]
load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /[Your initial ramdisk uimg]
booti ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr}

Remember to set image file path for first load and set correct root path in bootargs and generate new boot.scr with ./mkscr command.

Re: Custom installed ARMtix on RPi4. Stuck on U-boot.

Reply #2 –
You're right. it hasn't been solved. I changed the title accordingly. 
 
I tried your solution, but that didn't make any difference, 
apart from Working FDT set to 2eff2000.

Re: Custom installed ARMtix on RPi4. Stuck on U-boot.

Reply #3 –
What if you add `load {devtype} ${devnum}:${bootpart} ${fdt_addr_r} /path/to/dtb` before booti in boot.txt? I don't know how is fdt set without explicitly specifying this command
ARMtix
 
Artix forum uses a single cookie to remember youOK