Hi all! Yes, I am probably the one to blame, but I'll be busy the next week. If anyone has the time and energy to have a look or confirm the bug:
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. I've seen this bug on 18F26K22 and 18F45K22. I'll look into this myself as soon as I have the time, just didn'n want to delay a release, nor release a buggy lib. It may well be that a wrong bit is checked (e.g. one belonging to the first usart), but I haven't found any wrong reference. Greets, 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.
