-
Notifications
You must be signed in to change notification settings - Fork 48
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
CFloader flash img hangs at 99% with the classification demo #104
Comments
So after investigations it seems that any binary file larger than 747776 Bytes fails with the cfloader (getting stuck at 99%), and the classification example is 747792 Bytes large! This was possible to flash before... so what changed? The docker file itself hasn't changed, but perhaps the autotiler that needs to be pulled with that version is updated somehow? |
I also tried this binary file (can be downloaded through the following Google Drive link): This binary file is a CNN pytorch neural network, quantized by nemo and compiled by dory. It seems that although it is |
Hmm interesting! Where are you currently with the firmware of the aideck+ crazyflie? release 2022.09 or latest development branch? Will try this binary out soon. Yes I agree, it would be really weird if the filesize was the case, as it should be able to handle 60 MB or something like that? |
Oh wait I see that you answered my question on https://github.com/orgs/bitcraze/discussions/369 already. hmmmm really strange! The plot thickens... but we need to investigate this more. Thanks for sharing though! |
Other examples are 1000 bytes works |
Discussed in https://github.com/orgs/bitcraze/discussions/369
Originally posted by chengliu-LR November 7, 2022
Hi all,
I am using cfloader to flash some
target.board.devices.flash.img
to AI-Deck. For typicalimg
s like thewifi-demo
andpulp-dronet
, it works perfectly. However, when it comes to theclassification-demo
and my own compiled programs, the cfloader hangs at\ 99% Writing to bcAI:gap8 deck memory
everytime. Do you know possible reasons for this?Thank you!
The text was updated successfully, but these errors were encountered: