On 11.03.16 16:06, Freek de Kruijf wrote:
Op vrijdag 11 maart 2016 14:31:23 schreef Freek de Kruijf:
Op donderdag 10 maart 2016 09:22:39 schreef Guillaume Gardet:
Thanks for the fix! I accepted your SR to Base:System/u-boot. It is on the way to Factory.
Guillaume
I just tested JeOS 2016.03.09-Build5.1, but a reboot does not boot the system anymore, like before. It tries to boot via the network.
I now have a USB serial interface to connect to the GPIO pins 13 14 and 15. Will try this and hope to be able to give printenv.
I succeeded in getting the output of printenv after interrupting the U-boot process using Build389.1, which is working and the non-working 2016.03.09- Build5.1. It is an attachment, but I am not sure it will get through, so I also have it appended in this text.
--- wrong_image.txt 2016-03-11 15:36:31.473062507 +0100 +++ working_image.txt 2016-03-11 15:41:51.459094684 +0100 @@ -1 +1 @@ -U-Boot 2016.03-rc3 (Mar 07 2016 - 19:13:07 +0000) +U-Boot 2016.03-rc2 (Feb 26 2016 - 21:55:58 +0000) @@ -32 +31,0 @@ -boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootarm.efi; bootefi ${kernel_addr_r} @@ -34,0 +34 @@ +boot_prefixes=/ /boot/ @@ -46 +45,0 @@ -efi_dtb_prefixes=/ /dtb/ /dtb/current/ /boot/ /boot/dtb/ /boot/dtb/current/ @@ -54 +52,0 @@ -load_efi_dtb=load ${devtype} ${devnum}:2 ${fdt_addr_r} ${prefix}${fdtfile}; fdt addr ${fdt_addr_r} @@ -60 +58 @@ -scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev_for_efi; +scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done @@ -62 +59,0 @@ -scan_dev_for_efi=for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:2 ${prefix}${fdtfile}; then run load_efi_dtb; fi;done;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootarm.efi; then echo Found EFI removable media binary efi/boot/bootarm.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; boot_prefixes=/ /boot/
This is where it's broken. The patch I mentioned ealier in the thread fixed this hickup. To verify locally, try to run # setenv boot_prefixes / /boot/ # boot on your device. It should boot now even with the broken image. Once the updated u-boot is properly checked into Factory (submission is still pending), new images will get built that have this fixed. Sorry for the hickup. The patch that cause the breakage is part of a pretty major rework to enable grub2 and a standard EFI workflow on our arm images, so that during boot you can choose between different kernel flavors, edit kernel command lines etc. as soon as your board gets enabled. It shouldn't have broken the existing boot.scr path, but it did, sorry again :). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org