All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nethra <nethra_gmit@yahoo.co.in>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ramdisk problem (once again?)
Date: Tue, 19 Feb 2008 22:37:57 -0800 (PST)	[thread overview]
Message-ID: <15583256.post@talk.nabble.com> (raw)
In-Reply-To: <47B15940.8030901@gmail.com>



>Upload of kernel: tftp 0x260000 linux.uboot
>Upload of fs:        tftp 0x3a0000 root.uboot

>Environment:
>=> printenv
>bootcmd=run bootflash
>bootdelay=3
>baudrate=115200
>eth1addr=00:02:b3:02:02:02
>kernel_addr=50060000
>ramdisk_addr=501A0000
>bootflash=bootm $(kernel_addr)
>stdin=serial
>stdout=serial
>stderr=serial
>ethact=i82559#0
>ethaddr=00:11:22:33:44:55
>tftpdstp=10069
>bootargs=console=ttyS0,115200 root=/dev/ram0 rw irqpoll
>mtdparts=physmap-flash.0:256k(boot),128k(conf),1280k(linux),-(root)
>mem=128MB
>filesize=f4040
>fileaddr=3A0000
>netmask=255.255.0.0
>ipaddr=128.127.165.133
>serverip=128.127.50.94


Hi Miguel Angel,

In your case everything seems to be correct.....

but bootflash=bootm $(kernel_addr) should be 
     bootflash=bootm 0x260000 0x3a0000 i.e.,bootflash=bootm $(kernel_addr)
$(rams) for ramdisk booting.
    u can test with bootargs=/dev/ram itself.


Let me know output of it....

best regards,
Nethra
-- 
View this message in context: http://www.nabble.com/ramdisk-problem-%28once-again-%29-tp15428935p15583256.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

  parent reply	other threads:[~2008-02-20  6:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12  8:30 [U-Boot-Users] ramdisk problem (once again?) Miguel Angel Alvarez
2008-02-12 22:36 ` Wolfgang Denk
2008-02-12 22:39   ` michael
2008-02-12 23:07     ` Wolfgang Denk
2008-02-13 11:07       ` michael
2008-02-14 14:10   ` Miguel Angel Alvarez
2008-02-20  6:37 ` Nethra [this message]
2008-02-21 19:04   ` [U-Boot-Users] ramdisk problem (once again?) - Solved Miguel Angel Alvarez
2008-02-21 19:45     ` [U-Boot-Users] Taishan linker problem k b
2008-02-21 20:43       ` Wolfgang Denk

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=15583256.post@talk.nabble.com \
    --to=nethra_gmit@yahoo.co.in \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.