Forum Discussion
Factory reset Vision AI Developer kit does not work
MarcoWirtlYou may try upgrading the firmware https://azure.github.io/Vision-AI-DevKit-Pages/docs/Recover_device/
That resolved our issues
Hey Guys,
- Devices is attached
- Current Version (Shipping version) : v0.4940_Perf
- Is connected to WIFI and Azure IoT Hub
- All 4 Modules are on the camera (adb shell docker ps)
Running on Windows PC i copy the "FastbootUpgrade_v6_5.bat" + "VisionAIDevKit_InstallCheck.bat" File from the FW_UpgradeScript_Windows_v6_5 in the v0.5330_Perf Folder (where or what is the flat images folde in the PDF mentioned? / folder that contains the actual firmware files?)
--> see Screenshot 1
In this case when i run the FastbootUpgrade.bat i get an error (../v0.5330_Perf/abl.elf is missing(X) --> Screenshot 2)
Can anyone help?
If you run the scripts in the same folder than where the firmware is you'll need to change this row in Fastboot script to look like this:
The script structure keeps changing between the firmware updates so the instructions might unfortunately be outdated
Info: My machine is a windows machine!!
When i run the Linux Script (just intuitation because the Kit is running Yocta Linux) instead it finds the abl.elf file and start, it runs until the Install Check Script and prints:
It stucks on this point!
I've never done this on Linux, but you could try to comment out the "rm device.log" from the upgrade script? It seems to only be used to check if the device is connected
Changed the .bat file like this (also tried fw_path= BLANK):
When i run i got the same error:
My folder looks like this:
Also settedmy enviroment var to the oath of my plattform tools:
So can you help me?
I honestly don't know where the problem lies. I changed the abl.elf file name in the script to abl.elves and got the same error starting ./abl which indicates that you configuration is correct. When I changed the script back to search to abl.elf it works.
The only thing I can think of is that you are not running it in the v.05330_Perf folder but in the folder where the script is originally located. But I am sure you've checked that. Just to out rule that can you take a screenshot where your C: path is visible when you execute FastbootUpgrade_v6_5.bat?
