linaro-release team mailing list archive

[Anmar Oueja <anmar.oueja@xxxxxxxxxx>]

Mattias:  The plan is to avoid multiple HWPacks of course. But we won't
know until we get the boards in our hands, which hasn't happened yet.

-- 
You received this bug notification because you are a member of Linaro
Release Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/829220

Title:
  linaro-media-create fails for snowball_emmc

Status in Linaro Image Tools:
  Fix Committed
Status in Linaro ST-Ericsson Landing Team Project:
  In Progress

Bug description:
  Using the following command to create a Snowball emmc image fails with
  current (updated on 18th of August) l-m-c:

  linaro-media-create --image_file customSnowballImage.img --dev
  snowball_emmc --rootfs ext3 --hwpack hwpack_linaro-lt-
  snowball_20110818-0_armel_supported.tar.gz --binary
  nano-n-tar-20110818-1.tar.gz

  The bottom of the trace is:

    File "/work/snowball/linaro/leb/linaro-image-tools/linaro_image_tools/media_create/boards.py", line 835, in get_file_info
      size = os.path.getsize(filename)
    File "/usr/lib/python2.6/genericpath.py", line 49, in getsize
      return os.stat(filename).st_size
  OSError: [Errno 2] No such file or directory: '/tmp/tmpmr5VH2/binary/boot/u-boot.bin'

  which would suggest that the u-boot.bin from the u-boot package is not
  installed correctly. And indeed, looking at the u-boot package it
  installs u-boot.bin to /usr/lib/u-boot/u8500_snowball and doesn't
  contain eg. linking to /boot, where the startupfiles package installs
  its binaries and the configuration that refers to u-boot.bin (and
  which l-m-c reads when creating the emmc image).

  So it seems that either startupfiles should have a startfiles.cfg that
  points to the correct u-boot location or the u-boot package should
  install (or link) the u-boot.bin to /boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-image-tools/+bug/829220/+subscriptions