[Freedombox-discuss] Beaglebone Black failed to booting up by using u-boot (2016-01)

[Sunil Mohan Adapa]

On 02/16/2016 08:36 PM, Saúl Ibarra Corretgé wrote:
> On 02/02/2016 01:30 AM, tong hui wrote:
>> Today I just upgrade and flash my eMMC's Debian Jessie to latest 201601
>> from BBB official. This upgrade version updated u-boot to 2016-01 as
>> well. It could boot up eMMC Debian, but SD card Freedombox failed. It
>> stuck at "Starting Kernel..." from serial port watching.  
>>
>> However, I recreate the freedombox sdcard, it could boot up and finish
>> setup, but after it reboot, failed again. I believe it should be a bug. 
>>
>> And I still testing for sure.
>>
>> Following are the serial output:
>>
>> U-Boot SPL 2016.01-00001-g4eb802e (Jan 13 2016 - 11:14:31)
>> Trying to boot from MMC
>> bad magic
>>
>>
>> U-Boot 2016.01-00001-g4eb802e (Jan 13 2016 - 11:14:31 -0600), Build:
>> jenkins-github_Bootloader-Builder-313
>>
>>        Watchdog enabled
>> I2C:   ready
>> DRAM:  512 MiB
>> Reset Source: Global warm SW reset has occurred.
>> Reset Source: Power-on reset has occurred.
>> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
>> Using default environment
>>
>> Net:   <ethaddr> not set. Validating first E-fuse MAC
>> cpsw, usb_ether
>> Press SPACE to abort autoboot in 2 seconds
>> switch to partitions #0, OK
>> mmc0 is current device
>> Scanning mmc 0:1...
>> Found U-Boot script /boot.scr
>> 1577 bytes read in 17 ms (89.8 KiB/s)
>> ## Executing script at 80000000
>> 3452904 bytes read in 211 ms (15.6 MiB/s)
>> 31013 bytes read in 256 ms (118.2 KiB/s)
>> 13567447 bytes read in 792 ms (16.3 MiB/s)
>> Booting Debian 4.2.0-1-armmp from mmc 0:1...
>> Kernel image @ 0x82000000 [ 0x000000 - 0x34afe8 ]
>> ## Flattened Device Tree blob at 88000000
>>    Booting using the fdt blob at 0x88000000
>>    Loading Ramdisk to 8f30f000, end 8ffff5d7 ... OK
>>    Loading Device Tree to 8f304000, end 8f30e924 ... OK
>>
>> Starting kernel ...
>>
> 
> Did anyone manage to solve this? Thanks in advance.
> 

I just investigated a bit (without actually having a BBB to do
hands-on).  I have two possible workarounds:

1) Mount the SD card on a machine and rename away the boot.scr file.
Try to boot.

2) Press the S2 switch and reboot the BBB (switch must be pressed while
booting).  Try this also with 1).

Here is what I found:

- You are booting from on-board eMMC first.  There the u-boot version is
"U-Boot 2016.01-00001-g4eb802e (Jan 13 2016 - 11:14:31 -0600)".  This is
not be found on FreedomBox/Debian.  Pressing the S2 switch will change
the boot order and boot from MMC directly.

- This u-boot is trying to load boot script from the MMC (correctly).

- boot.scr file has been created by the flash-kernel script after
upgrade.  FreedomBox's usual way of booting is from uEnv.txt file which
is still there.  I don't see any problem with the boot.scr file but in
case this the problem, removing the file should make u-boot load the
uEnv.txt.

- I have noticed that after the package upgrade process, u-boot which on
SD card is intact.  So, pressing S2 switch to make it boot from here.

Let me know how it goes.  Further logs will be immensely helpful.

Issue tracker for this bug:
https://github.com/freedombox/freedom-maker/issues/49

-- 
Sunil

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/freedombox-discuss/attachments/20160216/6c476428/attachment.sig>