Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log variables kill firmware #73

Closed
pPatrickK opened this issue Jun 21, 2018 · 2 comments
Closed

Log variables kill firmware #73

pPatrickK opened this issue Jun 21, 2018 · 2 comments

Comments

@pPatrickK
Copy link

Hi,

we tried to add some sitAw Log variables which were commented in the
https://github.com/USC-ACTLab/crazyflie-firmware/blob/ca2882b874d8e4f57eea53f06e6864eb68a895cb/src/modules/interface/sitaw.h#L65-L67 .
It was still possible to build the firmware but after we've flashed the one blue and both red leds were solid.

After re flashing without these changes the drone was working like usual.
Do you have any hints what causes this behavior ?

best regards
Patrick

@whoenig
Copy link
Contributor

whoenig commented Jun 21, 2018

This is most likely caused by this issue in the original firmware: bitcraze/crazyflie-firmware#313. If you only log to uSD-card, you can remove the check here: https://github.com/USC-ACTLab/crazyflie-firmware/blob/crazyswarm-next/src/modules/src/log.c#L194. Otherwise, I recommend getting rid of some logging variables that you don't need.

This is on my plate to get fixed, but will probably take another 2 weeks or so, since it's a bug that affects the official firmware and all clients.

@whoenig
Copy link
Contributor

whoenig commented Dec 7, 2018

This has been fixed.

@whoenig whoenig closed this as completed Dec 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants