From: Gary Thomas <gary@mlbassoc.com>
To: alysson brito <alysson.alysson@gmail.com>
Cc: Chris Zimman <czimman@bloomberg.com>, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: Trash when running RAM image
Date: Fri, 04 May 2007 11:48:00 -0000 [thread overview]
Message-ID: <463B1D85.6050609@mlbassoc.com> (raw)
In-Reply-To: <876437dd0705040443q5be9b8b6tf8e614fd28525e2b@mail.gmail.com>
alysson brito wrote:
> Hi
>
> On 5/3/07, alysson brito <alysson.alysson@gmail.com> wrote:
>> Hi Chris
>>
>> On 5/3/07, Chris Zimman <czimman@bloomberg.com> wrote:
>> > Alysson,
>> >
>> > Hook up GDB and see where it's crashing. There's not nearly enough
>> > information to tell you much further. What is the image that you're
>> > trying to run?
>> >
>> > --Chris
>> >
>> > -----Original Message-----
>> > From: ecos-discuss-owner@ecos.sourceware.org
>> > [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of alysson
>> > brito
>> > Sent: 03 May 2007 12:35
>> > To: ecos-discuss@ecos.sourceware.org; Adam Yergovich
>> > Subject: Re: [ECOS] Re: Trash when running RAM image
>> >
>> > Thanks for the reply! Actually I am trying to run an RAM image of
>> > redboot, not a ramdisk, I might have written something wrong, sorry.
>> >
>> > The problem still persists, I have seen that Gary wrote today on "Re:
>> > [ECOS] standalone Redboot configuration" that some ARM have to get
>> > some massage to runging RAM images, I do not know whether this is a
>> > case, since xscale is arm based.
>> >
>> > If some one can help me out really I'd really apreciated some more
>> tips.
>> >
>> > -- Alysson
>> >
>> >
>>
>> Yeah, It might be the only way to go, since I can not figure out what
>> the problem might be .... leider ...
>>
>> I am trying to run an redboot_RAM.srec file, that came along with the
>> board (processor xscale ixdp425) software toolkit. If you wanna, I can
>> send it to you via email.
>>
>> Thanks
>>
>> --Alysson
>>
>
> Sorry, for the question, but I am wondering whether I can hook up on
> gdb server of redboot rom image an debug the redboot_ram.
>
> I even tryed, but I got a SIGTRAP after some instructions (is the
> board been reset cause redboot ram image ?). Then "nexti" command does
> not go any further ...
>
> Could anyone pls tell me if it is possible to use gbd to test a
> redboot ram image ? Or must I really use a JTAG?
RedBoot can't be used to debug RedBoot via GDB, unless you build
the RAM version without GDB support. Using a JTAG debugger works
best for this.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-05-04 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <876437dd0705020801t68d84716s9a8c1c8be3dfa2a3@mail.gmail.com>
2007-05-02 15:02 ` alysson brito
2007-05-02 15:10 ` Gary Thomas
2007-05-02 17:17 ` alysson brito
2007-05-02 17:26 ` Adam Yergovich
2007-05-03 11:35 ` alysson brito
2007-05-03 11:57 ` Chris Zimman
2007-05-03 12:54 ` alysson brito
2007-05-04 11:43 ` alysson brito
2007-05-04 11:48 ` Gary Thomas [this message]
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=463B1D85.6050609@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=alysson.alysson@gmail.com \
--cc=czimman@bloomberg.com \
--cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).