Beagle build 69 does not boot

Bug #768783 reported by Zach Pfeffer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android
Fix Released
Medium
Zach Pfeffer

Bug Description

Starting at:
https://wiki.linaro.org/Resources/HowTo?action=show&redirect=HowTo

Selecting:

Obtaining and Deploying Linaro Images
->Daily Builds

Using this build:

https://android-build.linaro.org/builds/~linaro-android/beagle/
Build 69

And this linaro-image-tools

bzr branch lp:linaro-image-tools

I do:

$./linaro-image-tools/linaro-android-media-create
Traceback (most recent call last):
  File "./linaro-image-tools/linaro-android-media-create", line 31, in <module>
    from linaro_image_tools.media_create.hwpack import install_hwpacks
ImportError: No module named hwpack

commented out:

# from linaro_image_tools.media_create.hwpack import install_hwpacks

Traceback (most recent call last):
  File "./linaro-image-tools/linaro-android-media-create", line 38, in <module>
    from linaro_image_tools.media_create.populate_boot import populate_boot
ImportError: No module named populate_boot

commented out:

# from linaro_image_tools.media_create.populate_boot import populate_boot

./linaro-image-tools/linaro-android-media-create --mmc /dev/mmcblk0 --dev beagle --system system.tar.bz2 --userdata userdata.tar.bz2 --root boot.tar.bz2

$minicom -D /dev/ttyUSB1

Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from nand

U-Boot 2009.11-rc1-00601-g3aa4b51 (Jan 05 2010 - 20:56:38)

OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 256 MiB
*** Warning - bad CRC or NAND, using default environment

In: serial
Out: serial
Err: serial
Board revision C4
Die ID #716400240000000004039f220201b020
Hit any key to stop autoboot: 0
mmc1 is available
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
reading uImage

** Unable to read "uImage" from mmc 0:1 **
Booting from nand ...

NAND read: device 0 offset 0x280000, size 0x400000
 4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
OMAP3 beagleboard.org #

tar -jxvf boot.tar.bz2
cp boot/* /media/boot/

U-Boot 2011.03 (Apr 22 2011 - 00:51:33)

OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Beagle Rev C4
timed out in wait_for_pin: I2C_STAT=0
No EEPROM on expansion board
Die ID #716400240000000004039f220201b020
Hit any key to stop autoboot: 0
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
reading uImage

3582644 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
   Image Name: Linux-2.6.38.3-g775d71e
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 3582580 Bytes = 3.4 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

fatload mmc 0:1 0x82000000 uImage
fatload mmc 0:1 0x83000000 uInitrd
bootm 0x82000000 0x84000000

Zach Pfeffer (pfefferz)
Changed in linaro-android:
assignee: nobody → Zach Pfeffer (pfefferz)
importance: Undecided → Medium
status: New → Fix Released
milestone: none → 11.06
summary: - Build 69 does not boot on Beagle with bzr branch lp:linaro-image-tools
+ Beagle build 69 does not boot
Revision history for this message
Zach Pfeffer (pfefferz) wrote :
Changed in linaro-android:
status: Fix Released → Won't Fix
Revision history for this message
Alexander Sack (asac) wrote :

why is this set to wont fix? feels like its working now ;)

Revision history for this message
Zach Pfeffer (pfefferz) wrote :

We're not going to fix build 69 since we have a new build. Maybe I'm being too pedantic. I'll set it to fixed.

Changed in linaro-android:
status: Won't Fix → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.