public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix initrd length miscalculation in bootm command
Date: Mon, 19 Feb 2007 17:51:23 -0600	[thread overview]
Message-ID: <45DA37FB.3070804@freescale.com> (raw)
In-Reply-To: <37B7ABBF-458F-4B50-80D8-F3FE22A52EB2@kernel.crashing.org>

Kumar Gala wrote:

>> I've never heard of multi image before.  How do I make one?  The 
>> README doesn't explain it.
> 
> mkimage  -A ppc -O Linux -T multi -C gzip -n 'Linux Multiboot-Image' -e 
> 0 -a 0 -d vmlinux.gz:rootfs.ext2.gz:oftree.dtb  kern+fs+dtb.bin

I need some more help getting the multi-image to work.  I have the following files:

vmlinux.bin.gz (built myself)
rootfs.ext2.gz.uboot (from the BSP, because I don't know how to build a root 
file system.  I don't know what the ".uboot" is for.)
mpc8349emitx.dtb (built myself)

I create the multi image per you instructions, tftp them to $loadaddr (200000), 
and do "bootm $loadaddr".  I get this output:

bootm $loadaddr
## Booting image at 00200000 ...
    Image Name:   Linux Multiboot-Image
    Created:      2007-02-19  23:46:03 UTC
    Image Type:   PowerPC Linux Multi-File Image (gzip compressed)
    Data Size:    20407814 Bytes = 19.5 MB
    Load Address: 00000000
    Entry Point:  00000000
    Contents:
    Image 0:  1416615 Bytes =  1.4 MB
    Image 1: 18987128 Bytes = 18.1 MB
    Image 2:     4054 Bytes =  4 kB
    Verifying Checksum ... OK
    Uncompressing Multi-File Image ... OK


U-Boot 1.2.0-g2e892316-dirty (Feb  9 2007 - 15:56:37) MPC83XX


So the image appears to be okay, but it doesn't boot at all.  Is there something 
obvious I'm doing wrong, or will I have to debug this?

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  parent reply	other threads:[~2007-02-19 23:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05 19:39 [U-Boot-Users] [PATCH] Fix initrd length miscalculation in bootm command Timur Tabi
2007-02-06  0:43 ` Wolfgang Denk
2007-02-06 15:11   ` Timur Tabi
2007-02-06 17:07     ` Kumar Gala
2007-02-06 17:11       ` Timur Tabi
2007-02-06 17:14         ` Kumar Gala
2007-02-06 17:17           ` Timur Tabi
2007-02-19 23:51           ` Timur Tabi [this message]
2007-02-20 16:14             ` Kumar Gala
2007-02-20 16:36               ` Timur Tabi
2007-02-20 19:06                 ` Wolfgang Denk
2007-02-20 19:19                   ` Timur Tabi
2007-02-20 23:05                   ` Timur Tabi
2007-02-26 13:10                     ` Wolfgang Denk
2007-02-26 16:15                       ` Timur Tabi
2007-02-27 16:48                       ` Timur Tabi
2007-02-27 20:55                         ` Wolfgang Denk
2007-02-27 22:13                           ` Timur Tabi
2007-03-16 21:49                             ` Timur Tabi
2007-03-23 22:44                               ` Johns Daniel
2007-03-27 16:25                                 ` Johns Daniel
2007-03-27 16:30                                   ` Timur Tabi

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=45DA37FB.3070804@freescale.com \
    --to=timur@freescale.com \
    --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