Replies: 5 comments 7 replies
-
I don't have an answer for this but figured I add my experience as it's similar. I also see a discrepancy with that 910 number from the tutorial. I've got the Crazyflie 2.1 and the AI-deck 1.1. I'm not sure how to determine the revision, though. My output looks like this:
Initially, when trying to flash the WiFi Example, it would fail arbitrarily at different percentages when flashing. I had the Flow v2 deck attached and ignored step 2, which says, "Make sure that only the AI-deck is attached to the Crazyflie, with no other deck." As soon as I removed the flow deck and retried the flash, it flashed to 99%. And it does this repeatedly if I retry, always stopping at 99%. If I try I ended up stepping through the code during the flash and found that the flash actually reaches 100% and then exists with Unfortunately, the |
Beta Was this translation helpful? Give feedback.
-
Hi @NSombekke, Sorry that you are having these problems. I'm just asking some extra questions to get some clarification
|
Beta Was this translation helpful? Give feedback.
-
So, first of all, the 25 min over air flash time of the esp firmware is quite worrying but I see why that is from your debug information:
Could you change the radio properties with these instructions? Select 2MBit/s and perhaps also change the radio address to be E7E7E7E701 to be sure that we don't have the issue described int #57. Then restart the crazyflie and go through the entire tutorial again. Also just to be sure, let's try the latest release of the cfclient, as your debug information indicate that you are running from the latest source,
Let us know how this goes |
Beta Was this translation helpful? Give feedback.
-
Not sure what is going one, but one of the things you can try some firmwares first, so hopefully we can avoid you using a programmer to fix things:
Then try to flash the binary for the wifi streamer again. In the mean time a question: Do you have an olimex or jlink programmer at your disposal just in case this doesn't work? |
Beta Was this translation helpful? Give feedback.
-
In a previous thread you mentioned that you use a virtual machine, which is displaying communication performances if not optimized for use. There are some tips to improve that: https://github.com/bitcraze/bitcraze-vm The best would be to do aideck development from a computer with a native ubuntu install. WSL2 (windows subsystem for linux) on window10/11 works too actually if you want some instructions for that. |
Beta Was this translation helpful? Give feedback.
-
Dear community,
I have been working with the Crazyflie 2.0 for the last couple of weeks and I finally got my hands on the AI-deck 1.1 (Revision D). I followed the getting started with AI-deck tutorial and updated the firmware of both the Crazyflie and AI-deck (through the cfclient bootloader on the bitcrazeVM) to version 2022.05. This actually took around 25 minutes (not the indicated 3 minutes).
When reconnecting the Crazyflie to the cfclient the console showed (besides other things):
ESP32: I (871) SYS: Initialized
ESP32: I (881) DISCOVERY: Hostname is aideck-E0E3DC
The first one differs from
ESP32: I (910) SYS: Initialized
which can be found in the getting started tutorial, why this difference and is this a problem?I continued with the tutorial as it did seem to work (apart from the difference mentioned above). Because I have revision D of the AI-deck I assumed I did not have to flash the bootloader on the GAP8 seperately but when continuing with the Flash Wifi example I faced new problems, similar to #57. The proposed solution in #57 did not seem to work as flashing kept being stuck at 0 or 2 percent. After being stuck for a while the Crazyflie seems to restart (the usual beeping sound and spinning rotors). Does anyone have a solution for this as it has been frustrating me for days now.
Beta Was this translation helpful? Give feedback.
All reactions