Re: Firmware v1.10 Release Notes
Dear Ken,
The firmware 1.10 upgrade does not behave any different than its predecessors, because the bootloader has never changed. It is known that USB sticks can have rather odd response timing when being prompted by the boot-loader, which is covered by generous time frames in which replies are expected. You can experience this often when connecting sticks to the PC and the times for mounting it may vary considerably. The X32 bootloader is allowing for 1.5 sec until the USB drive has to signal that it is there at all (which btw is much longer than the USB spec requires). Then the stick has a total of 5 sec to get itself prepared for reading. If the bootloader cannot find any suitable update file during that time, it would just start the regular boot process with the previous firmware.
When a suitable update file is found, the message 'checking integrity' will be displayed and the file is loaded. When the check is successful, the firmware will be exchanged and used for booting with the new version. When the check fails, the data will be discarded and the X32 will boot the previous firmware version.
In your example obviously the stick responded timely and a suitable update file was present, so the 'checking integrity' process was started.
If you find the old system is still present after booting, there are only 2 possible reasons:
1. the 'dcp_corefs_1.10.update' file is not the only one present in the USB drive's root directory
2. the 'dcp_corefs_1.10.update' file was corrupted while being extracted/stored from the zip file, e.g. if you un-zipped directly to the stick and removed it without ejecting the medium properly (i.e. using the "Safely Remove Hardware" function)
Hope that helps.
Jan
