>> If multiple bytes are transmitted using serial_hw2_int_cts.jal right
>> after another, only the last two bytes are really sent out through the
>> usart.
>>
>> It looks like all the queued bytes are stuffed to TXREG, without waiting
>> for the previous bytes to be transmitted. If there's a delay after the
>> string, while the buffer runs empty, the last two bytes are actually
>> sent out.
>
>What have you done???
>
>Well, serial_hw_int_cts and serial_hw2_int_cts have very similar names, serve
>very similar purposes, share a common API, but looked very different at their
>source code. Having in mind that hw3 and hw4 are soon to be done, I thought it
>would be good to have the code to look alike as possible.
I've never reverted anything before, would have to find out how... You can do
it, if you like. Thanks.
Kiste
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
