>> Can you paste the whole log from the u-boot prompt?
>
> In the previous run the ramdisk image was corrupted because the single
> image was loaded at 0x80. But the boot message showed that the
> initrd image was at 0x0066c000-0x009ae825. So it was over the 8MB
> area.
>
> However after the lo
>> I have a large ramdisk image. The size of the image itself (i.e. the
>> *.gz) is about 4MB. When the ramdisk was being decompressed
>
> Did you try to change link_address on the file, arch/powerpc/boot/wrapper?
No. I don't have to. Right? The link_address is still 0x40.
> Did you try boot
>> > > A follow up question. With this method, the total image size
>> > > (uncompressed) is limited to the 4MB (the link address of
>> the boot
>> > > wrapper)?
>> >
>> > No.
>>
>> Yes, unless you change the link address, or provide a
>> vmlinux_alloc callback (which currently only happens on true
>> I have a cuImage kernel in order to support legacy u-boot and a
>> ramdisk image. Kernel boots fine if these two images are separate and
>> "bootm $kernel $ramdisk" is used. But I can not make it to work using
>> a single multi image that contains the kernel and ramdisk images. Is
>> it even tec
> Try the following steps:
> --
> 1. cp arch/powerpc/boot/ramdisk.image.gz
> 2. make cuImage.initrd.
>
> You can get one Image, cuImage.initrd., including kernel and
> ramdisk.
Cool! Thanks a lot, Tiejun.
-Shawn.
___
U-Boot mailing list
U-Boot@lis
Hi,
I have a cuImage kernel in order to support legacy u-boot and a
ramdisk image. Kernel boots fine if these two images are separate and
"bootm $kernel $ramdisk" is used. But I can not make it to work using
a single multi image that contains the kernel and ramdisk images. Is
it even technically p
>> SPI flash seems supported in u-boot after searching it in the mailing
>> list. But can u-boot boot from spi flash?
>
> it completely depends on your processor. but you never said what
> processor you're actually using.
It's a LPC3131 (ARM926EJ-S) based.
Thanks,
-Shawn.
___
Hi,
SPI flash seems supported in u-boot after searching it in the mailing
list. But can u-boot boot from spi flash?
Thanks,
-Shawn.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
>> However my concern is specific to the powerpc arch. If I understand
>> correctly, the powerpc arch expects a bootloader provide a DTS file.
>
> Not if you use a cuImage as Timur suggested.
Wolfgan & Timur, thanks for the comments.
-Shawn.
___
U-Boot
On Thu, May 13, 2010 at 7:47 AM, Timur Tabi wrote:
> The only way to find out for sure is to test it. You'll probably need
> to enable cuImage support in the kernel, at the very least. No one
> keeps track of whether newer kernels work with older U-Boots, so
> there's no way to know in advance w
Hi,
Can an old u-boot (e.g. 1.1.2) boot a latest powerpc based kernel
(e.g. 2.6.33)? I noticed that the bd_info in the latest u-boot is
different from the one in 1.1.2. The custom board with u-boot 1.1.2
passed only the first 6 parameters to a 2.4 kernel shown as below.
typedef struct bd_info {
/
Before starting the project I'd like to have some advices from the community
about the feasibility of porting U-Boot/ucLinux to a cortex-m3 based SoC
with limited resources (up to 512K flash, up to 64K SRAM). I limit my
questions to U-Boot only and will post similar ones to ucLinux mailing-list.
Bu
12 matches
Mail list logo
