You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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.
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.
The text was updated successfully, but these errors were encountered: