tiomap-dev team mailing list archive

[Launchpad Bug Tracker <640406@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package jasper-initramfs - 0.25

---------------
jasper-initramfs (0.25) maverick; urgency=low

  * make sure we use the right partition for booting when running from SD on
    OMAP4 blaze (LP: #640406)
 -- Oliver Grawert <ogra@xxxxxxxxxx>   Thu, 16 Sep 2010 18:27:07 +0200

** Changed in: jasper-initramfs (Ubuntu)
       Status: Confirmed => Fix Released

-- 
Flashing OMAP4 kernel uses the wrong partition on Blaze
https://bugs.launchpad.net/bugs/640406
You received this bug notification because you are a member of TI OMAP
Developers, which is a direct subscriber.

Status in “jasper-initramfs” package in Ubuntu: Fix Released

Bug description:
When flash_kernel runs on blaze, it flashes in /dev/mmcblk0p1 (as per flash_kernel.conf). however on blaze mmcblk0 is the device name for the eMMC, not the SD card.

also in the image, the initial boot.scr has mmcblk0 hard coded, so it needs to be documented that this must be changed when booted on blaze.

blaze and panda are different machines at kernel level. on blaze /proc/cpuinfo contains:L

$ cat /proc/cpuinfo 
Processor	: ARMv7 Processor rev 1 (v7l)
processor	: 0

<snip>

Hardware	: OMAP4430 4430SDP board
Revision	: 0010
Serial		: 0000000000000000