At 12:42 PM -0800 2002/01/03, Daryl Van Vorst wrote: >The basic issue is: if a framing error occurs before (or at the start of preamble) >for an Ir packet (ex: any IrDA packet), the entire packet will be lost because the >serial manager forces you to call serClearErr (which takes longer to execute than >there are preamble characters) in order to continue reading/receiving characters.
Ah, serial IR... <eeew> >If you're fortunate enough to have a pile of m100's on your desk Heh heh... well I definitely have a pile of something on my desk, but it's not m100's... :oP >There... I think I explained it adequately. :) Yes, thanks! Now I know what you're trying to do. The following info may or may not help: UART framing errors are caught and tracked by the port driver "plug-in" with the current number of line errors for a given SrmReceiveXXX call being passed up to the serial manager. This is what's causing you the problem; the serial manager is detecting the line error(s) and doing what it can to recover, since the data just received as far as it's concerned is invalid. The only way around this that I can see is to write your own serial port driver which purposely ignores framing errors. The bad news is, this would require knowledge of the specific hardware for which it is to be used. The good news is, everything you need to write your own serial driver is available in the latest SDK and Palm OS KnowledgeBase. Best Regards, Jim Schram Palm Incorporated Partner Engineering -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
