[okl4-developer] More NSLU2 debugging

[Frank Kaiser]

> -----Original Message-----
> From: developer-bounces at okl4.org [mailto:developer-bounces at okl4.org]
On Behalf
> Of Geoffrey Lee
> Sent: Wednesday, June 25, 2008 10:08 AM
> To: Joshua Root
> Cc: developer at okl4.org
> Subject: Re: [okl4-developer] More NSLU2 debugging
> 
> > I didn't think to check this because I specified "elf_entry =
> > 0x01d00000L" in the nslu2 class in machines.py. Does that not work?
> > Changing the bootloader default is possible, but it's a bit of a
pain.
> 
> I think we did away with that flag because most bootloaders would
allow
> you to hand control over to an arbitary location.  The physical memory
> is allocated out of the physical pool and the memory for kernel
> happens to be allocated first, so starts at the lower end of the
> physical range.
> 
> >
> > Cheers,
> > Josh
> >
> 
> 	-gl
> 
_______________________________________________
Hello

Just one comment: I have the impression that neither the setting
'elf_entry=...' nor 'elfloader=true' in machines.py are effective in the
build system of OKL4 v2.1, although they are still mentioned on
http://www.ertos.nicta.com.au/software/kenge/build-tools/devel/booting.p
ml. The latter one did not create an image with an included ELF loader
(my U-Boot version does not support loading of ELF imgaes), and a grep
thru all the scripts did not show any place where the setting maight be
considered. However, this is not a big problem, since I could use
'objcopy' to get a binary.

Regards
Frank