I wrote in a previous post: I have found the same problem on an application that I am working on. It works fine on pre-OS5s but fails on the Tungsten. I have talk to Palm directly and indirectly and have not received any helpful information. My application is a real time app and must be able to process serial information as it enters the serial port. However I have found that serial input port is buffer incoming bytes of data over a very short time period (3-4 milliseconds). This short time period is an eternity for my application, which results in the application failing to deliver the desired results. I do not have the option of trying my application on a Sony NX series because my application uses an adapter utilizing the Palm universal connector. I hope that Palm is listening to this!
Since that post i have been in touch with an engineer from Palm Source. The following message was sent to that engineer: I checked the code and looks like FCR7:2 is set 00 (to generate an interrupt every 8 bytes) and SCR7 = 0 and TLR7:4 = 0000. Unfortunately we cannot do anything about this because it is a already shipping product. I am not sure if the future products will keep it like this or change it to 1 byte buffering. The fowwing message was his response: Unfortunately this is below the OS level and cannot be controlled by tweaking the OS. Changes have to made to underlying layer below OS, i am not sure if they can just fix it easily. Will let you know when i find more information on this. The real problem here is that the OMAP processors serial UART3 is not sending incoming bytes directly to the SrmReceive FIFO buffer when it is determined that that incoming byte is legitimate. SrmReceiveCheck check for the number of bytes in the SrmReceive FIFO Buffer. I hope this may help someone and that the next release of the OS fixes the problem for us developing real time serial applications. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
