This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: AEB: GDB vs. ROM monitor dilemma

To: Jesper Skov <jskov at cambridge dot redhat dot com>
Subject: Re: [ECOS] AEB: GDB vs. ROM monitor dilemma
From: Marco Götze <marco dot goetze at imms dot de>
Date: Tue, 20 Mar 2001 14:05:57 +0100 (MET)
Cc: ecos-discuss at sources dot redhat dot com
References: <985085393.3ab735d16b9a8@imp.imms.de> <otsnk88wec.fsf@thinktwice.zoftcorp.dk>

Quoting Jesper Skov <jskov@cambridge.redhat.com>:
> Marco> Symptoms: When running the target application inside GDB
> Marco> (Insight), things work as expected.  When communicating with
> Marco> the on-board ROM monitor (v0.01) via a terminal application
> Marco> (minicom), however, execution typically immediately branches
> Marco> through zero (as remarked upon by the monitor, followed by a
> Marco> reboot).
> Are you running an eCos app by downloading it with the board monitor's
> download command? If so, you will need to hack the eCos startup (I
> think including stubs should suffice) so the board will be properly
> initialized. The board monitor does not leave the board in the state
> expected by eCos applications.

Yes indeed--thanks!  Didn't expect it to be *that* simple, though. :^)


Marco
-- 

-------------------------------------------------
This mail sent through IMP: imp.imms.de

References:
- AEB: GDB vs. ROM monitor dilemma
  - From: Marco Götze
- Re: AEB: GDB vs. ROM monitor dilemma
  - From: Jesper Skov

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]