Hi David,
Thank you for this input. That is extremely helpful! Knowing it is
asynchronous, I can go ahead and add the support. I'll get started on
the PR right away.
By the way, as I understand it, Unix-like OSes do not support delivering
BREAK to the application either. It's not just a limitatio
Hi Nathan,
As far as I know Breaks are Asynchronous (not buffer)
By definition: a BREAK is a Start bit that lasts for more bit times then the
configured word size, parity and stop bit times. This is how the receiver
detects it.
AFAIN NuttX can not propagate the reception of the break to an App a
Hello,
Indeed the "proper" way of including a script would be to store it in a
file system.
However, when I needed to include a single and small script and I didn't
want to introduce a complete FS just for this, I used xxd.
xxd can convert any file to a C header file.
You can then include the he
Hi Alan,
Thanks for those links. FreeBSD does have excellent docs.
The 0.25 second to 0.5 second Breaks and >1.6 second Breaks discussed for
Unix-like systems are an artifact of the old school teletype systems and
that will work fine for my project right now.
But technically a Break is any seque
Hi David,
If I understand correctly, if there is ongoing transmit of data that was
previously buffered, this will mask it?
In other words, if O_NONBLOCK and the application does something like:
write(...);
ioctl(TIOCSBRK);
write(...);
then the Break will not necessarily be transmitted between t
There are at least two types of breaks, from previous link:
"In modern systems there are two types of Break signals. If the Break
is longer than 1.6 seconds, it is considered a "Modem Break", and some
modems can be programmed to terminate the conversation and go on-hook
or enter the modems' comman
