public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Subodh Nijsure <nijsure.subodh@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: ecos-devel@sourceware.org
Subject: Re: Booting ELF image using redboot
Date: Fri, 24 Jul 2009 16:30:00 -0000	[thread overview]
Message-ID: <110c8b2e0907240930g3e4429aek690a32f7282a93ce@mail.gmail.com> (raw)
In-Reply-To: <4A69D00F.6000807@mlbassoc.com>

See my attempts below (still no joy, I am stumped appreciate help!)

On Fri, Jul 24, 2009 at 8:15 AM, Gary Thomas<gary@mlbassoc.com> wrote:
> Subodh Nijsure wrote:
>> I am new to using redboot and I need some help.
>>
>> This is x86 platform.
>>
>> On this platform I can boot the bzImage but not the ELF format linux image.
>>
>> Example if I have following boot script my board boots fine.
>>
>> load -v -r -m disk -b 0x200000 hda2:bzImage
>> exec -b 0x200000 -l 0x300000 -c "console=ttyS0,115200 ip=dhcp
>> root=/dev/nfs  (some env specific stuff) "
>>
>> However I can not get redboot to load the ELF image I see message (
>> Bootsector magic not found (0x8954 @ 0x002001fe)
>>
>> (Not this  vmlinux  was produced by build process that created bzImage
>> that works)
>>
>> load -v -r -m disk -b 0x200000 hda2:vmlinux
>> exec -b 0x200000 -l 0x300000 -c "console=ttyS0,115200 ip=dhcp
>> root=/dev/nfs  (some env specific stuff) "
>> Bootsector magic not found (0x8954 @ 0x002001fe)
>>
>> Reason I am trying to boot ELF image is I am trying to use wraplinux
>> utility to wrap kernel and initrd, wraplinux produce
>>
>> Would appreciate any pointers as to what parameters I need to fix for
>> load/exec when loading ELF file.
>
> Try leaving out the '-r' and '-b' options - ELF loading
> should not need them.

So I tried doing the following

load -v -m disk hda2:vmlinux
exec -c "console=ttyS0,115200 root=/dev/sda2 ip=dhcp platformid=0x500300"

I also tried to execute exec with that specified -l

load -v -m disk hda2:vmlinux
exec -l 0x500000 -c "console=ttyS0,115200 root=/dev/sda2 ip=dhcp
platformid=0x500300"

without any luck objdump for vmlinux shows the following: so I have
also tried executing
go 0x00100000 without any luck


vmlinux:     file format elf32-i386
vmlinux
architecture: i386, flags 0x00000112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x00100000

Program Header:
    LOAD off    0x00001000 vaddr 0xc0100000 paddr 0x00100000 align 2**12
         filesz 0x0036032c memsz 0x0036032c flags r-x
    LOAD off    0x00362000 vaddr 0xc0461000 paddr 0x00461000 align 2**12
         filesz 0x0007a086 memsz 0x000bc000 flags rwx
    NOTE off    0x002b4cd8 vaddr 0xc03b3cd8 paddr 0x003b3cd8 align 2**2
         filesz 0x00000024 memsz 0x00000024 flags ---




/Subodh

  reply	other threads:[~2009-07-24 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 15:04 Subodh Nijsure
2009-07-24 15:15 ` Gary Thomas
2009-07-24 16:30   ` Subodh Nijsure [this message]
2009-07-26 16:33     ` Weqaar Janjua
2009-07-27 15:20       ` Subodh Nijsure
2009-07-27 18:17         ` Gary Thomas
2009-07-27 22:55           ` Weqaar Janjua

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=110c8b2e0907240930g3e4429aek690a32f7282a93ce@mail.gmail.com \
    --to=nijsure.subodh@gmail.com \
    --cc=ecos-devel@sourceware.org \
    --cc=gary@mlbassoc.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).