Bitcraze Forums

Well to steps forward and one back :). I'm thinking there is still something wrong with the i2c buss then. If you flash the release software I guess everything is working as it should (to rule out cfclient issue)? Yes, with the original firmware everything's fine. Didn't even change the cfclient. I...

I set the I2C1 bus (for EEPROM and sonar) to 100 kHz and the copter starts up normally. The LEDs are acting as the are supposed to and I get a stable connection. Pushed the changes to my repo. But: The telemetry data in the PC Client is still showing weird values (e.g. the ASL). Neither the data fie...

You could always try to run it slower to see if it changes anything. I found this in the datasheet: Pin 5-SCL (I2C Clock): This is the clock line for I2C communications. These sensors support I2C clock frequencies up to 400kHz provided clock stretching is supported by the master device. Without clo...

OK, I did some SWD debugging and I found a bug . The ST I2C library (CPAL) get stuck in a timeout. This happens when there isn't anything to communicate but works if things run as it should. So I'm thinking you aren't getting any answer from the sonar sensor? I tested just changing the MB1242 drive...

Hey tobias,

thanks for jumping in. Here you have my sonar-cf2 branch holding the CF 2.0 port of my original CF 1.0 sonar implementation (that you know already... ):

https://github.com/alexriegel/crazyflie ... /sonar-cf2

Pushed the change to I2C port I2C1_DEV some minutes ago.

Still testing... :cry: Changed the code for the sonar sensor to I2C1_DEV, but without initializing the bus. This is already done at system start for accessing the EEPROM. After startup, the red heart beat flashes two times before it stays dark completely. Only the two blue LEDs are constantly switch...

Glad I was able to help.

Nominal flight time for the CF 1.0 is about 7 minutes, but it depends on your flight style, of course. No further experience with battery wear since I'm developing most of the time...

Hi all, You can skip this part: I havent touched my Crazyflie 1.0 for about a year and since the weather here is improving I thought I'd pick it up again and do some flying. So I've updated the firmware of the Crazyradio to work on my new Macbook. Then I flashed the latest available binary firmware...

Getting closer: I need to use I2C3_DEV instead of I2C2 (CF 1.0). Now the firmware compiles without warnings, finally. Furthermore, I initialized I2C3_DEV a second time by mistake although it has already been initialized in imu_cf2.c . Fixed that. The CF 2.0 can be found and connected with the PC Cli...

Ok, after flashing my custom firmware again without the sonar connected via I2C, the CF restarts in firmware mode correctly. I assume that flashing with the sonar deck attached to the copter caused the problem. Now it throws the console/LED errors you already described above. Have to get the I2C wor...