No this is very helpful. I haven't tried the other I2C ports so will test them out too as well as your other suggestions.
For 2), the Portenta I2C through the breakout board is 3.3v and is using Pin->Qwiic...
Not a problem and happy to elaborate.
I'm using an Arduino Portenta as the Master on an I2C bus with all the other devices as Slave one of which is this Teensy setup. The bus runs at 3.3V as all devices either only...
No, I don't see the same issue occuring with the samples. I am realising there is something in the program written, i just can't understand what might be causing it though.
Specifically why would that chip on the...
While I can't share the software (unreleased project i'm contributing to), the odd thing is that has occured across two shields only when using I2C in slave. When using the serial pins or just USB, it hasn't occured...
Good question,
The shield is mounted underneath with/without the Sparkfun I2C shield in between (I’ve isolated it from the test and it appears to not be a factor)
The increase in temp happens within 5-10s with ...
Hi everyone,
I've got a overheating issue occuring that resulted in the loss of two Audio Shields Rev D and the issue is difficult to reproduce.
Using the teensyDuino 1.57 on a TeensyBoard 4.1 with Audio Shield...
@PaulSoffregen I switched to the Richard-Gemmell I2C and repointed the Audio.h libraries to that instead of Wire and this has restored I2C connectivitiy while using I2S Output
...
@PaulSoffregen, I'm stumped as to why this is happening. Board responds to I2C commands when the AudioOutput is PWM or others but not I2S.
On Teensy 4.1 with Audio Shield
#include <Audio.h>
#include <Wire.h>...
This line appears to be conflicting with the I2C onRecieve
AudioOutputI2S i2s2;
If i comment it out, the I2C works but if I put it in, it prevents the communication.
Teensy as Slave Code
#include <Audio.h>...
@PaulSoffregen it's worth noting that I still get more errors than other boards but it is massively reduced when shielding the wires and removing nearby potential interference.
Update: I think it is safe to say this is a user/hardware issue not a software/firmware issue.
I replaced the I2C cables and rewired with untwisted cables between the I2C shields and it is communicating strongly now...
@tonton81 Switched it over and repeated the test but got the same results :(
Also I tested directly with Sparkfun I2C shield and same results. Works great as the master, horrible as the slave.
Hi Paul,
Updated to 1.57 and still no luck.
Test setup is msg#1 with the Portenta as the "Master" Script above and the teensy with "Slave" Script. i've attached an image of the teensy on the breakout board...
@PaulSoffregen I2C is running ok however I'm getting a lot of bad character read and transmission. I've isolated and tested with Teensy 4.1 and other boards in identical configuration however while all other boards get...
Find latest posts