Bug 9015 - [beaglebone] u-boot can not autoboot
Summary: [beaglebone] u-boot can not autoboot
Status: VERIFIED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-yocto (show other bugs)
Version: 2.1
Hardware: BeagleBone arm
: Medium+ normal
Target Milestone: 2.1 M3
Assignee: Kevin Hao
QA Contact: Yi Zhao
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-01-29 09:23 UTC by Yi Zhao
Modified: 2016-03-17 03:09 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
u-boot-2016.1.log (6.77 KB, text/x-log)
2016-01-29 09:23 UTC, Yi Zhao 		no flags Details
u-boot-2015.7.log (4.95 KB, text/x-log)
2016-01-29 09:24 UTC, Yi Zhao 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2016-01-29 09:23:58 UTC 
Created attachment 2952 [details]
u-boot-2016.1.log

Image location: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M2.rc1/machines/beaglebone/

Git rev: master/3d2c0f5902cacf9d8544bf263b51ef0dd1a7218c

After u-boot updated to 2016.1, when system boot, it enters the interactive commandline and can not autoboot for beaglebone: 
#################
U-Boot SPL 2016.01 (Jan 26 2016 - 17:49:08)
Trying to boot from MMC
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img


U-Boot 2016.01 (Jan 26 2016 - 17:49:08 -0800)

       Watchdog enabled
I2C:   ready
DRAM:  512 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Error - No Valid Environment Area found
*** Warning - bad CRC, using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
=> 
##############

Check the u-boot var, there is no bootdelay in defatult setting:
###########
=> printenv bootdelay
## Error: "bootdelay" not defined
=> 
#############

The attachment is the full log for u-boot-2016.1
Comment 1 Yi Zhao 2016-01-29 09:24:51 UTC 
Created attachment 2953 [details]
u-boot-2015.7.log

The full log for u-boot-2015.7
Comment 2 Yi Zhao 2016-01-29 09:29:46 UTC 
(In reply to comment #0)
> Created attachment 2952 [details]
> u-boot-2016.1.log
> 
> Image location:
> http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M2.rc1/machines/
> beaglebone/
> 
> Git rev: master/3d2c0f5902cacf9d8544bf263b51ef0dd1a7218c
> 
> After u-boot updated to 2016.1, when system boot, it enters the interactive
> commandline and can not autoboot for beaglebone: 
> #################
> U-Boot SPL 2016.01 (Jan 26 2016 - 17:49:08)
> Trying to boot from MMC
> reading args
> spl_load_image_fat_os: error reading image args, err - -1
> reading u-boot.img
> reading u-boot.img
> 
> 
> U-Boot 2016.01 (Jan 26 2016 - 17:49:08 -0800)
> 
>        Watchdog enabled
> I2C:   ready
> DRAM:  512 MiB
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> *** Error - No Valid Environment Area found
> *** Warning - bad CRC, using default environment
> 
> Net:   <ethaddr> not set. Validating first E-fuse MAC
> cpsw, usb_ether
> => 
> ##############

In interactive command line, run bootcmd can boot without problems


> 
> Check the u-boot var, there is no bootdelay in defatult setting:
> ###########
> => printenv bootdelay
> ## Error: "bootdelay" not defined
> => 
> #############
> 
> The attachment is the full log for u-boot-2016.1
Comment 3 Erkka Kääriä 2016-02-18 14:39:11 UTC 
0
Comment 4 Erkka Kääriä 2016-02-18 14:47:40 UTC 
Ignore my previous reply

I bisected the u-boot codebase and found that the patch which broke beaglebone autobooting is http://git.denx.de/?p=u-boot.git;a=commit;h=755324c432f62306487786f89efce96398291a03

This was then fixed in http://git.denx.de/?p=u-boot.git;a=commit;h=7205442e621db54ea06c3bca2d793e1ae2214f9c

I backported this patch in http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=master-next&id=a46dc87c92b4cf3f56c17b6f1d6e53ed0583bc09
Comment 5 Kevin Hao 2016-02-23 05:30:36 UTC 
This has been fixed by Erkka Kääriä.
Comment 6 Yi Zhao 2016-03-17 03:09:03 UTC 
Verified with 2.1 M3 RC1
git rev: master/8debfea81e69d038bd2d56314b272cb74f5582ed