From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Date: Wed, 20 Apr 2005 17:35:21 -0600 Subject: [U-Boot-Users] Cannot boot from a uImage on the lite5200 In-Reply-To: <20050420201516.3D55DC1510@atlas.denx.de> References: <528646bc0504201254fade191@mail.gmail.com> <20050420201516.3D55DC1510@atlas.denx.de> Message-ID: <528646bc050420163579a4fefd@mail.gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 4/20/05, Wolfgang Denk wrote: > In message <528646bc0504201254fade191@mail.gmail.com> you wrote: > > > > What specifically needs to be done to configure a kernel for use with > > u-boot? From the documentation I could only find references to using > > mkimage to prepare an image (which I've done). > > You must use the raw kernel image, without the kernel bootstrap > stuff. And you must make sure to pass the parameters correctly > (struct bd_info). See also the FAQ at > http://www.denx.de/twiki/bin/view/DULG/LinuxHangsAfterUncompressingKernel Do you mean the bootstrap stuff that's wrapped around a vmlinux.gz to create a zImage, or do you mean arch/ppc/kernel/setup.c and others? I'm building the uImage directly from the vmlinux.gz, so I don't have any of the zImage stuff. > > > but it made no difference. I could not find anything in the kernel > > config file related to u-boot for this port. The file > > This is probably the problem. > > > Documentation/powerpc/mpc52xx.txt in the kernel tree states that a > > 'make uImage' should build an image bootable by u-boot. (The Makefile > > simply calls mkimage for the uImage target) > > This is probably not enough. At least you must make sure not to > include any bootstrap stuff. I've got weird stuff happening here now. With the same uImage I've now seen three different behavious: 1. (most frequently) get initial setup banners ("id arch", et all). Crashes w/ board reset before kernel version banner 2. locks up before printing anything 3. kernel boots fine. It's looking more like I've got a problem with the hardware configuration on the Linux side now. Time to step through init code.... g.