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: Re: debugging custom Xilinx boot loader with abatron and Montavista devrocket
Date: Sat, 24 Feb 2007 16:40:54 -0600	[thread overview]
Message-ID: <45a1b53e0702241440y76024946w20ba32658460388c@mail.gmail.com> (raw)
In-Reply-To: <1172267591.13040.30.camel@jaalaptop>

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

   Thanks!

   I did indeed mean to say "devrocket" when I said "MontaVista"

   I went down the DDD/gdb  route using the MontaVista command line tools.
Their ppc_405-gdb connects to the abatron bdi2000 as a gdb server.  I was
able to get that to work to some extent.

    I did not ask my main question correctly enough.  Let me rephrase.

    My main question (for the MontaVista experts out there) is either

    1) In DevRocket, what kind of project do you choose to debug an
externally build .elf file?
       MontaVista support engineers had no clue.

    or

    2) How do you use DevRocket to create a cross compiled set of code
linked to a specific address.
       MontaVista support engineers also had no clue on this one.

   If either answer is no, OK.

    Now that I have the DDD/gdb/Abatron complex working, I don't think I
absolutely need the DevRocket and its nice (but slow) facilities.  It would
be nice to do the cross compile under DevRocket, but the Xilinx EDK is doing
just fine.

    I will look into uboot later, when I do another attempt at getting linux
into the system.

   I failed to mention that we have the system ace chip with a compact flash
card, and it is apparently functional.  It provides all the "flash" that we
need.  We do have some onboard flash for configuration data.

   Our project is simultaneously complex and simple.  It is complex in what
it does ( a complicated receiver based on latest DSL technology), but simple
in the household chores (linux is almost overkill, but we do need ethernet
and all that implies).

  Interesting we can get PPC linux into 16 meg.  Once that happens, I'll try
it again.

thanks,
wade


On 2/23/07, Jeff Angielski <jeff@theptrgroup.com> wrote:
>
> On Fri, 2007-02-23 at 10:11 -0600, Wade Maxfield wrote:
> >
> >   I want to debug a ppc custom boot loader with Montavista (since we
> > spent the money on it) under the Xilinx fx60.
>
> Writing custom bootloaders is nontrivial.  Are you sure you really want
> to do that?
>
> And what does MV have to do with the bootloader?


<snip>

--
> Jeff Angielski
> The PTR Group
>
>

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

  reply	other threads:[~2007-02-24 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 16:11 debugging custom Xilinx boot loader with abatron and Montavista devrocket Wade Maxfield
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 [this message]
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=45a1b53e0702241440y76024946w20ba32658460388c@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).