RE: TUSL2-C almost work.....

[Yap Ee Huey]

Hi,

I thought zkernel_start could be the reason, but not :

---------------------------------------------------------------------------
Welcome to elfboot, the open sourced starter.
January 2002, Eric Biederman.
Version 1.2
  203:init_bytes() - zkernel_start:0xfffc0000  zkernel_mask:0x0000007f
Searching for 16 byte tags
   64:rom_read_bytes() - overflowed source buffer. max_block = 3
init_bytes found 0 tags
Found ELF candiate at offset 0
Loading Etherboot version: 5.1.8
Dropping non PT_LOAD segment
New segment addr 0x20000 size 0x12e0f offset 0xb0 filesize 0x3f5d
(cleaned up) New segment addr 0x20000 size 0x12e0f offset 0xb0 filesize 
0x3f5d
Loading Segment: addr: 0x000000000ff7ec68 memsz: 0x0000000000012e0f filesz: 
0x0000000000003f5d
Clearing Segment: addr: 0x000000000ff82bc5 memsz: 0x000000000000eeb2
Jumping to boot code at 0x20000

(Restarted)
LinuxBIOS-1.0.0 Tue May 13 11:51:30 EDT 2003 starting...
Ram1
Ram2
.................

---------------------------------------------------------------------------

Still looping............

My kernel was built by :
mkelfImage --command-line="root=/dev/hda5 console=ttyS0,19200"
--kernel vmlinux -o vmlinux..elf

But the ELF image cannot be tagged. (invalid linux kernel)
Also, the tagged bzImage cannot be made ELF. (Not an linux kernel at line 
73)

Could it be a problem ? I should have a tagged ELF according to the 
Documentation.

Thanks a lot.
regards,
eehuey
> From: [e-mail]
> To: [e-mail], [e-mail]
> CC: [e-mail]
> Subject: RE: TUSL2-C almost work.....
> Date: Thu, 15 May 2003 15:28:14 +0900
> > Welcome to elfboot, the open sourced starter.
> > January 2002, Eric Biederman.
> > Version 1.2
> >    203:init_bytes() - zkernel_start:0xfff00000
> > zkernel_mask:0x0000ffff
> > Searching for 16 byte tags
> >     64:rom_read_bytes() - overflowed source buffer. max_block = 15
> > init_bytes found 0 tags
> > Found ELF candiate at offset 0
> > Loading Etherboot version: 5.1.8
> > Dropping non PT_LOAD segment
> > New segment addr 0x20000 size 0xeee0 offset 0xb0 filesize 0x617c
> > (cleaned up) New segment addr 0x20000 size 0xeee0 offset 0xb0
> > filesize
> > 0x617c
> > Loading Segment: addr: 0x000000000ff7ece8 memsz:
> > 0x000000000000eee0 filesz:
> > 0x000000000000617c
> > Clearing Segment: addr: 0x000000000ff84e64 memsz: 0x0000000000008d64
> > Jumping to boot code at 0x20000
> >
> > Then it restarts.
>
> It seems like you should specify ZKERNEL_START correctly. If you have 256KB
> flash part, ZKERNEL_START should be 0xfffc0000.
>
> Heechul.

_________________________________________________________________
Download the latest MSN Messenger http://messenger.msn.com.my

TUSL2-C almost work.....

[Peter Stuge]

On Thu, May 15, 2003 at 08:31:45AM +0000, Yap Ee Huey wrote:
> I thought zkernel_start could be the reason, but not :

[..snip..]
> My kernel was built by :
> mkelfImage --command-line="root=/dev/hda5 console=ttyS0,19200"
> --kernel vmlinux -o vmlinux..elf
>
> But the ELF image cannot be tagged. (invalid linux kernel)
> Also, the tagged bzImage cannot be made ELF. (Not an linux kernel at line 
> 73)
>
> Could it be a problem ? I should have a tagged ELF according to the 
> Documentation.

Try getting a fresh version of mkelfimage. You should be able to run
mkelfimage (note small i in newer versions) on bzImage without problems..

//Peter