> > are you getting the same results on PalmSim as well? > > No, the code works fine on the OS 5 Simulator. SrmReceiveCheck() > works as expected.
ok. then its a device issue :) > > so, best solution is to avoid SrmReceiveCheck() :) seems that is > > coded to thread block/return nothing until 8 bytes are in the > > buffer. > > That's what I'll have to do I guess. if what Craig Curry informs us is correct, there will be no workable solution to the problem - as, it seems that the UART on the OMAP is causing the delays you are experiencing. > > > We haven't tried this method, but I'll try it out. Thanks for > > > your help! > > > > its old code :) but, technically should work the same way. since > > you are only looking for one byte, you can have a pretty low > > timeout value without slowing things down too much :) > > > > i had to dig deep in my archives for that code.. its a bit dusty. > > Thanks again! i'd be very surprised if that code works, so, please do let us know. you might be able to force a timeout just enough not to impact your requirements :) *snip* --- 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. --- *snip* to prove this is actually the case, you could technicaly poke at the OMAP registers to change FCR7:2, SCR7 and TLR7:4. but, that is not a recommended option. if it does work, however, you can do a CPU id check and determine if these can be changed at runtime to provide a fix. (just be sure to change them back). i am not sure if these registers are read only however. thats something for digging in the CPU manuals. --- Aaron Ardiri [EMAIL PROTECTED] CEO - CTO +46 70 656 1143 Mobile Wizardry http://www.mobilewizardry.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
