thanks all for the replies,
no Xon Xoff is enabled in the terminal, i tested also other PC
terminals, same issue.
Problem seems to happen for some hours/days, and then disappear, to come
back again.
MAX3232 circuit seems working properly, and in any case, it don't have
any memory inside.
Don't seems also that unused HW interrupts are the cause, i pulled them up.
The fact that when i press a key, the rest of the message is received,
make me think that the device is in some "paused" state, and send the
reminder when i unlock it pressing a key.
At boot, big parts of "mesg" are not sent out, and sometime i don't even
get those parts later, but just the promt (#), like below.
Linux version 2.6.29-uc0001 (ang...@angel7) (gcc version 4.2.4) #204 Tue
Jun 8 21:35:13 CEST 2010
uClinux/COLDFIRE(m5307)
COLDFIRE port done by Greg Ungerer, [email protected]
Modified for M5307 by Dave Miller, [email protected]
Flat model support (C) 1998,1999 Kenneth Albanowski, D. Jeff Dionne
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 4064
Kernel command line:
PID hash table entries: 64 (order: 6, 256 bytes)
Dentry cache hash table entrieb]
#
115200 should be still a quite safe serial speed, measured the bit width
through scope, it is 8.8usec, (113.636 baud) the cable is hand-made. but
in any case, as i said, often most of the missing parts are sent to the
PC later, when i press a key, so this don't seems to be cable related.
I am still investigating.
thanks
Regards,
Angelo
On 08/06/2010 22:57, Lennart Sorensen wrote:
On Tue, Jun 08, 2010 at 10:35:18PM +0200, angelo wrote:
i have a strange issue on the console serial port.
On a coldfire 5307, uClinux kernel 2.6.X, using the console serial port
at 115200,N,8,1, bus_clock 45Mhz, sometime a block of bytes (even some
hundreds) seems lost and not received from the PC-side terminal. But
when i press a key, the missing block is then received.
Example:
# ls
bin dev etc
(nothing more is received, so i press<enter>)
# ls
bin dev etc home lib mnt proc tmp usr var
#
(after enter missing part arrive).
Could this issue be related to some kernel misconfiguration ? Or most
probably another HW issue ?
115200 is really pushing it unless you have a high quality cable and
good buffering on both ends of the link (which the console port probably
doesn't have). Use 57600 if you want reliable console is my experience.
Now the other possibility is that you have an IRQ mistake, in which
case you hitting a key generates an IRQ that then causes it to start
transmitting again. Maybe your IRQ line isn't hooked up properly or
not configured right.
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
