On 2022-10-11, Philip Rinn wrote: > OK, I used a custom bootstrap script now and that works:
For clarity, sounds like you used u-boot-menu (at my suggestion), which
does not use boot scripts...
> U-Boot 2022.10+dfsg-1 (Oct 04 2022 - 00:06:38 +0000) Allwinner Technology
>
> CPU: Allwinner A64 (SUN50I)
> Model: Olimex A64-Olinuxino-eMMC
> DRAM: 2 GiB
> Core: 74 devices, 20 uclasses, devicetree: separate
> WDT: Not starting watchdog@1c20ca0
> MMC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
> Loading Environment from FAT... Unable to use mmc 0:1...
> In: serial
> Out: serial
> Err: serial
> Net: eth0: ethernet@1c30000
> starting USB...
> Bus usb@1c1a000: USB EHCI 1.00
> Bus usb@1c1a400: USB OHCI 1.0
> Bus usb@1c1b000: USB EHCI 1.00
> Bus usb@1c1b400: USB OHCI 1.0
> scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
> scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
> scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
> scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
> scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot: 0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> Found /boot/extlinux/extlinux.conf
> Retrieving file: /boot/extlinux/extlinux.conf
> U-Boot menu
> 1: Debian GNU/Linux bookworm/sid 5.19.0-2-arm64
> 2: Debian GNU/Linux bookworm/sid 5.19.0-2-arm64 (rescue target)
> Enter choice: 1: Debian GNU/Linux bookworm/sid 5.19.0-2-arm64
> Retrieving file: /boot/initrd.img-5.19.0-2-arm64
> Retrieving file: /boot/vmlinuz-5.19.0-2-arm64
> append: root=/dev/mmcblk0p1 ro quiet
> Retrieving file:
> /usr/lib/linux-image-5.19.0-2-arm64/allwinner/sun50i-a64-olinuxino-emmc.dtb
> Moving Image from 0x40080000 to 0x40200000, end=42000000
> ## Flattened Device Tree blob at 4fa00000
> Booting using the fdt blob at 0x4fa00000
> Loading Ramdisk to 48196000, end 49ffffd7 ... OK
> Loading Device Tree to 000000004818b000, end 0000000048195370 ... OK
>
> Starting kernel ...
>
> [ 3.943010] sun50i-a64-pinctrl 1c20800.pinctrl: request() failed for pin 40
...
> [ 5.065265] sunxi-mmc 1c10000.mmc: Error applying setting, reverse things
> back
> [ 5.236700] sunxi-mmc 1c11000.mmc: data error, sending stop command
> [ 6.244813] sunxi-mmc 1c11000.mmc: send stop command failed
> [ 11.139614] lima 1c40000.gpu: error -ENODEV: dev_pm_opp_set_regulators: no
> regulator (mali) found
>
> Debian GNU/Linux bookworm/sid debian ttyS0
>
> debian login:
Ok, some success!
> I did use
>
> TARGET=/usr/lib/u-boot/a64-olinuxino-emmc/ u-boot-install-sunxi64 ${SDCARD}
Why did you have to specify TARGET? Was it not able to detect the
correct board? Or were you running u-boot-install-sunxi64 that from
another system?
That said, if u-boot-menu's generated /boot/extlinux/extlinux.conf is
correctly parsed by u-boot, I'm at a loss why flash-kernel's generated
boot script wouldn't work... (they both basically end load the
kernel/initrd/dtb into ram and call "booti $kernel_addr_r
$ramdisk_addr_r $fdt_addr_r"). I've seen this before, and don't recall
coming up with a resolution.
Wild guess; maybe the flash-kernel boot.scr gets the wrong console
settings (e.g. serial vs. hdmi or whatnot), while u-boot-menu just uses
the default console specified in the .dtb?
live well,
vagrant
signature.asc
Description: PGP signature
