[CF21-BL, AI Deck] AI Deck firmware update stuck at “Updating deck bcAI:esp”

[stevdan]

Environment

• Hardware: Crazyflie 2.1 Brushless (CF21-BL) with AI Deck attached, Crazyradio Dongle
• Host: Windows 11 (latest updates)
• Power: Tried via USB, battery, and both
• cfclient version: 2025.2

Issue
Hi, I’m following the Getting Started with the AI Deck tutorial: https://www.bitcraze.io/documentation/tutorials/getting-started-with-aideck/ During the firmware update, the process gets stuck at: "Updating deck bcAI:esp"

I tried flashing the Wifi example too. The progress stays at 0%:

| 0% Writing to bcAI:gap8 deck memory

Interestingly, after restarting the Crazyflie, the “WiFi streaming example” network does appear in my WiFi list.

Steps I tried

• Started the firmware update via cfclient with only the AI Deck attached → stuck at “Updating deck bcAI:esp”.
• Tested with/without battery and with/without USB cable (various combinations).
• Retried flashing multiple times under different conditions.
• Also tried mounting the AI Deck in different positions (bottom, top).

Expected behavior

• All three MCUs (STM, NRF, ESP) should be re-flashed.
• The ESP update (“bcAI:esp deck memory”) should complete in ~3 minutes.
• Console tab should show something like: "ESP32: I (910) SYS: Initialized."

Question

1. Has anyone seen this issue before? Is there a known fix or workaround for the ESP flashing process and the wifi example?

[gemenerik]

Thanks for reporting this bug, I can reproduce it. You may be able to skip the ESP flashing step, since the ESP gets flashed in production Otherwise you can flash it over JTAG following the instructions in the repository.

[stevdan]

Thanks for the clarification, that makes sense.

I went ahead and skipped the ESP flashing step (where the update always got stuck) and moved on to the Flash WiFi Example from the tutorial:
Getting Started with the AI Deck – Flash WiFi Example.

However, when I attempt to flash aideck_gap8_wifi_img_streamer_with_ap.bin, the process consistently still hangs at 0% (same as before).

In the tutorial, there’s a note about some AI Decks being shipped with an older bootloader that prevents OTA flashing. The symptoms I’m seeing seem to match that description, which makes me wonder:

• Does this indicate that my AI Deck might have been delivered with the old bootloader?
• If yes, what is the recommended next step? Do I need to send the deck back for replacement or is there another workaround?

Thanks again for your support!

[gemenerik]

The next step in the getting started guide is to flash the GAP8 bootloader over JTAG: https://www.bitcraze.io/documentation/tutorials/getting-started-with-aideck/#gap8-bootloader

That should allow flashing OTA.

[stevdan]

Thanks for the explanation. Unfortunately, I do not have a JTAG programmer. As the current bootloader prevents me from using the deck as described in the documentation, could you please advise if the unit can be exchanged for one with the updated bootloader or if it is possible to send it back for reflashing?

That would really help us move forward. Thanks in advance for your support!

[gemenerik]

The JTAG debugger is a required tool for working with the AI Deck throughout development, not just for initial setup. The bootloader can break and need reflashing via JTAG. Beyond that, JTAG flashing is much faster than OTA, especially for larger applications like CNNs, and the debugger provides capabilities that are essential for development work.
That's why the debugger is listed as required on our store and product pages. Exchanging or reflashing your unit wouldn't solve the underlying issue - you'd likely run into the same issues later. I understand the confusion - some of our documentation suggested the debugger is only needed "once," which isn't quite accurate.I'm updating the wording.

[stevdan]

Thank you for clarifying. That makes sense now. I see why the debugger is considered an essential part of the workflow rather than just a one-time setup tool.
I appreciate that you’re updating the wording to make this point clearer for future users.
Thanks for your kind support!