From: Robert Hodaszi <mouse1@sch.bme.hu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Mips, U-Boot and ramdisk
Date: Mon, 22 Jun 2009 16:55:30 +0200 [thread overview]
Message-ID: <4A3F9B62.5070107@sch.bme.hu> (raw)
Hello,
Can anybody help me? I'm working on this for a few days...
I'm working on a custom developed board, with Au1200, and I'd like to
use the U-Boot as bootloader. I ported the U-Boot to my board, made a
Linux kernel image, and a ramdisk image.
To try out the configuration, I burn the U-Boot image into the flash (it
works well), and after I start the board, it download the kernel image
and the ramdisk image through TFTP. I'm using the following two commands:
tftp 81000000 uImage
tftp 81FFFFC0 uRamdisk
I set the bootargs variable to: root=\dev\ram (I used: set bootargs
root=/dev/ram)
But when I'm trying to start the Linux with the
bootm 81000000 81FFFFC0
the Linux can't find the ramdisk. It write out:
Initrd not found or empty - disabling initrd
But when I set its address into the bootargs (so the bootargs:
root=/dev/ram rd_start=0x82000000 rd_size=0x191160), it works well; it
successfully find the image, and can mount it.
How does the U-Boot pass the ramdisk information? It sets some kind of
environment variables in the bootm.c. But it doesn't work for me. Why?
(I could use the bootargs solution in this case, but I'm afraid, it
can't pass other arguments too, like ethernet address, etc.)
Thanks in advance!
Best regards,
Robert Hodaszi
next reply other threads:[~2009-06-22 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 14:55 Robert Hodaszi [this message]
2009-06-23 9:25 ` [U-Boot] Mips, U-Boot and ramdisk Detlev Zundel
2009-06-23 10:14 ` Robert Hodaszi
2009-06-23 9:54 ` Matthew Lear
2009-06-23 10:38 ` Robert Hodaszi
2009-06-23 12:45 ` Robert Hodaszi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A3F9B62.5070107@sch.bme.hu \
--to=mouse1@sch.bme.hu \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox