Interesting, but I think in my case I need to rely on small packets. This is because there is no time to bit-bang an interface and ALSO manage a circular buffer, and then move to memory. I'm thinking to just read in data and directly place it into the Keyboard buffer. Once the packet is read - pause and process the Rx data. Ready to send another command then.
The short packet is a form of flow control. TPDD doesn't send data without a command to do so. On Mon, Apr 20, 2020 at 4:17 PM John R. Hogerhuis <[email protected]> wrote: > > > On Mon, Apr 20, 2020 at 1:11 PM Stephen Adolph <[email protected]> > wrote: > >> thanks for looking at that John. >> Yes, motivation is for CP/M and large files. I believe I can get TPDD >> protocol to run on the BCR TTL port since it is half duplex and limited in >> response message size to 128 bytes + a few. >> >> I'm eager to try it out and see how far I can push it. >> >> ..Steve >> > > That's another thing we could do at the same time, add support for larger > packets. > > -- John. > >>
