Zbrain System Z4 built_in_firmware_update
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| built_in_firmware_update [2014/04/14 14:52] – ba | built_in_firmware_update [2017/11/07 22:26] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| This VI performs a software update from sd card.\\ | This VI performs a software update from sd card.\\ | ||
| \\ | \\ | ||
| + | |||
| + | A application that was built to boot from [[hw: | ||
| ===== Detailed operation ===== | ===== Detailed operation ===== | ||
| Line 19: | Line 21: | ||
| - A reset is executed | - A reset is executed | ||
| - The flashed application is started | - The flashed application is started | ||
| + | |||
| + | ===== Operation without display ===== | ||
| + | |||
| + | If no display refnum is wired to the vi, the firmware update is performed without display. | ||
| Line 39: | Line 45: | ||
| * **chksum** The check sum must match the check sum built over the loader file. | * **chksum** The check sum must match the check sum built over the loader file. | ||
| * **size** The size must match the size of the loader file in bytes. | * **size** The size must match the size of the loader file in bytes. | ||
| - | * **deletme** If this parameter is 1 the zfu file will be deleted after the update. | + | * **deletme** If this parameter is 1 the zfu file will be deleted after the update. This can be used to prevent from repeatedly flashing the same update. |
| * **waitbeforereset** The target waits for the given seconds before resetting the board after the update. No reset is issued (reset or power cycle must be initiated manually) when this parameter is 0. | * **waitbeforereset** The target waits for the given seconds before resetting the board after the update. No reset is issued (reset or power cycle must be initiated manually) when this parameter is 0. | ||
| Line 53: | Line 59: | ||
| ===== Limitations ===== | ===== Limitations ===== | ||
| - | * **If the update process is interrupted by a reset or a power cycle, the firmware update will be corrupt. In this case the device needs to be reprogrammed manually via JTAG emulator**. This limitation does not apply when starting the firmware update from [[hw: | + | * **If the update process is interrupted by a reset or a power cycle, the firmware update will be corrupt. In this case the device needs to be reprogrammed manually via JTAG emulator**. This limitation does not apply when starting the firmware update from [[hw: |
| * The flashed application is responsible to start the boot loader application. There is no by pass. It is crucial to test the firmware update functionality in new application versions before shipment. | * The flashed application is responsible to start the boot loader application. There is no by pass. It is crucial to test the firmware update functionality in new application versions before shipment. | ||
| * Older targets and SDKs are not supported. | * Older targets and SDKs are not supported. | ||
built_in_firmware_update.1397479969.txt.gz · Last modified: 2017/11/07 22:26 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
