From: Jonathan Larmour <jlarmour@cygnus.co.uk>
To: Andrea Acquaviva <acquaviva@deis.unibo.it>
Cc: eCos discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS]Hello World on AEB rev.C
Date: Tue, 07 Nov 2000 08:27:00 -0000 [thread overview]
Message-ID: <3A082D52.80940884@cygnus.co.uk> (raw)
In-Reply-To: <3A07FC30.E7D865F8@deis.unibo.it>
[ BTW, your mail address bounces ]
Andrea Acquaviva wrote:
>
> Jonathan Larmour wrote:
>
> > Andrea Acquaviva wrote:
> > >
> > > Hi,
> > >
> > > I followed the instructions on the manuals to build eCos for AEB revC
> > > board and
> > > link it with the Hello World example, but when I start with the
> > > debugging after
> > > the download, the "insight" debugger crashes. I use Angel as a debug
> > > monitor in the target board.
> > > The steps I made to build eCos for AEB are the followings:
> > >
> > > - ecosconfig new aeb
> > > - in the ecos.ecc file I set the user_value in the
> > > CYGHWR_HAL_ARM_AEB_REVISION option
> > > section to "C".
> > > - in the same file I set the user_value in the CYG_HAL_STARTUP option
> > > section to "RAM".
> > > - ecosconfig tree
> > > - make
> > >
> > > Are there some settings that I need to be aware to keep executables
> > > working on
> > > the AEB board with Angel remote debug monitor?
> >
> > You cannot use RAM-loaded eCos applications under Angel. Instead you should
> > reprogram the board with GDB stubs. This is described in the Getting
> > Started documentation.
> >
> > Jifl
> > --
> > Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
> > "Plan to be spontaneous tomorrow." || These opinions are all my own fault
>
> Hi,
>
> I downloaded the prebuilt version of the gdb-stub (gdb_module-revC.img,
> version 1.2.2) ,
You mean downloaded as in programmed in flash right?
> but after the connection with the target (set to remote/serial, 9600 baud),
> I'm not able to dowload the hello executable
> (the download command has no visible effect).
If you just connect with a direct serial connection, when you power on the
board you should be able to see output like ++$T01.....
If not, then the gdb stub is not programmed onto the board correctly.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-11-07 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 2:46 Andrea Acquaviva
2000-11-06 11:34 ` Jonathan Larmour
2000-11-07 6:15 ` Andrea Acquaviva
[not found] ` <3A07FC30.E7D865F8@deis.unibo.it>
2000-11-07 8:27 ` Jonathan Larmour [this message]
2000-11-08 6:18 ` Andrea Acquaviva
2000-11-14 4:44 [ECOS] Hello world " Andreas.Karlsson
2000-11-14 6:39 ` Andrea Acquaviva
2000-11-16 22:11 ` Jonathan Larmour
2000-11-20 4:29 ` Andrea Acquaviva
2001-01-18 20:39 [ECOS]Hello World " Narayanan, Anita (CTS)
2001-01-19 2:33 ` Jesper Skov
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=3A082D52.80940884@cygnus.co.uk \
--to=jlarmour@cygnus.co.uk \
--cc=acquaviva@deis.unibo.it \
--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).