reboot on PQ2FADS board.

2006-08-18 Thread Liu Dave-r63238
+daveliu=freescale.com at ozlabs.org [mailto:linuxppc-embedded-bounces+daveliu=freescale.com at ozlabs.org] On Behalf Of Zhimin (Jimmy) Liu Sent: Friday, August 18, 2006 1:00 AM To: linuxppc-embedded at ozlabs.org Subject: reboot on PQ2FADS board. Did

reboot on PQ2FADS board.

2006-08-17 Thread Zhimin (Jimmy) Liu
Did you sovlve the problem? I have same issue for the PQ2FADS board. jimmy -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060817/3eb9347a/attachment.htm

reboot on PQ2FADS board.

2006-07-20 Thread Lei Sun
Hi : The following is the version I am using, it's pretty much same as do_reset() code in u-boot -1.1.4 for m8260 target. However the machine just hangs. I wonder if there are any difference between Power on Reset and Hard reset? in my case maybe the machine did get reset, but the u-boot

reboot on PQ2FADS board.

2006-07-20 Thread Wolfgang Denk
In message f9a7e7a80607192046s3f17e8a5s4cfba43f1747e9ec at mail.gmail.com you wrote: m8260_restart(char * cmd) ... startaddr = 0x0440; /* this is taken from u-boot-1.1.4 */ This is a random address which happens to be not mapped in the specific board (MPC8260ADS.h). The

reboot on PQ2FADS board.

2006-07-20 Thread Liu Dave-r63238
This way maybe can not work. when the MMU turn off, the next instructions maybe can not be fetched if these instructions didn't exist cache. so it is possible these instruction can not executed. Trying to jump to some boot rom address is IMHO always a bad approach to reboot a system. You

reboot on PQ2FADS board.

2006-07-19 Thread Li Yang-r58472
-Original Message- From: linuxppc-embedded-bounces+leoli=freescale.com at ozlabs.org [mailto:linuxppc-embedded-bounces+leoli=freescale.com at ozlabs.org] On Behalf Of Lei Sun Sent: Tuesday, July 18, 2006 11:41 AM To: linuxppc-embedded at ozlabs.org Subject: reboot on PQ2FADS board

reboot on PQ2FADS board.

2006-07-19 Thread Wolfgang Denk
In message 4879B0C6C249214CBE7AB04453F84E4D050B0F at zch01exm20.fsl.freescale.net you wrote: command cause machine check and kernel ooops. The problem seems in the m8260_gorom in head.S. The restart() function in m8260_setup.c passed 2 parameters to that assembly code, r3 is the bd_info

reboot on PQ2FADS board.

2006-07-19 Thread Lei Sun
Hi : I tried your approach last ight, (in fact I copied part of the do_reboot() code from u-boot and put it in m8260_restart() function in the kernel). The only difference is the first line, volatile immap_t *immap = (immap_t *) IMAP_ADDR; in my case it is volatile immap_t * immap =

reboot on PQ2FADS board.

2006-07-19 Thread Mathieu Deschamps
Hi, On Wednesday 19 July 2006 16:12, Lei Sun wrote: Hi : I tried your approach last ight, (in fact I copied part of the do_reboot() code from u-boot and put it in m8260_restart() function in the kernel). The only difference is the first line, volatile immap_t *immap = (immap_t *)

reboot on PQ2FADS board.

2006-07-18 Thread Lei Sun
Hi: I have linux 2.4.30 runnning on this board, the reboot -f command cause machine check and kernel ooops. The problem seems in the m8260_gorom in head.S. The restart() function in m8260_setup.c passed 2 parameters to that assembly code, r3 is the bd_info , r4 is the warm start address, I