Hi,
I have just downloaded the 4-1-10-9 firmware to a number of Paylink units. It worked on most of them but one unit just stopped with "Unit Resetting" on the screen.
I had to use Task Manager to kill the downloader and the unit would not run normally.
I tried running the download program again, and it downloaded all the code again, but still stopped at "Unit Resetting".
Firmware Download hangs with "Unit Resetting"
Moderators: aardvark, davebush, Admin
It turns out that all versions of Paylink prior to 4.1.10.11 have a fault in the flash reprogramming code.
During reprogramming of the Paylink unit from the USB link, a single bit can be programmed with the wrong data. The fault occurs in about 1% of re-programming operations and is not detected during the flash reprogramming operation.
Paylink versions 4.1.10.9 and later have a reprogramming kernel, which detects the corruption when the application is checksummed before being started. The application is not started and the unit goes directly into re-programming mode.
In this situation, the AES driver program does not show the connection as operational and the windows re-programming utility shows the existing application version as 0.0.0.0.
When the new version (4.1.10.11 or later) is downloaded to Paylink, the flash is reprogrammed with the flash programmer that is part of the previously loaded code. This means that re-programming a unit that was running old software (pre 4.1.10.11) still has a 1% chance of corrupting the flash.
If a corruption does occur when a unit is reprogrammed with 4.1.10.11 or later, the new Kernel detects it and the Paylink reprogramming mechanism will run again. This time though the new flash reprogramming algorithm is used and will be successful.
The loader program combined with the firmware (Windows version 1.0.4.4) has been enhanced to detect a Paylink that has automatically restarted in this way and will automatically repeat the failed download. As this repetition will use the newly downloaded correct code the reprogramming will work this time and the Paylink will remain operational.
During reprogramming of the Paylink unit from the USB link, a single bit can be programmed with the wrong data. The fault occurs in about 1% of re-programming operations and is not detected during the flash reprogramming operation.
Paylink versions 4.1.10.9 and later have a reprogramming kernel, which detects the corruption when the application is checksummed before being started. The application is not started and the unit goes directly into re-programming mode.
In this situation, the AES driver program does not show the connection as operational and the windows re-programming utility shows the existing application version as 0.0.0.0.
When the new version (4.1.10.11 or later) is downloaded to Paylink, the flash is reprogrammed with the flash programmer that is part of the previously loaded code. This means that re-programming a unit that was running old software (pre 4.1.10.11) still has a 1% chance of corrupting the flash.
If a corruption does occur when a unit is reprogrammed with 4.1.10.11 or later, the new Kernel detects it and the Paylink reprogramming mechanism will run again. This time though the new flash reprogramming algorithm is used and will be successful.
The loader program combined with the firmware (Windows version 1.0.4.4) has been enhanced to detect a Paylink that has automatically restarted in this way and will automatically repeat the failed download. As this repetition will use the newly downloaded correct code the reprogramming will work this time and the Paylink will remain operational.
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.