From: Jing Luo <Jing@vicom.com>
To: 'Charles-Henri Balet' <charles-henri@bluewin.ch>,
ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Insight 5.1.1 with Angel /serial debugger
Date: Tue, 26 Feb 2002 21:55:00 -0000 [thread overview]
Message-ID: <B26EACBBAF91D411BD8500508BF7D695051D80@earth.vicom.com> (raw)
The same problem with me when I am trying to port eCos to 80200EVB.
But my configuration is disable of CYGIMP_HAL_PROCESS_ALL_EXCEPTIONS and
enable of of CYGSEM_HAL_USE_ROM_MONITOR.
If this one doesn't work, how I can do to debug eCos?
Thanks,
-----Original Message-----
From: Charles-Henri Balet [mailto:charles-henri@bluewin.ch]
Sent: Tuesday, February 26, 2002 9:58 AM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Insight 5.1.1 with Angel /serial debugger
Hi,
I use Insight 5.1.1 on an ARM processor on a board with Angel 1.20, the
link, download, debugger work fine,
my problem, the ecos startup code in the Vectors.s file, this startup
replace vectors in the vector table and when the
vector of the undefined instruction is replaced, insight freeze, I'm have to
start step by step and the problem is
on the line "str r2,[r0,#0x24]"
this is the part of the warm_reset where the problem appear :
mov r0,#0 // move vectors
ldr r1,=__exception_handlers
#ifndef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
// Wait with this if stubs are included (see further down).
ldr r2,[r1,#0x04] // undefined instruction
str r2,[r0,#0x04]
ldr r2,[r1,#0x24]
str r2,[r0,#0x24]
#endif
ldr r2,[r1,#0x08] // software interrupt
str r2,[r0,#0x08]
I have built an "RAM" startup, with enable of
CYGIMP_HAL_PROCESS_ALL_EXCEPTIONS
and disable of CYGSEM_HAL_USE_ROM_MONITOR.
any has any idea, can we modify the vectors table with an Angel debugger ?
many thanks
balet charles-henri
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2002-02-27 2:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 21:55 Jing Luo [this message]
2002-02-28 0:27 ` Jesper Skov
2002-02-28 14:28 ` [ECOS] Oddly formatted target.ld Bill Knight
2002-02-28 17:32 ` michael shiloh
2002-03-01 12:03 ` Jonathan Larmour
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 20:20 [ECOS] Insight 5.1.1 with Angel /serial debugger Jing Luo
2002-02-28 22:49 ` Charles-Henri Balet
2002-03-01 11:42 ` Jonathan Larmour
2002-02-26 14:39 Charles-Henri Balet
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=B26EACBBAF91D411BD8500508BF7D695051D80@earth.vicom.com \
--to=jing@vicom.com \
--cc=charles-henri@bluewin.ch \
--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).