This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: virtual vectors problem
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Stephane Royo <stephane dot royo at europe-technologies dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Wed, 07 Sep 2005 07:47:13 -0600
- Subject: Re: [ECOS] virtual vectors problem
- References: <001301c5b3af$b007ff50$6401a8c0@europetechnologies.com>
On Wed, 2005-09-07 at 15:25 +0200, Stephane Royo wrote:
> Hello,
>
> I updated eCos via CVS, then my application two months ago. Since, i noticed
> that the comm_channels variable -used to contain the functions pointer on
> serial communication channel- is no more in data section but it is in bss
> section.
>
> So, when my application is configurated to works in RAM in order to debug
> it, i have problem. Indeed, in this configuration i use the option "Inherit
> console settings from ROM monitor", but unfortunately the comm_channels
> variable is put to zero during the bss initialization consequently, all
> subsequent accesses to comm_channels variable cause a hardware reset.
>
> I didn't find anything in eCos sources or in my configuration (ecc file)
> which explains this change of location, but to solve the problem i
> initialized the comm_channels at the time of declaration : static
> hal_virtual_comm_table_t
> comm_channels[CYGNUM_HAL_VIRTUAL_VECTOR_NUM_CHANNELS+1]={0};
>
> Anybody, could help me to understand the problem ?
We'd need to know what platform/target you are using. This stuff
works (has worked for many years), so it's probably something "special"
in your target support.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss