This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: EB40A (AT91) serial port oddness
Tom Lynn <tom.lynn@hypertag.com> writes:
> Thanks for the helpful suggestions. It looks like it was a problem
> with driving the cable-replacement hardware I've been using and not
> the serial port itself after all. I was misled by that fact that the
> following Python code which I'd expect to be equivalent to the eCos
> code works as expected:
>
> from serial import Serial # http://pyserial.sourceforge.net
> from time import sleep
>
> s = Serial("COM1", 9600, 8, 'N', 1, xonxoff=0, rtscts=0, writeTimeout=None)
> while 1:
> s.write("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz-=\n")
> sleep(1)
>
> So it looks like I'll be digging around comparing the internals of the
> two for a while. Any suggestions on what to look for would be much
> appreciated.
It is possible that the Python code is emitting the characters more
slowly that the AT91's serial hardware. With the PDC it should be
sending the characters out at close to line speed.
>
> I'd still be interested to know how you turn off the debug output too,
> since I suspect I'll have more serial port diagnosis in the near
> future. My suspicion is that so few people want to turn it off that
> turning it off no longer works.
I'm not entirely sure what you are asking here. If you don't call
diag_printf() then there will be no traffic on the debug serial
line. You can then use it for any purpose you want.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss