Joep Suijs wrote:
> I just tested 16f877a_serial_hw_int_cts and it looks perfect to me. I
> tried a few hundered chars and they work okay, just like the space
> that outputs a range of numbers.
>
> I used compiler version ; compiler: jal 2.4j (compiled Mar 12 2009)
>
> What file did you test, on which pic and with which compiler version?
I used 16f88, 2.4j. Maybe it is my test setup. Currently I'm working on
the device files with MPlab 8.30. I'll pickup testing with this lib soon.
> I also checked for fsr use in the library, but did not find it. It is
> of course used in by the compiler when you use arrays and this should
> be handled by the isr routine. I am not realy into asm, but when I
> scanned the resulting asm, I could not find this. I'll take a look
> into this later, but I regard the risk that FSR gets corrupted is
> quite low and can not explain why it goes wrong most of the time. (But
> it could give a failure every now and then in a production situation
> which is very dificult to track).
I have 2 changes in mind: combine the 2 interrupt procedures to one
(there is already a interrupt-type test in each, so it is easy to
combine, and the code will be somehat more efficient). And secondly add
save/restore of FSR, even though the chance on corruption may be
minimal. The C-compiler I used (cc5x) has a nice feature: it doesn't
automatically save FSR, but produces a warning when FSR is used in the
interrupt routine.
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
-~----------~----~----~----~------~----~------~--~---
