This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: Init-problem with ecos.
- From: "Chris Zimman" <czimman at bloomberg dot com>
- To: <Bob dot Brusa at gmail dot com>, "ecos-discuss" <ecos-discuss at ecos dot sourceware dot org>
- Date: Mon, 6 Apr 2009 10:24:42 -0400
- Subject: RE: [ECOS]Init-problem with ecos.
- References: <op.uryx2qb8keg3uf@localhost>
> When running this app, I get the following output:
> ïïInit device '/dev/ser0'
> AT91 SERIAL init - dev: fffc0000.6
> Set output buffer - buf: 0x00202c80 len: 128
> Set input buffer - buf: 0x00202d00 len: 128
> Init device '/dev/ser1'
> AT91 SERIAL init - dev: fffc4000.7
> Set output buffer - buf: 0x00202d80 len: 128
> Set input buffer - buf: 0x00202e00 len:
> 128×ÔïïïïïïïïïÉïïÍïïÉï5)55)5)ïïïïïïïïÉï'AT91 SERIAL init - dev:
> fffc0000.6
> Set output buffer - buf: 0x00202c80 len: 128
> Set input buffer - buf: 0x00202d00 len: 128
> Init device '/dev/ser1'
> AT91 SERIAL init - dev: fffc4000.7<cut>.... and it repeats this
>
> When setting a breakpoint at the call myjob() it is reached, but now
> output appears on ser1. But debugging this application is tricky,
> because it does not show reproducible behaviour. What's going on here?
You have device initialization tracing turned on -- if you don't want to see
these messages, disable CYGDBG_IO_INIT.
I don't understand the issue further, can you elaborate a little more?
--Chris