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 15:03] – 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 57: | 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.1397480621.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
