ECS-L Home Automation and Security Archives
  learn more | view messages for this month | NetBloc® | terms of use | search

Google
 


  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects

Subject:
From:
Date:
CCE3:RX OVERRUN
Mark Gilmore
Mon, 23 Aug 1999 13:41:32 -0700

Regarding the old "CCE3:RX OVERRUN" error:
When resetting the CPU-XA with ECS, I noticed that
I would get this error every time - BINGO - I COULD
FINALLY REPRODUCE IT!

What triggered it was queing BELL.WAV (click sound)
just prior to requesting a 264-byte packet from the CPU-XA.
This packet was being received during playback, and triggered
an overrun on the UART's 16-byte FIFO (Win did not service
the RX-byte interrupt in time). I know it was a UART overrun
because the RX-byte count is always 16.
What's strange is that I have the related COM port at IRQ3,
and the sound-card at IRQ7. So I would expect COM4 interrupts
to have priority. I must be missing something.

Additional clues:
1) The error does NOT occur on my faster 233MHZ PC
   (only on my 66MHZ). I am curious to know if all
   who are experiencing this problem are using "slower" PCs.
2) The error does NOT occur if I replace BELL.WAV with one
   that I recorded (frequency-related ???). This is a quick/
   dirty "fix". If you do this, also replace ERRBELL.WAV.

Any ideas as to causes and/or solutions ???
Tanx
-- 
Mark Gilmore
Omnipotence (ECS home automation software)
http://www.usit.com/omnip
omnip@usit.net
423-745-0026

  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects




Services provided by [NetBloc]®! NetBloc Solutions Inc.
Terms of use. Indexing software (c) 1999 Lin-De, Inc
.