From: Evgeny Belyanco <esp1@kbkcc.ru>
To: ecos-discuss@ecos.sourceware.org
Subject: Re[2]: [ECOS] eCos & RedBoot on AT91SAM7S
Date: Thu, 15 Jun 2006 17:47:00 -0000 [thread overview]
Message-ID: <1276357639.20060615214425@kbkcc.ru> (raw)
In-Reply-To: <20060615173216.GG15848@lunn.ch>
Thursday, June 15, 2006, 9:32:16 PM, you wrote:
>> will I be capable of writing code to FLASH via GDB (RS-232
>> connection)?
AL> Using gdb, no. You need to use redboot itself to do an xyzmodem load
AL> into flash.
>> Can I make debugging in FLASH via GDB (RS-232 connection)?
AL> You cannot have break points, or single step. So this makes it very
AL> hard to do anything useful.
AL> The only practicaly way to debug code in Flash is over the jtag
AL> interface.
If I will use simple JTAG tool, for example Macraigor usb2Sprite™
http://www.macraigor.com/usb2sprite.htm
will I can make FLASH write, break points, or single step in
AT91SAM7S?
Or I need only "serious" JTAG tool like PEEDI for this features?
Evgeny Belyanko
**********************************
* E-mail: ea@kbkcc.ru
**********************************
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-06-15 17:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 16:55 [ECOS] Problem with Config Tool on Cygwin Tom Smithkowski
2006-06-15 8:34 ` [ECOS] " John Dallaway
2006-06-15 12:25 ` John Dallaway
2006-06-15 15:06 ` Tom Smithkowski
2006-06-15 15:16 ` John Dallaway
2006-06-15 15:53 ` Andy Jackson
2006-06-15 17:22 ` [ECOS] eCos & RedBoot on AT91SAM7S Evgeny Belyanco
2006-06-15 17:32 ` Andrew Lunn
2006-06-15 17:47 ` Evgeny Belyanco [this message]
2006-06-15 18:53 ` Andrew Lunn
2006-06-15 20:55 ` Re[2]: " Evgeny Belyanco
2006-06-15 22:59 ` Laurie Gellatly
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=1276357639.20060615214425@kbkcc.ru \
--to=esp1@kbkcc.ru \
--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).