You want one set of pullups to 3.3v on the i2c bus, the ones on the Raduino for the si5351 are sufficient for this.
toggle quoted messageShow quoted text
That i2c bus is relatively slow, if you load it down with traffic from Nano to Teensy it may become too slow.
At that point, I'd recommend completely replacing the Nano with the Teensy somehow.
Maybe sooner, as it is usually easiest to just have all firmware on one processor.
W0EB reports that they have the Teensy driving the uBitx, available as a kit:
That sounds like a great way to go.
On Thu, Oct 10, 2019 at 04:43 AM, Rob French (KC4UPR) wrote:
I am looking to have multiple devices communicating via I2C with my stock Raduino. Currently, I have of course the Si5351 on the Raduino, and I also have an I2C backpack on my slave. The I2C backpack is a 5v unit, so I have removed it's onboard SDA/SCL pullup resistors, and so it shares the two 2.2k resistors on the Raduino.
I am about to add a Teensy 3.2 into the mix, communicating as an I2C slave with the Raduino. The Teensy documentation mentions that external pullups are required when using I2C. I *think* this can also be the 2.2k resistors on the Raduino, but I just want to make sure. Am I correct? (Essentially the Teensy would be hooked up similarly to the second Arduino in this KD8CEC drawing, albeit with additional functions.)