From: Hsiang-ting Cheng <htcheng@broadmedia.com.tw>
To: danish iftikhar <d_iftikhar@hotmail.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] EP7211 & Jeeni
Date: Thu, 23 Nov 2000 17:31:00 -0000 [thread overview]
Message-ID: <3A1DC56D.441CE48F@broadmedia.com.tw> (raw)
In-Reply-To: <F299NFmWAFsTmIClmpc0000246e@hotmail.com>
Using JEENI means you don't need GDB stubs (disable "Include GDB
stubs in HAL). Your arm-elf-gdb is talking to the ICE via direct serial
connection or ethernet connection (select ANGEL/serial or ANGEL/Ethernet
in Taget Setting if you are using insight-5.0 for arm-elf)
Some hints can be found in the FAQs of JEENI
( http://www.epitools.com/support/arm/faq_jeeni.shtml )
However, it is talking about gdb-4.18.
For diagnostic output, you should "disable GDB protocol for diagnostic output"
and using HyperTerminal or minicom to connect to the UART of your board.
Terry Cheng
danish iftikhar wrote:
> Hi
>
> i have build ecos on the linux host for EP7211 target board .
> i want to connect to the target board through the Embedded Ice (Jeeni).
> Does it also requires that gdb stub should be sitting inside the board . In
> ecos.ecc file there is option for serial port for the diagnostic output .
> But if we use Jeeni what happens to tha diagnostic output . where will this
> output be printed and how .
> do i need to configure some options in ecos.ecc to be able to make it behave
> decently with Jeeni .
>
> thanks
> danish.
> _____________________________________________________________________________________
> Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com
next prev parent reply other threads:[~2000-11-23 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 23:25 danish iftikhar
2000-11-23 17:31 ` Hsiang-ting Cheng [this message]
2001-01-11 8:21 danish iftikhar
2001-01-12 0:00 ` Jesper Skov
2001-01-12 6:48 danish iftikhar
2001-01-12 7:23 ` Jesper Skov
2001-01-12 9:29 ` Grant Edwards
2001-01-12 7:38 danish iftikhar
2001-01-14 13:01 ` Jesper Skov
2001-01-16 15:43 Jeremy Lin
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=3A1DC56D.441CE48F@broadmedia.com.tw \
--to=htcheng@broadmedia.com.tw \
--cc=d_iftikhar@hotmail.com \
--cc=ecos-discuss@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).