From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert P. J. Day Date: Mon, 5 Dec 2011 07:05:54 -0500 (EST) Subject: [U-Boot] having trouble booting a simple kernel on a TQM860 board In-Reply-To: <20111205100903.2E06413BE0E6@gemini.denx.de> References: <4ED95F4A.70003@freescale.com> <20111205100903.2E06413BE0E6@gemini.denx.de> 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 Mon, 5 Dec 2011, Wolfgang Denk wrote: > Dear Robert, > > In message you wrote: > > > > 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. > > You update U-Boot, but to a version 4 releases old. Why not to > current code? > > > 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 > > No. Now you don't need a cuImage nay more. Just use the DT as I > showed you in the builkd and boot log I sent before. for the sake of clarification, you write that i don't *need* cuImages anymore, but that's not the same as saying that i *must* move to using device trees. in fact, a cuImage file still works just fine for my lite5200 boards, so obviously the version of u-boot that i've flashed to my TQM boards can still handle that format. so while it's probably a good idea to move to the device tree recipe, that still doesn't explain why i can't use a cuImage file for my tqm boards. so i'll test the device tree process later today, but i'm still curious as to why a cuImage format file still fails in this case when it works just fine for the other boards. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================