I saw this bug and able to duplicate on another i.Mx51 design, however it seems
to be fix by my patch attached.
dunno if it's still helpful. or someone can test the patch as well.
** Patch added: fix_fail_to_read_mmc.patch
wont happen for lucid or other older releases...
** Changed in: uboot-imx (Ubuntu)
Status: Confirmed = Won't Fix
--
lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
https://bugs.launchpad.net/bugs/506761
You received this bug notification because you are a member of Ubuntu
marking this back down to medium since it no longer blocks an essential
spec. We can revisit the importance at a later date if it becomes
essential again.
** Changed in: uboot-imx (Ubuntu Lucid)
Importance: Critical = Medium
** Changed in: uboot-imx (Ubuntu)
Importance: Critical = Medium
** Changed in: uboot-imx (Ubuntu Lucid)
Milestone: lucid-alpha-3 = None
--
lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
https://bugs.launchpad.net/bugs/506761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
we are going for redboot for imx ... until all bugs are fixed for uboot.
** Changed in: uboot-imx (Ubuntu Lucid)
Status: Confirmed = Won't Fix
** Changed in: uboot-imx (Ubuntu)
Milestone: lucid-alpha-3 = later
--
lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
** Changed in: uboot-imx (Ubuntu Lucid)
Status: Won't Fix = Triaged
** Changed in: uboot-imx (Ubuntu Lucid)
Status: Triaged = Confirmed
** Changed in: uboot-imx (Ubuntu Lucid)
Importance: Undecided = Critical
--
lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
** Changed in: uboot-imx (Ubuntu Lucid)
Milestone: None = lucid-alpha-3
--
lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
https://bugs.launchpad.net/bugs/506761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Oliver found that this is a regression over the 2009.01 code we had
before.
From checking the differences it seems unlikely that its in actual fat
or fdos code; rather in mmc code.
I also get hangs when loading a larger chunk of blocks from SD cards
using mmc read; so we should investigate in
even though initramfs and kernel load now, we still can not load
boot.scr files which is essential for parsing the kernel cmdline options
on SD boots.
--
lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
https://bugs.launchpad.net/bugs/506761
You received this bug notification because
we seemed to work around this issue by using bigger fat partitions.
setting lucid target to wont fix for now as this doesnt block release
** Changed in: uboot-imx (Ubuntu Lucid)
Status: Confirmed = Won't Fix
** Changed in: uboot-imx (Ubuntu)
Importance: Undecided = Medium
--
lucid
Thanks Zhang, sadly thats not the way it can work in ubuntu, we build a
package of the kernel (natively on an armel machine) which then puts out
a vmlinuz file to be used with the various supported bootloaders
(redboot/uboot). for creating a bootloader specific variant of the
kernel image we need
Since we use LTIB for building (do mkimage operation), all documents you got
did not mention it. Sorry for inconvencience.
In FSL document for android platform, the following information is mentioned:
$ cd myandroid/kernel_imx/arch/arm/boot
$
We don't have any issue creating uImages; we build zImages because they
can be easily be converted to uImage if needs be or used as is; the
issue seems to be with the filesystem code in uboot or with the script
creating the partition table + filesystem.
--
lucid uboot hangs on fatload uImage on
wow, thanks zhang, another issue we have is that we dont know where
exactly to load an uinitrd to, that isnt documented either, would you
know what values to use here ?
--
lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
https://bugs.launchpad.net/bugs/506761
You received this bug
In my own experiments, I had success using commands like these:
ext2load mmc 0:2 0x90007fc0 uImage
ext2load mmc 0:2 0x907fffc0 initrd.uImg
[...]
bootm 0x90007fc0 0x907fffc0
The choice of 0x907fffc0 was arbitrary, but seemed to work for me
(assuming the kernel zImage is 8MB of course)
--
lucid
unmilestoning since the latest script code i committed makes this work
well.
** Changed in: uboot-imx (Ubuntu Lucid)
Importance: Critical = Undecided
** Changed in: uboot-imx (Ubuntu Lucid)
Milestone: lucid-alpha-3 = None
--
lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
blocks essential spec:
+
https://blueprints.launchpad.net/ubuntu/+spec/mobile-lucid-imx51-debian-cd-to-uboot
** Changed in: uboot-imx (Ubuntu Lucid)
Status: Incomplete = Confirmed
** Changed in: uboot-imx (Ubuntu Lucid)
Milestone: None = lucid-alpha-3
** Changed in: uboot-imx
i can get a working image it seems using the following steps:
1. get a current redboot lucid image; put that on the sd card
2. get the current uboot.bin from archive
3. sudo dd conv=notrunc if=uboot-imx51_to3.bin of=/dev/mmcblk0 bs=512
skip=1 seek=1
4. copy the uImage produced by our
using casper vmlinuz from the same image:
mkimage -A arm -O linux -T kernel -C none -a 0x90008000 -e 0x90008000 -n
LinuxRocks -d /media/4B4C-AB5E/casper/vmlinuz /media/4*/uimage1
-
BBG U-Boot run bootargs_base
BBG U-Boot mmcinfo
Device: FSL_ESDHC
Manufacturer ID: 3
OEM: 5344
Name: SD04G
Tran
so ... seems pretty obvious the script messes something up with how the
image is produced.
--
lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
https://bugs.launchpad.net/bugs/506761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
ok, i committed a few changes to the script branch. seems to work now
with:
./uboot-image-script ../out.img ../data/vmlinuz-2.6.31-601-imx51 ../data
/uboot-imx51_to3.bin 240M
somewhat the trick was to increase boot partition size to 200M ... i
will see if a lower size really is broken.
--
commands to boot that were:
mmcinfo
fatload mmc 0:2 0x9080 /uimage1
bootm 0x9080
--
lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
https://bugs.launchpad.net/bugs/506761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
To build uImage, can change build target from zImage to uImage. For example,
make ARCH=arm
CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-
uImage
You can copy mkimage to /usr/bin/mkimage
--
lucid uboot hangs on fatload
23 matches
Mail list logo
