[RobH]
>> The last couple of days I have been struggling to get a simple RS232Â
>> library working. I have the intention to put this library in Jallib, butÂ
>
[Eur]
> serial_hardware.jal works. I've come to appreciate it.
There are different implementations for RS232 support:
- bitbanging
- USART polling (without interrupts)
- USART with interrupts, unbuffered
- USART with interrupts, buffered
- USART with interrupts, buffered and automatic CTS flow control
And then there are differences in available functions for the
application: some are simple and rigid, some are suffisticated and
flexible. Not every lib is suitable for every application (for example
because of memory or cycle constraints), so it is good to have several
libs available. But we probably need a table of features for users to to
be able to select the proper library.
The library I'm working on is of the type of the last in the list above.
It has currently only 2 application program functions: send_byte() and
receive_byte(). It is meant for an application which is very busy and
has limited time slots to process commands from the PC application.
Regards, Rob.
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---
