From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chuck Meade Date: Tue, 24 Feb 2004 10:32:35 -0500 Subject: [U-Boot-Users] Problems with u-boot, PPChameleonEVB and MontaVistakernel In-Reply-To: Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Yes sorry, that is what I thought I saw. The load addr is OK in the pImage. I was thinking about the tftp load addr. Chuck > -----Original Message----- > From: mag at mag.sysgo.com [mailto:mag at mag.sysgo.com]On Behalf Of Marius > Groeger > Sent: Tuesday, February 24, 2004 10:22 AM > To: Andy Hawkins > Cc: 'Chuck Meade'; u-boot-users at lists.sourceforge.net > Subject: RE: [U-Boot-Users] Problems with u-boot, PPChameleonEVB and > MontaVistakernel > > > On Tue, 24 Feb 2004, Andy Hawkins wrote: > > > > You have a load address and entry point of 0x0. > > > You can't load and run Linux at 0x0. Try something more sensible > > > like 0x400000. > > > > The image that comes with the board (and boots fine) has the load and > > entry addresses both set to zero... > > Guys, don't confuse the load address of the pImage with the *download > address*, ie. the one used for tftp. Your setting of 0/0 for the load > address and entry point is correct. > > However, from your initial post I gathered that your MV kernel does > not have BSP support for your hardware. It is unlikely that a simple > adaption of the boot info structure will be sufficient. Check out the > relevant files in arch/ppc/{platforms,kernel} as well as the configure > options in arch/ppc/config.in and look for things specific for your > board. > > Regards, > Marius > > -- > Marius Groeger > Project Manager > > SYSGO Real-Time Solutions AG | Embedded and Real-Time Software > Am Pfaffenstein 14 > 55270 Klein-Winternheim, Germany > > Voice: +49-6136-9948-0 | FAX: +49-6136-9948-10 > www.sysgo.com | www.elinos.com | www.osek.de