Bitcraze Forums

Is this problem solved? I have the same problem with Alex when I connect my RGB sensor ISL29125 into I2C2 port. I doubt that there is something wrong with the I2C in the extension header. I was able to log the value if I hard-coded it in the firmware but when I tried to read the sensor data, it sim...

tobias wrote:We have been insanely busy, sorry for not replying.

We have had the I2C2 bus working with other sensors but we have so many clones of the FW that I don't know which one it is. We will do our best to try and solve this today.
/Tobias

Sounds promising, any news so far?

Come on, guys, I'm really stuck with this project, did someone have a look at it? Has someone ever managed to communicate with an external I2C sensor via the expansion port? Sorry for asking with importunity but it's really frustrating to cope with basic things like this for weeks. :cry: :? In the n...

Thanks to the dedicated help of the watterott.com service team, we narrowed down the problem: The sensor itsself is working fine. The wiring on my breadboard is correct, too. (the pictures in my CF gallery are outdated) My code for requesting and reading measurements from the sensor is ok, including...

Here's a quick status update: Did some measurements with a multimeter. I assume that the sensor has a defect since it consumes 0 mA during operation. According to the datasheet it should have an idle current consumption of around 2.7 mA, which obviously isn't the case. I sent it back to the vendor h...

Hi Alex! Are you sure you are using the latest code from the repo? Here is the code for the I2C2 interrupt handler. Yes, I am absolutely sure, double-checked that again. Both master branches are identical. Overlooked that interrupt handler for I2C2 before. Some days ago, I managed to eliminate the ...

tobias, I wrote some dirty debug code using the on-board LEDs and found out that neither i2cdevWriteByte nor i2cdevReadByte return TRUE, i.e. these functions fail. After stepping through the I2C interface with brain 1.0 (rooting address and data bytes through the function calls, looking how they are...

arnaud wrote:Since we run on a little endian machine you are safe setting the log in unsigned 8 bits, it will send 1 or 0 depending of the bool value. I would guess bool is 32bit wide but I'm not sure.

Ok, I will try to track down the issue with the help of your input.

This sounds like it is crashing somewhere when reading the sensor. It could help to look at the I2C lines to see if there is any communication going on. Also lighting up an LED just before reading a range value and lighting off just after will tell you if it crashes in this part of the code or some...

As for the crash at startup I do not see it, when flashing program from your branch my Crazyflie starts normally. It may be related to the presence of the I2C device. The best would be to see where it crash exactly, do you have a jtag debuger? Otherwise I would use the leds: lighting up led at diff...