Dear All,
I'm running file tftp_get_firmware.c use rcm6700 and dc10.72a.
After downloading complete, always error verify.
Download completed, attempting to install.
verifying and installing new firmware
Found v0.00...
Attempting to install new version...
verify 0.00%
Error -1 verifying firmware
firmware image bad, installation aborted
attempting to restore boot firmware from RAM
Already test with other bin file but still verify error.
Can anyone help me ?
Thanks
Stev
Posted by: S Sutikno
Remote program update
Started by ●December 22, 2016
Reply by ●December 22, 20162016-12-22
How are you building the binary? Have you selected the correct board in the
“Targetless Device” section of the project settings? Having it fail
that early is a likely indication that there’s a problem with the firmware
info structure in the first 1KB of the image.
With the RCM6700, if you have the space to spare, you should explore the power-fail safe options for Remote Program Update. In that instance, the device always keeps a bootable version of the firmware, and can survive a power failure at any point in the update process. The other methods will have at least a small widow of time where a failure would leave the board unbootable.
-Tom
> On Dec 22, 2016, at 4:23 AM, S Sutikno s...@gmail.com [rabbit-semi] wrote:
>
> Dear All,
>
> I'm running file tftp_get_firmware.c use rcm6700 and dc10.72a.
> After downloading complete, always error verify.
>
> Download completed, attempting to install.
> verifying and installing new firmware
> Found v0.00...
> Attempting to install new version...
> verify 0.00%
> Error -1 verifying firmware
> firmware image bad, installation aborted
> attempting to restore boot firmware from RAM
>
> Already test with other bin file but still verify error.
> Can anyone help me ?
>
> Thanks
> Stev
With the RCM6700, if you have the space to spare, you should explore the power-fail safe options for Remote Program Update. In that instance, the device always keeps a bootable version of the firmware, and can survive a power failure at any point in the update process. The other methods will have at least a small widow of time where a failure would leave the board unbootable.
-Tom
> On Dec 22, 2016, at 4:23 AM, S Sutikno s...@gmail.com [rabbit-semi] wrote:
>
> Dear All,
>
> I'm running file tftp_get_firmware.c use rcm6700 and dc10.72a.
> After downloading complete, always error verify.
>
> Download completed, attempting to install.
> verifying and installing new firmware
> Found v0.00...
> Attempting to install new version...
> verify 0.00%
> Error -1 verifying firmware
> firmware image bad, installation aborted
> attempting to restore boot firmware from RAM
>
> Already test with other bin file but still verify error.
> Can anyone help me ?
>
> Thanks
> Stev
Reply by ●December 23, 20162016-12-23
Dear Tom,
Thanks for your advice. Wrong board on targetless device.
Stev
On Thu, Dec 22, 2016 at 11:14 PM, Tom Collins t...@tomlogic.com
[rabbit-semi] wrote:
> How are you building the binary? Have you selected the correct board in
> the “Targetless Device” section of the project settings? Having it fail
> that early is a likely indication that there’s a problem with the firmware
> info structure in the first 1KB of the image.
>
> With the RCM6700, if you have the space to spare, you should explore the
> power-fail safe options for Remote Program Update. In that instance, the
> device always keeps a bootable version of the firmware, and can survive a
> power failure at any point in the update process. The other methods will
> have at least a small widow of time where a failure would leave the board
> unbootable.
>
> -Tom
> On Dec 22, 2016, at 4:23 AM, S Sutikno s...@gmail.com [rabbit-semi] <
> r...> wrote:
>
> Dear All,
>
> I'm running file tftp_get_firmware.c use rcm6700 and dc10.72a.
> After downloading complete, always error verify.
>
> Download completed, attempting to install.
> verifying and installing new firmware
> Found v0.00...
> Attempting to install new version...
> verify 0.00%
> Error -1 verifying firmware
> firmware image bad, installation aborted
> attempting to restore boot firmware from RAM
>
> Already test with other bin file but still verify error.
> Can anyone help me ?
>
> Thanks
> Stev
Thanks for your advice. Wrong board on targetless device.
Stev
On Thu, Dec 22, 2016 at 11:14 PM, Tom Collins t...@tomlogic.com
[rabbit-semi] wrote:
> How are you building the binary? Have you selected the correct board in
> the “Targetless Device” section of the project settings? Having it fail
> that early is a likely indication that there’s a problem with the firmware
> info structure in the first 1KB of the image.
>
> With the RCM6700, if you have the space to spare, you should explore the
> power-fail safe options for Remote Program Update. In that instance, the
> device always keeps a bootable version of the firmware, and can survive a
> power failure at any point in the update process. The other methods will
> have at least a small widow of time where a failure would leave the board
> unbootable.
>
> -Tom
> On Dec 22, 2016, at 4:23 AM, S Sutikno s...@gmail.com [rabbit-semi] <
> r...> wrote:
>
> Dear All,
>
> I'm running file tftp_get_firmware.c use rcm6700 and dc10.72a.
> After downloading complete, always error verify.
>
> Download completed, attempting to install.
> verifying and installing new firmware
> Found v0.00...
> Attempting to install new version...
> verify 0.00%
> Error -1 verifying firmware
> firmware image bad, installation aborted
> attempting to restore boot firmware from RAM
>
> Already test with other bin file but still verify error.
> Can anyone help me ?
>
> Thanks
> Stev
