Could not get flight data from CF2(firmware 2017.05)

Discussions about all things Bitcraze
Post Reply
tianhelight
Beginner
Posts: 4
Joined: Sun Jun 18, 2017 12:48 am

Could not get flight data from CF2(firmware 2017.05)

Post by tianhelight »

Hi all,

I am now facing a problem when I reflashed CF2 to the recently firmware.
When I connect the Client to CF2,I can only get the battery and link quality data, but can not get the flight data!
I use the Android Client, also can not Control the CF2.
I try to use the recently Client,The problem persists.
I flashed the CF2 back to firmware 2016, everything is OK again.

Can somebody tell me why?

Thank you for your time and support,

Tianhelight
arnaud
Bitcraze
Posts: 2538
Joined: Tue Feb 06, 2007 12:36 pm

Re: Could not get flight data from CF2(firmware 2017.05)

Post by arnaud »

Could you send the link to the exact firmware file you are using? I just tried and I cannot reproduce the problem here.
tianhelight
Beginner
Posts: 4
Joined: Sun Jun 18, 2017 12:48 am

Re: Could not get flight data from CF2(firmware 2017.05)

Post by tianhelight »

hi arnaud,
I downloaded the bin firmware from https://github.com/bitcraze/crazyflie-firmware/releases,and flashed the firmware by STM32 ST-LINK Utility,I set the flash start address to 0x08004000.The CF2 start ,I can only get the battery and link quality data, but can not get the flight data! also can not control it.

I tryed different firmware from git,I found after the summit d38113b8ac58f9191b0fc956036c5fcad4c15045 [d38113b] by Tobias Antonsson (Sensors task moved to HAL and made as common interface to get sensor data),the firmware can not work normally.Before the point,the firmware work well.

Can you tell me why,what should I do?

Thanks!
arnaud
Bitcraze
Posts: 2538
Joined: Tue Feb 06, 2007 12:36 pm

Re: Could not get flight data from CF2(firmware 2017.05)

Post by arnaud »

Are you sure that the bootloader is still flashed in your Crazyflie? When flasing with a debugger it is often that the debuger will damage the bootloader so we usually either flash firmware with the debugger without bootloader support (at address 0x08000000 then), or we keep the bootloader in place and work by flashing using the radio bootloader.

It is very strange that you are seeing difference between commit though. Do you have a config.mk setting custom flags?
Post Reply