From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert P. J. Day Date: Sun, 4 Dec 2011 21:14:20 -0500 (EST) Subject: [U-Boot] having trouble booting a simple kernel on a TQM860 board In-Reply-To: <4ED95F4A.70003@freescale.com> References: <4ED95F4A.70003@freescale.com> 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 On Fri, 2 Dec 2011, Scott Wood wrote: > On 12/02/2011 05:19 PM, Robert P. J. Day wrote: > > and, at this point, i would think that all i need to do is: > > > > => bootm 400000 > > ## Booting image at 00400000 ... > > Image Name: Linux-2.6.37 > > Created: 2011-12-02 23:08:06 UTC > > Image Type: PowerPC Linux Kernel Image (gzip compressed) > > Data Size: 1301506 Bytes = 1.2 MB > > Load Address: 00000000 > > Entry Point: 00000000 > > Verifying Checksum ... OK > > Uncompressing Kernel Image ... OK > > You need to use a cuImage, just as you did with lite5200. i believe i've solved this issue, at least. i downloaded ELDK 4.2 and installed the ppc_8xx- toolchain. with that, i managed to compile u-boot 2010.12 and flashed it to my TQM860, reset and, lo and behold, i have a 2010.12 u-boot. so my u-boot issue seems to be resolved. > Or update U-Boot and pass a device tree. > > > and that's where it hangs. > > > > i have no idea if it's still booting properly but i've simply > > screwed up the serial port setting. > > > > does this set of steps look reasonable? the configuration, the > > building, the TFTP, the verification steps, the "bootm" command? this > > is what's printed when the board resets: > > > > U-Boot 0.4.0 (Apr 13 2004 - 15:01:22) > > > > CPU: XPC860xxZPnnD4 at 80 MHz: 16 kB I-Cache 8 kB D-Cache FEC > > present > > Board: TQM860LDB0A3-P80.208 > > DRAM: 16 MB > > FLASH: 8 MB > > In: serial > > Out: serial > > Err: serial > > Net: SCC ETHERNET [PRIME], FEC ETHERNET > > PCMCIA: No Card found > > > > am i just missing something obvious? what should i use for the > > kernel console setting? i'm open to suggestions. > > console=ttyCPM0 ok, i'm still having trouble getting a bootable kernel so here's what i did. using 2.6.37 version of kernel source, i followed your advice and first just configured for the 860 with: $ make ARCH=powerpc tqm8xx_defconfig then $ make ARCH=powerpc uImage which generated a uImage file. but as i understand it, i want a cuImage-format file as i used with my lite5200, so i edited the file arch/powerpc/boot/wrapper (as you suggested) and made the following change: case "$platform" in *-mpc866ads|*-mpc885ads|*-adder875*|*-ep88xc|*-tqm8xx) ^^^^^^^^^ added which now allows me to do the following: $ make ARCH=powerpc cuImage.tqm8xx and it's my understanding that this is the file i'll TFTP down to the TQM860 board and boot, correct? here's a look at that file: $ mkimage -l /var/lib/tftpboot/cuImage.tqm8xx Image Name: Linux-2.6.37 Created: Sun Dec 4 20:51:56 2011 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1258640 Bytes = 1229.14 kB = 1.20 MB Load Address: 0x00400000 Entry Point: 0x0040055C $ look reasonable? so i download to the board to address 200000, check it: => imi 200000 ## Checking Image at 00200000 ... Legacy image found Image Name: Linux-2.6.37 Created: 2011-12-05 1:51:56 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1258640 Bytes = 1.2 MiB Load Address: 00400000 Entry Point: 0040055c Verifying Checksum ... OK => but at this point, any attempt to "bootm 200000" gives me (as before): ## Booting kernel from Legacy Image at 00200000 ... Image Name: Linux-2.6.37 Created: 2011-12-05 1:51:56 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1258640 Bytes = 1.2 MiB Load Address: 00400000 Entry Point: 0040055c Verifying Checksum ... OK Uncompressing Kernel Image ... OK immediately followed by a long line of diamonds with question marks inside them. i would assume i've just screwed up the console setting, but i've tried various combinations of tty0, ttyS0 and ttyCPM0, with different baud rates. any hint as to what i should be looking at? i suspect i'm close, i just have this last issue to deal with. thanks. rday