Hi Joep, I agree with your concerns, especially the testing that would be required.
Would it be OK to add a new, separate i2c_reset.jal library to JALLIB? This should not impact any existing projects, and later on, it could be folded into i2c_hardware.jal, if desired. If not OK, then , I will keep i2c_reset.jal off-line. Thank you, William On Friday, March 28, 2014 12:52:01 PM UTC-5, William wrote: > > Greetings, > > I tend to make dumb mistakes while I am working with a new / unfamiliar > i2c slave chip. At some point, I can get the chip confused such that I > have to resort to turning off the power on the board. SDA is 'stuck' low. > > However, when using i2c_software.jal, its version of i2c_initialize() will > reset/clear away the problem. > > What I am doing wrong with i2c_hardware.jal? > > As a stop-gap measure, in a local directory here, I have copied > i2c_software.jal, to a new file, i2c_reset.jal, and stripped out every > thing but i2c_initialize(), and renamed the function to i2_reset(). I use > it just for reset, and use i2c_hardware.jal for everything else. This > approach seems to be working so far. > > Suggestions welcome! > > William > > -- 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. For more options, visit https://groups.google.com/d/optout.
