traceinfo code help

QNX Newsgroups (Archives) qdn.public.qnx4
1

Hi -

I’m trying to determine what the following tracelog entry means:
Oct 02 19:08:02 2 00002007 00000680

I’m pretty sure it has something to do with the serial device at address
680,
but I’m not sure what. The copy of /etc/config/traceinfo we’ve got doesn’t
list this event.

Thanks.

  • Fred.
2

Is this a Blue Heat card? If so it may be an “unexpected break” - I
don’t recall if that’s what 2007 meant. If this sounds like it, I notice
Connectech has a new driver - you might try that.

If you download the Dev.ser source, you may be able to figure it out.

Richard

Fred Boak wrote:

Hi -

I’m trying to determine what the following tracelog entry means:
Oct 02 19:08:02 2 00002007 00000680

I’m pretty sure it has something to do with the serial device at address
680,
but I’m not sure what. The copy of /etc/config/traceinfo we’ve got doesn’t
list this event.

Thanks.

  • Fred.
3

Fred Boak <fred@wordstock.com> wrote:

Hi -

I’m trying to determine what the following tracelog entry means:
Oct 02 19:08:02 2 00002007 00000680

I’m pretty sure it has something to do with the serial device at address
680,
but I’m not sure what. The copy of /etc/config/traceinfo we’ve got doesn’t
list this event.

you got a break ( bit 0x10 of the lsr ) on port 0x680
the tracecodes should be updated to reflect this… this is a transient
condition on the port as you know.

–
Randy Martin email: randy@qnx.com www.qnx.com
QNX Software Systems Ltd. QUICS: randy (613) 591-0934 (data)
(613) 591-0931 x287 (voice) mail: 175 Terence Matthews Cr
(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8

4

It’s not a Blue Heat card, I’m afraid. I was hoping I could get
a quick answer rather than have to grovel through the Dev.ser
code, but it looks like I might have to.

Thanks for the Blue Heat info, though!

  • Fred.

Previously, Richard R. Kramer wrote in qdn.public.qnx4:

Is this a Blue Heat card? If so it may be an “unexpected break” - I
don’t recall if that’s what 2007 meant. If this sounds like it, I notice
Connectech has a new driver - you might try that.

If you download the Dev.ser source, you may be able to figure it out.

Richard

Fred Boak wrote:

Hi -

I’m trying to determine what the following tracelog entry means:
Oct 02 19:08:02 2 00002007 00000680

I’m pretty sure it has something to do with the serial device at address
680,
but I’m not sure what. The copy of /etc/config/traceinfo we’ve got doesn’t
list this event.

Thanks.

  • Fred.
5

Randy’s right about it being a BREAK. The reason I asked if it was a
Blue Heat, is that the only time we ever ewncountered this trace code
was with a few of these cards. As you know, a BREAK doesn’t normally
cause this output. The section of code that logs this is dealing with
“spurious” events. The comments read:
Read whatever input data happens to be in the
buffer (to “eat” the spurious data associated
with break, parity error, etc.)


Fred Boak wrote:

It’s not a Blue Heat card, I’m afraid. I was hoping I could get
a quick answer rather than have to grovel through the Dev.ser
code, but it looks like I might have to.

Thanks for the Blue Heat info, though!

  • Fred.

Previously, Richard R. Kramer wrote in qdn.public.qnx4:
Is this a Blue Heat card? If so it may be an “unexpected break” - I
don’t recall if that’s what 2007 meant. If this sounds like it, I notice
Connectech has a new driver - you might try that.

If you download the Dev.ser source, you may be able to figure it out.

Richard

Fred Boak wrote:

Hi -

I’m trying to determine what the following tracelog entry means:
Oct 02 19:08:02 2 00002007 00000680

I’m pretty sure it has something to do with the serial device at address
680,
but I’m not sure what. The copy of /etc/config/traceinfo we’ve got doesn’t
list this event.

Thanks.

  • Fred.