If the compiler can't cross a byte boundary it should at least generate an error or a warning.
I think it's a bug because the checksum (at frame:1) is correct. The incorrect value of 47 for the address is the byte at frame:3 and the incorrect value for the data (94) is the byte starting at frame:2. (and it's the remainder when dividing 19,10 and 1 by 8). The compiler should add the offset to the correct byte. -- 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 https://groups.google.com/group/jallib. For more options, visit https://groups.google.com/d/optout.
