[SOLVED] Error when using the address 0xE7E7E7E7E4

Post here to get support
Post Reply
sAz
Beginner
Posts: 27
Joined: Wed Jun 10, 2020 5:35 pm

[SOLVED] Error when using the address 0xE7E7E7E7E4

Post by sAz »

Hi everyone,

I am connecting to 6 drones at the same time. When I use the address 0xE7E7E7E7E4 for one of the drones I get the messages below. These messages are prompted non stop so I have to press ctrl+c to stop the program.

Code: Select all

[2] SYS: -------------------------
[1] SYS: -------------------------
[3] SYS: -------------------------
[0] SYS: -------------------------
[0] ---

[2] ---

[1] ---

[3] ---

[2] SYS: Crazyflie 2.1 is up and r
[1] SYS: Crazyflie 2.1 is up and r
[2] unning!

[1] unning!

[2] SYS: Build 9:414c0363bb76 (202
[0] SYS: Crazyflie 2.1 is up and r
[3] SYS: Crazyflie 2.1 is up and r
[1] SYS: Build 9:414c0363bb76 (202
[2] 0.06 +9) MODIFIED

[3] unning!

[1] 0.06 +9) MODIFIED

[2] SYS: I am 0x203937434848501500
[3] SYS: Build 9:414c0363bb76 (202
[1] SYS: I am 0x203937434848501600
[2] ash!

[3] 0.06 +9) MODIFIED

[1] ash!

[2] CFGBLK: v1, verification [OK]

[0] unning!

[1] CFGBLK: v1, verification [OK]

[0] SYS: Build 9:414c0363bb76 (202
[3] SYS: I am 0x203937434848500D00
[3] 47003E and I have 1024KB of fl
[0] 0.06 +9) MODIFIED

[3] ash!

[0] SYS: I am 0x203937434848501700
[3] CFGBLK: v1, verification [OK]

[0] 1A0040 and I have 1024KB of fl
[3] DECK_CORE: 1 deck(s) found

[0] ash!

[3] DECK_CORE: Calling INIT on dri
[0] CFGBLK: v1, verification [OK]

[3] ver bcLighthouse4 for deck 0

[0] DECK_CORE: 1 deck(s) found

[0] DECK_CORE: Calling INIT on dri
[3] IMU: BMI088 Gyro I2C connectio
[3] n [OK].

[0] IMU: BMI088 Gyro I2C connectio
[0] n [OK].

[3] IMU: BMI088 Accel I2C connecti
[3] on [OK]

[0] IMU: BMI088 Accel I2C connecti
[3] IMU: BMP388 I2C connection [OK
[0] on [OK]

[3] ]

[0] IMU: BMP388 I2C connection [OK
[0] ]

[3] ESTIMATOR: Using Kalman (2) es
[3] timator

[0] ESTIMATOR: Using Kalman (2) es
[3] CONTROLLER: Using PID (1) cont
[0] timator

[3] roller

[0] CONTROLLER: Using PID (1) cont
[3] MTR-DRV: Using brushed motor d
[0] roller

[3] river

[0] MTR-DRV: Using brushed motor d
[0] river

[3] EEPROM: I2C connection [OK].

[3] IMU: BMI088 gyro self-test [OK
[3] ]

[0] EEPROM: I2C connection [OK].

[0] IMU: BMI088 gyro self-test [OK
[0] ]

[3] SYS: The system resumed after 
[3] watchdog timeout [WARNING]

[0] SYS: The system resumed after 
[3] SYS: Hardfault. r0: BEAF7882, 
[0] watchdog timeout [WARNING]

[3] r1: 3F2257E9, r2: BD4AE6BA, r3
[0] SYS: Hardfault. r0: BF144B52, 
[3] : BB56C7C8, r12: BD4AE6BA, lr:
[0] r1: 3F8C360B, r2: BD604505, r3
[3]  3F2257E9, pc: 8009F2C, psr: 2
[0] : BB56C7C8, r12: BD604505, lr:
[3] 1000000

[0]  3F8C360B, pc: 8009F2C, psr: 2
[0] 1000000

[2] OW: Cmd 0x22 timeout.

[1] OW: Cmd 0x22 timeout.

[2] DECK_INFO: Reading deck nr:0 [
[1] DECK_INFO: Reading deck nr:0 [
[2] FAILED]. No driver will be ini
[1] FAILED]. No driver will be ini
[2] tialized!

[1] tialized!

[2] DECK_CORE: 0 deck(s) found

[1] DECK_CORE: 0 deck(s) found

[2] IMU: BMI088 Gyro I2C connectio
[2] n [OK].

[1] IMU: BMI088 Gyro I2C connectio
[1] n [OK].

[2] IMU: BMI088 Accel I2C connecti
[2] on [OK]

[1] IMU: BMI088 Accel I2C connecti
[2] IMU: BMP388 I2C connection [OK
[1] on [OK]

[2] ]

[1] IMU: BMP388 I2C connection [OK
[1] ]

[2] ESTIMATOR: Using Complementary
[1] ESTIMATOR: Using Complementary
[2]  (1) estimator

[1]  (1) estimator

[2] CONTROLLER: Using PID (1) cont
[1] CONTROLLER: Using PID (1) cont
[2] roller

[1] roller

[2] MTR-DRV: Using brushed motor d
[1] MTR-DRV: Using brushed motor d
[2] river

[1] river

[2] EEPROM: I2C connection [OK].

[2] IMU: BMI088 gyro self-test [OK
[1] EEPROM: I2C connection [OK].

[2] ]

[1] IMU: BMI088 gyro self-test [OK
[1] ]

quit[2] SYS: The system resumed after 
[2] watchdog timeout [WARNING]

[1] SYS: The system resumed after 
[2] SYS: Hardfault. r0: BE86BBFF, 
[1] watchdog timeout [WARNING]

[2] r1: 3F6CB34E, r2: BD4AE0AD, r3
[1] SYS: Hardfault. r0: BF313F50, 
[2] : BB56C7C8, r12: BD4AE0AD, lr:
[1] r1: 3F3DD629, r2: BD632E02, r3
[2]  3F6CB34E, pc: 8009F2C, psr: 2
[1] : BB56C7C8, r12: BD632E02, lr:
[2] 1000000

[1]  3F3DD629, pc: 8009F2C, psr: 2
[1] 1000000
That occurs only when I use the above address and only when I try to fly multiple drones. When I fly only one drone with this address I get the message below but I am able to fly the drone.

Code: Select all

[4]   phase0: 0.043792

[4]   phase1: -0.021377

[4] Got calibration from A810FE05

[4]   phase0: 0.022644

[4]   phase1: 0.003971
Does someone have any idea where to start?
Last edited by sAz on Sun Jan 31, 2021 12:46 pm, edited 2 times in total.
whoenig
Expert
Posts: 395
Joined: Mon Oct 27, 2014 2:55 am

Re: Error when using the address 0xE7E7E7E7E4

Post by whoenig »

The hardfault indicates that the firmware crashed for some reason. Could you please provide some more details on how you are running the experiments? In particular: 1) which firmware version are you using?, 2) How are you connecting to the Crazyflie (Python lib, crazyflie_ros, Crazyswarm)?
sAz
Beginner
Posts: 27
Joined: Wed Jun 10, 2020 5:35 pm

Re: Error when using the address 0xE7E7E7E7E4

Post by sAz »

This behaviour occurred because of an error in the code. I was trying (unintentionally) to access an array out of bounds.

To answer your questions:
1) I am using the version from 2020.06.
2) I am using the python-lib.
Post Reply