linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Wade Maxfield" <wmaxfield@gmail.com>
To: ppc <linuxppc-embedded@ozlabs.org>
Subject: debugging custom Xilinx boot loader with abatron and Montavista devrocket
Date: Fri, 23 Feb 2007 10:11:28 -0600	[thread overview]
Message-ID: <45a1b53e0702230811i79bbc10dqd6e10ac05b06ac16@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2012 bytes --]

  I want to debug a ppc custom boot loader with Montavista (since we spent
the money on it) under the Xilinx fx60.

  I've been able to get the kernel to debug under MontaVista.  However,
since the hardware engineers have given up on DDR ram (they could not get it
to work reliably and will be dropping it from the next release), I don't
think I can use Linux for now.   Unfortunately, this decision is not
changeable.  When a hardware engineer is embarrassed, the results are not
good for software engineers.

I don't think I've got enough static ram to host a PPC linux kernel and
applications (we only have 8 meg).  We will have 16 meg on the next release,
I expect.  Is that enough for simple apps and linux under PPC???  I need
some guidance here, as I don't have enough PPC experience.

  Fortunately, we got the ppc running and can manage the hardware using
Xilkernel and Xilnet (lwIP maybe later).

  I've done numerous Google searches, and searches on MontaVista support
page.  They are specific to Linux.

  Has anyone debugged a custom boot loader with MontaVista and Abatron?  How
do you set up the project under  eclipse (which is devrocket)?  Nothing I
see seems to match, as I need the boot vector code, and I don't know how to
tell eclipse to compile for that option.  Can I just bring over the elf
(compiled with debug under Xilinx) and the source files and start
debugging?  If so, what kind of project would I pick under devrocket?  The
more I look, the more confused I get.

   I could possibly bring up linux on an ML403 board and use gdb/ddd on
that.  if so, how would I cause the boot code to be located at the right
address?  Any howto's to read that aren't simply hand waves would be very
useful. I understand once I do it is easy, but getting it done the first
time is my problem right now.

   I've got to pull some serious asses from the fire, so I'm under a lot of
pressure.  I also know who will be blamed if I don't pull this off.

  Any help is greatly appreciated!

thanks,
wade

[-- Attachment #2: Type: text/html, Size: 2261 bytes --]

             reply	other threads:[~2007-02-23 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 16:11 Wade Maxfield [this message]
2007-02-23 21:33 ` debugging custom Xilinx boot loader with abatron and Montavistadevrocket Leonid
2007-02-23 21:53 ` debugging custom Xilinx boot loader with abatron and Montavista devrocket Jeff Angielski
2007-02-24 22:40   ` Wade Maxfield
2007-02-24 23:14     ` debugging custom Xilinx boot loader with abatron and Montavistadevrocket Martin, Tim
2007-02-24 23:34     ` Charles Krinke

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=45a1b53e0702230811i79bbc10dqd6e10ac05b06ac16@mail.gmail.com \
    --to=wmaxfield@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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 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).