Alright, learning as I go here but this is what worked so far.
Shell " stty -F /dev/ttyS5 9600 raw -ixon -ixoff -crtscts cs8 -echo -parenb -cstopb -icanon min 0 time 0"
And I'm able to send data from qb64pe out, and recieve raw characters, without a hang on 'GET' statement waiting for data.
It's amazing how many times I've used com ports for what I considered pretty advanced projects and never asked much questions.
For example i can 'PUT' whatever string i want without error, but can only 'GET' into a numerical byte array.
But, it does work, with this, I can use the orange pi UART serial from qb64 programs.
I will probably arrange a subroutine where it checks several times a second for more data using 'GET', and if there is any just load the rest without delay. that way it's functional and not super CPU intensive.
I suppose theres probably a way to adjust buffer sizes so it needs less checking too, another days project.
Just adding that after the shell stty command, I open the serial device file, in my case /dev/ttyS5. then open as binary.
Shell " stty -F /dev/ttyS5 9600 raw -ixon -ixoff -crtscts cs8 -echo -parenb -cstopb -icanon min 0 time 0"
And I'm able to send data from qb64pe out, and recieve raw characters, without a hang on 'GET' statement waiting for data.
It's amazing how many times I've used com ports for what I considered pretty advanced projects and never asked much questions.
For example i can 'PUT' whatever string i want without error, but can only 'GET' into a numerical byte array.
But, it does work, with this, I can use the orange pi UART serial from qb64 programs.
I will probably arrange a subroutine where it checks several times a second for more data using 'GET', and if there is any just load the rest without delay. that way it's functional and not super CPU intensive.
I suppose theres probably a way to adjust buffer sizes so it needs less checking too, another days project.
Just adding that after the shell stty command, I open the serial device file, in my case /dev/ttyS5. then open as binary.