Bruce, Thanx once again for the quick response. I did some more testing over the weekend and determined positively that the problem lies with the Sena BT device I'm talking to. Even though BT comms is supposed to run at least 1Mbps with a max application throughput of .7Mbps (according to Wikipedia)...

Thanks again for the quick reply and for answering most of my questions. I surmized the 15 instead of 16 bytes at a time from a line I saw in uart.c, something to the effect of " uartTXFIFOcnt = 15; // seems like 16 breaks it " I currently have auto-CTS enabled on the NXP and that's how I'm seeing t...

Bruce, Thanx for your reply from last week; after reviewing the C sources from the latest download, I have a few ?'s: 1. I assumed the relevant pieces are in uart.c & uart.h; is this correct? 2. I noticed in the comments you may be assuming UART1 is connected to P2.0/P2.1; I am using P0.15/P0.16 ins...

Bruce, I am still seeing overflow issues when using TXD1 to transmit data; I have tried your new firmware and have even had a go at directly addressing the NXP UART1 registers, but still seeing some problems. Specifically, I saw no way in the the NXP documentation to tell when the FIFO TXD buffer wa...

Bruce,

Yes, please, I'd like to have the new firmware to try this again; I saw similar behavior to what you are describing in my early tests of v8.20 back in Feb.

I PM'd you regarding this in more detail.

Thanx,
emmette

A while back I started using TXD0/1 in place of SEROUT to take advantage of the hardware UARTs and allow my program to continue working. However, I recently noticed that I was spending a LOT of time in my subroutine that was writing out data and put in some code to calculate timing on TXD1. It appea...