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

Not considering increased boot time after flashing ESP32 #526

Closed
gemenerik opened this issue Mar 7, 2025 · 1 comment · Fixed by #527
Closed

Not considering increased boot time after flashing ESP32 #526

gemenerik opened this issue Mar 7, 2025 · 1 comment · Fixed by #527
Assignees
Labels

Comments

@gemenerik
Copy link
Member

bitcraze/crazyflie2-nrf-firmware#102 introduced delayed boot if AI-deck is attached. #510 attempts to take these delays into consideration. However, bitcraze/crazyflie-clients-python#742 shows that this boot delay is not taking into consideration in the restart after flashing the ESP32.

@gemenerik gemenerik self-assigned this Mar 7, 2025
@gemenerik gemenerik changed the title Not always considering increased boot time with AI-deck attached Not considering increased boot time after flashing ESP32 Mar 7, 2025
gemenerik added a commit that referenced this issue Mar 18, 2025
When flashing the ESP, we also reboot the GAP8, requiring the same delay. However, since flashing the ESP firmware does not necessarily mean we are flashing the GAP8, we must explicitly check if the ESP is among our targets to apply the timeout correctly. This ensures the GAP8 is never in an incorrect state.

This fixes #526.

Also adds a missing boot delay in the reset-to-firmware call, originally intended in b7ead19.
@gemenerik
Copy link
Member Author

This triggers the console message: "Failed to flash: Too many packets lost." However, the flashing process completes successfully; the failure occurs when attempting to reconnect, as the we time out before the drone restarts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants