This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: ecos application problem
- From: Sergei Gavrikov <w3sg at SoftHome dot net>
- To: "Paul D. DeRocco" <pderocco at ix dot netcom dot com>
- Cc: 'albert prasetyo' <prasetyoalbert at gmail dot com>, 'ecos-discuss' <ecos-discuss at ecos dot sourceware dot org>
- Date: Fri, 24 Aug 2007 09:06:03 +0300
- Subject: RE: [ECOS] ecos application problem
- References: <02b801c7e602$3d029150$887ba8c0@PAULD>
Paul D. DeRocco writes:
> > From: albert prasetyo [mailto:prasetyoalbert@gmail.com]
> >
> > Thanks for the reply. According to your remarks, is it means
> > that I need to exclude GDB stubs in HAL (redboot template)?
> > (i.e. disable CYDBG_HAL_DEBUG_GDB_INCLUDE_STUBS)
> > I tried to do that but the output is still the same.
> > I communicate with the board using hyperterminal.
>
> I'm no expert in this area, because my ARM7 board has a second serial port
> that I use for my application, leaving the first for the GDB stubs. I'm
> under the impression that the application accesses the serial port through
> the virtual vector table, so it is still the Redboot code in flash that is
> doing the output mangling. Maybe someone else can point to the particular
> option that makes the application not use the VV table for serial I/O. Of
> course, this would prevent serial debugging.
Try to import this
cat <<_EOF | ecosconfig import /dev/stdin
cdl_option CYGSEM_HAL_USE_ROM_MONITOR {inferred_value 0 Generic};
cdl_option CYGSEM_HAL_DIAG_MANGLER {user_value None};
_EOF
before the build the eCos stuff
Sergei
>
> --
>
> Ciao, Paul D. DeRocco
> Paul mailto:pderocco@ix.netcom.com
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss