Hello, Jonathan! Copying the provided u-boot.bin worked :)
Yes, the issue just affects USB DRIVE. Never touched config.txt. The procedures were: dd if=minirootfs61.fs of=(USB drive or sd-card ) bs=1M If I use sd-card, then I make sure that USB drive is not bootable and is empty and use both. If USB Drive, just itself. Thank you so much! 2017-07-31 21:17 GMT-03:00 Jonathan Gray <[email protected]>: > On Mon, Jul 31, 2017 at 11:15:52PM +0000, R0me0 *** wrote: > > I wrote minirootfs as usual directly to usb flash drive > > > > minirootfs61.fs 31-Jul-2017 03:11 22020096 > > > > > > > > U-Boot> boot > > Card did not respond to voltage select! > > mmc_init: -95, time 24 > > > > USB device 0: > > Device 0: Vendor: Kingston Rev: 1.00 Prod: DataTraveler 2.0 > > Type: Removable Hard Disk > > Capacity: 14762.4 MB = 14.4 GB (30233588 x 512) > > ... is now current device > > Scanning usb 0:1... > > Found EFI removable media binary efi/boot/bootaa64.efi > > reading efi/boot/bootaa64.efi > > 75732 bytes read in 75 ms (985.4 KiB/s) > > ## Starting EFI application at 01000000 ... > > Card did not respond to voltage select! > > mmc_init: -95, time 24 > > Found 0 disks > > BS->LocateHandle() returns 0 > > "Synchronous Abort" handler, esr 0x02000000 > > ELR: 39b3ecfc > > LR: 39b421ec > > x0 : 0000000000000000 x1 : 000000003afec000 > > x2 : 0000000000000002 x3 : 000000000000003f > > x4 : 0000000000000010 x5 : 0000000000000000 > > x6 : 000000003af96558 x7 : 0000000039b3efa8 > > x8 : 0000000039b4c8ac x9 : 0000000039b3e39c > > x10: 000000003ab4fa70 x11: 000000003ab4faf0 > > x12: 000000003ab4fbc0 x13: 0000000039b4d850 > > x14: 000000003ab4fd6c x15: 00000000ffffffff > > x16: 0000000000004110 x17: ad7bd9a555f85ec4 > > x18: 0000000000000000 x19: 0000000039b4db12 > > x20: 0000000039b4c920 x21: 0000000000000001 > > x22: 0000000039a3d030 x23: 0000000039b4cb00 > > x24: 0000000039b4c920 x25: 0000000000000200 > > x26: 000000003afa76b0 x27: 0000000039b3e148 > > x28: 0000000000000000 x29: 000000003ab4fcd0 > > > > Resetting CPU ... > > > > resetting ... > > That is with only a USB drive? You've previously blown the > fuse by setting the config.txt value and no SD card is present? > > Try with a newer U-Boot > http://jsg.id.au/openbsd/u-boot.bin > SHA256 (u-boot.bin) = 342af5b0331c502a0b1c64a96b2b7f > c915b516567cc3bd293a5078ea493a6e49 > > Mount the msdos fs /dev/sdNi and copy u-boot.bin over the existing one. > > The U-Boot build is based on the latest development version and > in particular includes: > > commit 70bfcdc6bb6f969babd69efc49e1dc7a1faeca54 > Author: [email protected] <[email protected]> > Date: Tue Jun 20 19:10:27 2017 +0000 > > efi_loader: disk: iterate only over valid block devices > > The efi_loader currently stops iterating over the available > block devices stopping at the first device that fails. > This may imply that no block device is found. > > With the patch efi_loader only iterates over valid devices. > ... >
