Forum Discussion
Factory reset Vision AI Developer kit does not work
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
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?
i'm running it in the v.05330_Perf folder!
Befor i start any script the camera is connected to WIFI and IoT Hub and all 4 docker containers are running.
Workflow Nr.1:
1. Open the v.05330_Perf folder in Explorer
2. Right Click on FastbootUpgrade.bat
3. execute as administrator
4. Got this error (Here the screenshot where the C path is visible):
Workflow Nr 2 (See all in the following Screenshot):
1. Open CMD as a administrator
2. cd to the v.05330_Perf folder
3. start the .bat
4. Upgrade Fail
So it actually goes further from the command line and doesn't complain about the abl.elf. What happens in the scenario is that the device reboots to bootloader mode. It seems you press "any key to continue" before USB recognizes the device again. If you have sound on in your computer you should hear a sounds when the USB disconnects (device reboots) and then another sound when USB founds the device again. It's safe to continue after that.
Having said that I have recently seen a case where the device is never recognized again. I asked developers about it and only root cause we know is that "it's USB cables fault" (and it's not 100%). So I'd recommend to try again and wait for the USB to recognize the device again after the reboot. If that doesn't happen try switching the USB cable if you have options.