The flash problems of ai decks

[buabula]

Hello,
Question Description:
I have two AI Decks. One of them ( referred to as Deck A) previously worked successfully with the WiFi Video Streamer example using a JLink debugger, and I was able to retrieve images. However, when I tried to flash other programs via cfloader, the process got stuck. I decided to reflash the WiFi Video Streamer example, but this time, the computer could no longer detect the WiFi. I attempted to redo the process, but flashing the bootloader failed and got stuck.

Then I switched to another AI Deck (referred to as Deck B) and a different debugger (ARM-USB-TINY-H). Using this new setup, I managed to flash the bootloader on Deck B successfully. However, I still couldn't update the firmware via cfloader.

Below are the detailed steps and results of my attempts:

Steps to Reproduce:
Following the tutorial: Getting Started with AI Deck

1. Update the CF2.1 and AI Deck firmware using cfclient
   Firmware version: 2024.10.2 - firmware-cf2

2. Flash the bootloader with the following command:

sudo docker run --rm -it -v $PWD:/module/ --device /dev/ttyUSB0 --privileged -P bitcraze/aideck /bin/bash -c 'export GAPY_OPENOCD_CABLE=interface/ftdi/olimex-arm-usb-tiny-h.cfg; source /gap_sdk/configs/ai_deck.sh; cd /module/; make all image flash'

However, the process got stuck:

I reconnected the battery and the cable to the computer, and then ran the following command, as shown below:

Tried the same process with Deck B:

While it appeared successful, the next step got stuck again:

Setup Details:
AI Deck hardware version: Rev.C1
Crazyflie hardware version: 2.1
no other Decks connected
Platform: Ubuntu 20.04 (not WSL or VM)

OpenOCD Version:

Debugger:ARM-USB-TINY-H
Configuration Files:

（added ‘adapter speed 100‘）

(unmodified file）

Summary of the Issue:
Both AI Decks encounter flashing issues at different steps. I would greatly appreciate any advice or solutions to resolve these problems.
Thank you so much for your time and support!

[buabula]

Additionally, I want to attach two videos for reference: the first shows the hardware while flashing the bootloader using the debugger, and the second shows the hardware while wirelessly flashing via cfloader.

1.mp4

2.mp4

[gemenerik]

Thank you for your post, and I’m sorry to hear you’re having trouble flashing the AI deck.

For future posts, please take a moment to fix the formatting, as some images and a video were not showing, and text was incorrectly highlighted as code or vice versa.

Regarding your issue. It seems the bootloader flashing was successful on "deck B." Can you verify whether the ESP32 was flashed during the firmware update with the client? After updating the NRF and STM32, the drone should detect the decks, restart, and then flash the ESP32, which can take some time.

I’m not sure what you’re attempting with the OpenOCD commands on "deck A." Have you retried flashing the bootloader using the Olimex debugger on that deck? Ensure everything is properly powered during this process.

If you’re still encountering issues, consider turning the system off for a few minutes. Residual electrical charge in the capacitors can sometimes interfere with the proper initialization of the GAP8.

[buabula]

Thank you for your reply, and I am sorry for the formatting errors. I will ensure better formatting in future posts.

I reattempted the flashing process for both decks and found that deck B can now successfully run the WiFi example. However, deck A still gets stuck during the bootloader flashing process. Specifically, while using the same Olimex debugger, I was able to flash the bootloader on deck B without issues, but the process failed on deck A. The current console output for deck A shows the following:

Meanwhile, the console output for deck B displays the following (which may indicate normal behavior):

The purpose of using the OpenOCD commands was to indicate that the process got stuck when flashing the bootloader for deck A and it didn't flash properly, although the connection between the flasher and the computer should be normal. So the commands were mainly to supplement the flashing problem of deck A.

Thank you again for your suggestions. I look forward to your reply!