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: Fw: Asynchronous GDB break serial target


I was fooled by the GUI configtool, where I changed some options, but
hitting F7 for build didn't recompile vector.s, where hal_ctrlc_isr_init is
called.
After deleting all *.o files in the build tree's and remaking
hal_ctrlc_isr_init was called.
Asynchronous Break now seems to work, I'll have to test further...

Raymund Hofmann

----- Original Message -----
From: "Jesper Skov" <jskov@cambridge.redhat.com>
To: "RAY Electronic-Design GmbH" <info@raygmbh.de>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Thursday, August 02, 2001 8:51 AM
Subject: Re: [ECOS] Fw: [ECOS] Asynchronous GDB break serial target


> >>>>> "RAY" == RAY Electronic-Design GmbH <info@raygmbh.de> writes:
>
> >> I traced so far now, that the hal_default_isr is called, but in
> >> there is going on something i don't understand:
> >>
> >>
> >> __ #ifndef CYGSEM_HAL_ROM_MONITOR if
> >> (CYGNUM_CALL_IF_TABLE_VERSION_CALL_HACK ==
> >> (CYGACC_CALL_IF_VERSION() &
> RAY> CYGNUM_CALL_IF_TABLE_VERSION_CALL_MASK))
> >> #endif { hal_virtual_comm_table_t* __chan =
> >> CYGACC_CALL_IF_DEBUG_PROCS(); if (__chan) gdb_vector =
> >> CYGACC_COMM_IF_CONTROL(*__chan, __COMMCTL_DBG_ISR_VECTOR); } if(
> >> vector == gdb_vector ) __
> >>
> >> in there it reads the version of the virtual vector table, which is
> >> 0x18
> RAY> in
> >> my redboot build, but tries to compare it with 0x41. The Version is
> >> calculated:
>
> The version is set to 0x41 in hal_ctrlc_isr_init which is (or should
> be) called by RAM applications as they enable ctrl-c support.
>
> Jesper


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