From: Prakash kanthi <pkanthi@yahoo.com>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: After Uncompresseing Linux..., what's next
Date: Fri, 20 Dec 2002 08:32:38 -0800 (PST) [thread overview]
Message-ID: <20021220163238.45233.qmail@web41215.mail.yahoo.com> (raw)
In-Reply-To: <20021220161436.81737.qmail@web41212.mail.yahoo.com>
I found the correct exception guys. It means
Privileged Instruction Exception.
--- Prakash kanthi <pkanthi@yahoo.com> wrote:
>
> Folks,
>
> I just wanted to provide more info on my env. I have
> PPC405 based board with no network support forcing
> me
> to use zImage.initrd.elf.
>
> Can you suggest more on my problem described below?
> I
> saw the memory values at 0x00000000 onwards after
> uncompressing linux and they have changed. But when
> the control jumps to 0x0, my board hangs. I see that
> ESR is showing a value of 0x80000000, meaning either
> illegal instruction or Machine Check.
>
> Can you tell what's going on? What happens next
> after
> uncompressing? I am thinking it executes
> start_kernel
> function which calls lock_kernel. Let me know if i
> am
> wrong.
>
> thanks,
> Prakash
>
>
>
>
> --- James Don <JDon@spacebridge.com> wrote:
> > I just went thru this myself ... ;-)
> >
> > 1.) Get a BDM/JTAG tool look halt the processor
> > after you see " Now booting
> > the kernel" and look for valid asm at 0x0 ... make
> > sure it mathes your
> > start.s file ...
> >
> > 2.) Veryfy you have your mem map from ppcboot
> > matching requirements for the
> > kernel i.e ram (physical=0x0, virtual=0xc0000000)
> > and immr (phys 0xff000000
> > virtual 0xff000000) ... I had my immr in ppc boot
> at
> > 0x02200000 this screwed
> > me for quite a while ... otherwise you have no
> > printk ... the memory map is
> > very important not to screw with some things
> depend
> > on it (unless your
> > careful) ...
> >
> > 3.) verify you SMC1 (uart) is getting proper
> > clocking config ... i.e
> > bus->brg1 and brg1 is 16 times baud rate ...
> > otherwise you have no printk
> >
> > 4.) and always always keep in mind your RAM refesh
> > could be wrong ...
> > everyone will tell you this even when it has
> nothing
> > to do with your problem
> > ... try not to ignore them if you are still stuck
> > ;-) But verifying step 1
> > should prove your ok ...
> >
> > Best of luck,
> > Jim
> >
> >
> > -----Original Message-----
> > From: Prakash kanthi [mailto:pkanthi@yahoo.com]
> > Sent: Wednesday, December 18, 2002 7:14 PM
> > To: LinuxPPC
> > Subject: After Uncompresseing Linux..., what's
> next
> >
> >
> > Hi there,
> >
> > I was trying to load linuxppc_2_4_devel onto my
> > board.
> > It goes through the board info read, UART init and
> > Uncompressing the linux kernel. But after that, i
> do
> > not see any messages and board hangs.
> >
> > Here is the UART output:
> > ------------------------------------
> > OS Booting...
> >
> > loaded at: 00400000 0060D1CC
> > board data at: 00000030 00000044
> > relocated to: 00405C24 00405C38
> > zimage at: 00406290 004A08FF
> > initrd at: 004A1000 006097CA
> > avail ram: 0060E000 007F8000
> >
> > Linux/PPC load: console=ttyS0,9600 console=tty1
> > ip=on
> > root=/dev/xsysace/disc0/pa
> > rt3 rw
> > Uncompressing Linux...done.
> > Now booting the kernel
> > -------------------------------------------
> >
> > After the last line, it hangs. I get a feeling
> that,
> > the uncompressing process is not writing in the
> > memory
> > starting from 0x00000000 and, after uncompressing,
> > it
> > is jumping into 0x00000000 and is not able to find
> > anything.
> >
> > My questions are,
> > 1. How can i make sure that, the uncompressing
> > process
> > is going to start writing the data from
> 0x00000000.
> >
> > 2. How big a space this uncompressing process
> needs?
> > And also how much overall memory is required for
> > running linux. I just have 8MB SDRAM.
> >
> > 3. What is the next step in the booting process?
> > Which
> > Device (eth, pci, ide, ???) Initialization?
> >
> > Your help is appreciated.
> >
> > thanks,
> > Prakash
> >
> >
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-20 16:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 16:10 After Uncompresseing Linux..., what's next James Don
2002-12-19 16:39 ` Tom Rini
2002-12-20 16:14 ` Prakash kanthi
2002-12-20 16:32 ` Prakash kanthi [this message]
2002-12-20 16:49 ` Jim Potter
2002-12-20 17:02 ` Jim Potter
2002-12-20 16:38 ` Gary Thomas
2002-12-20 16:48 ` Prakash kanthi
2002-12-20 16:52 ` Gary Thomas
2002-12-20 17:06 ` Prakash kanthi
2002-12-20 17:22 ` Gary Thomas
2002-12-20 21:59 ` Serious Problem: " Prakash kanthi
2002-12-20 16:47 ` Jim Potter
2002-12-26 22:47 ` Smallest Initrd (ram disk) Prakash kanthi
2002-12-26 22:55 ` Jim Potter
2003-01-13 2:15 ` Prakash kanthi
2003-01-13 7:55 ` Wolfgang Denk
2003-01-14 18:42 ` ramdisk mount problem Prakash kanthi
2003-01-14 18:57 ` Wolfgang Denk
2003-01-15 8:33 ` Frederic Soulier
2003-01-16 4:49 ` Ramdisk details; execve("/bin/sh") output Prakash kanthi
2003-01-16 5:57 ` Hi Anish
2003-01-16 8:00 ` Hi Wolfgang Denk
2003-01-16 8:06 ` Ramdisk details; execve("/bin/sh") output Wolfgang Denk
2002-12-27 0:22 ` Smallest Initrd (ram disk) Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 1:01 bug in early_uart_init()? linuxppc_2_4_devel Brad Parker
2002-12-19 0:14 ` After Uncompresseing Linux..., what's next Prakash kanthi
2002-12-19 1:09 ` Jim Potter
2002-12-19 15:46 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021220163238.45233.qmail@web41215.mail.yahoo.com \
--to=pkanthi@yahoo.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.