Hello, While working on 18f devices, I noticed that all pin definitions point to LAT registers, e.g.
(18f4550.jal) var volatile bit pin_B5 shared at LATB : 5 While this works great for writing, it does not work for reading out a pin (in stead you'll read back the latched port, set during the last write action, and not the actual port value. So a the current library files / examples that need reading a pin value, where a logical library name is tied to a pin name, e.g. var volatile bit i2c_sda is pin_c4 will fail in the i2c library where a read is done on the i2c_data variable Has anybody thought about these issues and how to deal with them? Albert --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
