Project Home
Project Home		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
QNX Operating System/Discussion/OSTech/devc-ser8250 and slogger/List of Posts
Forum Topic - devc-ser8250 and slogger: (6 Items)
   
Update
Pavol Kycina
03/31/2011 6:48 AM
post84458
devc-ser8250 and slogger   
Hello.

In old QNX4 days, serial driver (dev.ser) logged an event in traceinfo system in case of framing, parity and other 
errors.

It was very neat feature. Is there any equivalent in QNX 6.4 or newer?

I have tried starting devc-ser8250 with many "-v", but it only logged startup information about fifo sizes, buffer sizes
 to slogger.

Connecting serial line to other system with different baud rates produced garbage in qtalk screen, but sloginfo showed 
no entries regarding serial line.

Have I forgotten something?

Thanks, PKY
Niklas Angare
04/01/2011 3:55 PM
post84527
Re: devc-ser8250 and slogger   
It works for me on 6.5.0 x86:

# sloginfo                   
Time             Sev Major Minor Args
Apr 01 21:45:11    3     6     0 io-char: Framing error on /dev/ser2
Apr 01 21:48:49    3     6     0 io-char: S/W buffer Overrun error on /dev/ser2

I started devc-ser8250 with -F to disable flow control but nothing else that would matter.
Pavol Kycina
04/04/2011 7:24 AM
post84549
Re: devc-ser8250 and slogger   
Thanks for the info.

I have tried that, but it doesn't work for me. Could you please post cksum of devc-ser8250 you are using?

Mine is (in QNX 6.5.0 system) 1252698927 79459 /sbin/devc-ser8250

Do you have "special way to generate errors" or is your line generating them?

Thanks, PKY

> It works for me on 6.5.0 x86:
> 
> # sloginfo                   
> Time             Sev Major Minor Args
> Apr 01 21:45:11    3     6     0 io-char: Framing error on /dev/ser2
> Apr 01 21:48:49    3     6     0 io-char: S/W buffer Overrun error on /dev/
> ser2
> 
> I started devc-ser8250 with -F to disable flow control but nothing else that 
> would matter.
Pavol Kycina
04/04/2011 8:25 AM
post84559
Re: devc-ser8250 and slogger   
Update on my previous post.

My test setup: 2 computers, sending one configured to 38400 8N1, receiving one configured to 38400 8E1. Note the 
difference in parity.

In QNX4 setup, after sending 196 bytes from xml file I get on receiving computer 120 framing errors and 80 parity errors
 logged in traceinfo.

In QNX6 setup, I get 19 framing errors and 14 parity errors. The difference in numbers (approx. only 1/6 is logged in 
comparison to QNX4) may be the reason that so far I haven't seen any logs regarding these errors.

That made me suspicious about fifo threshold in qnx6 setup.

I made a test, when I configured rx fifo to 14, 4 and 1. (8 is the default setup)

Here are the results:
threshold 14 ... 12 framing errors, 11 parity errors
threshold 8 .... 19 framing errors, 12 parity errors
threshold 4 .... 39 framing errors, 13 parity errors
threshold 1 .... no errors ?????

It seems the higher the threshold, the less errors get reported. So to be able to check the line quality one should set 
the threshold to 1. But unfortunately, no errors are reported at this setting.

Any ideas?

Regards, PKY

> It works for me on 6.5.0 x86:
> 
> # sloginfo                   
> Time             Sev Major Minor Args
> Apr 01 21:45:11    3     6     0 io-char: Framing error on /dev/ser2
> Apr 01 21:48:49    3     6     0 io-char: S/W buffer Overrun error on /dev/
> ser2
> 
> I started devc-ser8250 with -F to disable flow control but nothing else that 
> would matter.
Niklas Angare
04/15/2011 2:54 PM
post85064
Re: devc-ser8250 and slogger   
> I have tried that, but it doesn't work for me. Could you please post cksum of 
> devc-ser8250 you are using?
> 
> Mine is (in QNX 6.5.0 system) 1252698927 79459 /sbin/devc-ser8250

# cksum `which devc-ser8250`
 476569156      80321 /sbin/devc-ser8250
# use -i `which devc-ser8250`
NAME=devc-ser8250
DESCRIPTION=Character device driver for the 8250 chipset
DATE=2010/07/09-13:55:14-EDT
STATE=stable
HOST=mainbuild
USER=builder
VERSION=6.5.0
TAGID=89
# uname -a
QNX localhost 6.5.0 2010/07/09-14:43:25EDT x86pc x86

> Do you have "special way to generate errors" or is your line generating them?

The receiver was set to 57600 bits/s while the sender was set to 19200 bits/s, I believe. No application had the serial 
port open at the time.

> In QNX4 setup, after sending 196 bytes from xml file I get on receiving 
> computer 120 framing errors and 80 parity errors logged in traceinfo.
> 
> In QNX6 setup, I get 19 framing errors and 14 parity errors. The difference in
>  numbers (approx. only 1/6 is logged in comparison to QNX4) may be the reason 
> that so far I haven't seen any logs regarding these errors.

Could the difference be in the sender? These errors will be affected by the spacing between characters.
Pavol Kycina
04/19/2011 4:17 AM
post85108
Re: devc-ser8250 and slogger   
Thanks for the information.

Difference between your and mine devc-ser8250 is probably caused by the different release. I was using experimental 
release of 6.5.0. from 23.6.2010.

I have also noticed the variation caused by sender. 
I have DELL GX620 computer running windows XP, this computer is used as a sender. When I connect serial cable to real 
serial port, it logs different errors on receiver's side to the situation when I connect serial cable to prolific 
usb2serial port. 

Thanks for your assistance.

Regards, PKY

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems