From: Gary Thomas <gary@chez-thomas.org>
To: Prakash kanthi <pkanthi@yahoo.com>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: After Uncompresseing Linux..., what's next
Date: 20 Dec 2002 09:52:33 -0700 [thread overview]
Message-ID: <1040403153.32282.6220.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <20021220164821.77027.qmail@web41213.mail.yahoo.com>
On Fri, 2002-12-20 at 09:48, Prakash kanthi wrote:
> I do have xilinx tools and i am working with their V2P
> product. I completely understands what you are said.
> But the problem is, right after the uncompression and
> cpy to 0x00000000, i loose total control because i
> don't have any clue what is getting executed.
>
What sort of things can you do with the Xilinx tools? Is
there any way to set [hardware] breakpoints or single step?
> And also, i have my boot monitor code at 0x00000000,
> before uncompress process overwrites it. I see that
> some of that code is getting executed after jump to
> 0x0. I reason i am overwriting 0x0 is because, i only
> have 8MB RAM.
>
8M should be plenty of RAM.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-20 16:52 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
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 [this message]
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=1040403153.32282.6220.camel@hermes.chez-thomas.org \
--to=gary@chez-thomas.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pkanthi@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).