From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail19e.g19.rapidsite.net (mail19e.g19.rapidsite.net [204.202.242.20]) by ozlabs.org (Postfix) with SMTP id F38A5DDECB for ; Tue, 23 Jan 2007 23:49:41 +1100 (EST) Received: from mx86.stngva01.us.mxservers.net (198.173.112.3) by mail19e.g19.rapidsite.net (RS ver 1.0.95vs) with SMTP id 3-0156926578 for ; Tue, 23 Jan 2007 07:49:38 -0500 (EST) From: "Russell McGuire" To: Subject: MPC8360E Linux and 2.6.19.2 Date: Tue, 23 Jan 2007 04:49:25 -0800 Message-ID: <000301c73eec$ea489de0$6405a8c0@absolut> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01C73EA9.DC255DE0" List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0004_01C73EA9.DC255DE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit All, Trying to boot up / debug my board with a Rev 1.2 MPC8360E. After the kernel launches from U-boot I receive no serial debug, and the system hangs. I am running U-boot 1.1.6. Dirty , I have walked through the DTS/blob file, after U-boot modifies it, , and can clearly see that the /chosen node, etc.. is getting entered. My original DTS file already has all of the clock speeds entered . I have limited debug ability via some GPIO leds on our board, I can see that the kernel starts to run and at least gets to the point where it clears all the BATs , at which point I lose access to the IO space and can no longer write out to the debug lights. Unfortunately I do not have access to a COP debugger at this point. It doesn't seem to get to the platform files, or at least I can get the GPIO access inside the IMMR space to work correctly. Does anyone have any suggestion per software only debug method that might be enabled? Or a way to temporarily hack the early serial output so I can see what is going on? -Russ ------=_NextPart_000_0004_01C73EA9.DC255DE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,

 

Trying to boot up / debug my board with a Rev 1.2 = MPC8360E.

After the kernel launches from U-boot I receive no = serial debug, and the system hangs.

 

I am running U-boot 1.1.6. Dirty <which does = contains support for the 8360>,

 

I have walked through the DTS/blob file, after U-boot modifies it, <I turned on all the debug info>, and can clearly see = that the /chosen node, etc.. is getting entered. My original DTS file already = has all of the clock speeds entered <modeled after the MPC8360xx.dts file = that was already in the DENX-2.6.19.2 kernel = release>.

 

I have limited debug ability via some GPIO leds on = our board, I can see that the kernel starts to run and at least gets to the = point where it clears all the BATs <powerpc/boot/head_32.S and = setup_32.c>, at which point I lose access to the IO space and can no longer write out to = the debug lights. Unfortunately I do not have access to a COP debugger at = this point. It doesn’t seem to get to the platform files, or at least I = can get the GPIO access inside the IMMR space to work = correctly.

 

Does anyone have any suggestion per software only = debug method that might be enabled? Or a way to temporarily hack the early = serial output so I can see what is going on?

-Russ

 

------=_NextPart_000_0004_01C73EA9.DC255DE0--