You can pass a pin in a procedure, by making it volatile. But then all I2C procedures in the call stack need to pass this pin to each other.
i2c1_start and i2c2_start, etc are probably easier. Still a lot of work. You can use the same register names, but not the same low-level routines. Sent from my iPhone > On 5 feb. 2014, at 14:22, Vasile Surducan <[email protected]> wrote: > > I've noticed that using the i2c_hardware for PIC's with two I2C interfaces > is difficult, a lot of aliases are required for all registers. > > Last time I've duplicate the i2c lib in two custom libraries every with it's > own register names. > > Do you have a better idea? > > thx, > Vasile > -- > 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/groups/opt_out. -- 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/groups/opt_out.
