1329 | | From time to time, there may be updates to this firmware in order to provide new features. There are two options for updating the GSC firmware: |
1330 | | * JTAG from a host Linux PC via the Linux jtag_usb application found [http://dev.gateworks.com/jtag here]: |
1331 | | * JTAG in it's entirety is explained [wiki:jtag_instructions here] |
1332 | | * '''Note''' Virtual Machines, or VMs are known to have issues using the jtag_usb tool / software |
1333 | | {{{ |
1334 | | #!bash |
1335 | | jtag_usbv4 -m <firmware.txt> ;# update GSC firmware image |
1336 | | jtag_usbv4 -x <firmware.txt> ;# verify GSC firmware image |
1337 | | }}} |
1338 | | |
1339 | | * Linux running on the target board using the {{{gsc_update}}} application which is present in the various Gateworks BSP's (source [https://github.com/Gateworks/gsc_update here]) |
1340 | | {{{ |
1341 | | #!bash |
1342 | | gsc_update -f <firmware.txt> |
1343 | | }}} |
1344 | | |
1345 | | Notes: |
1346 | | * GSC firmware images can be found with the pre-built firmware images for the various product families |
1347 | | * using the {{{gsc_update}}} method, there is no validity checking of the firmware file (for transfer errors or for product ID) - updating an invalid image will require you to use the linux jtag_usbv4 application and a JTAG dongle to re-program (via {{{./jtag_usbv4 -m gsp_firmware.txt}}}). Care should be taken to make sure you are updating a valid image meant for your target board. To verify the firmware update completed properly you can query the GSC firmware version register: |
1348 | | {{{ |
1349 | | #!bash |
1350 | | i2cget -f -y 0 0x20 14 |
1351 | | }}} |
1352 | | * after re-programming the GSC will revert some of its configuration just as if the coin-cell battery had been removed and replaced (see [#firmware-reset firmware-reset] for details) |
| 1329 | From time to time, there may be updates to this firmware in order to provide new features. |
| 1335 | |
| 1336 | There are two options for updating the GSC firmware: |
| 1337 | * Option 1: JTAG from a host Linux PC via the Linux jtag_usb application found [http://dev.gateworks.com/jtag here]: |
| 1338 | * JTAG in it's entirety is explained [wiki:jtag_instructions here] |
| 1339 | * '''Note''' Virtual Machines, or VMs are known to have issues using the jtag_usb tool / software |
| 1340 | {{{ |
| 1341 | #!bash |
| 1342 | jtag_usbv4 -m <firmware.txt> ;# update GSC firmware image |
| 1343 | jtag_usbv4 -x <firmware.txt> ;# verify GSC firmware image |
| 1344 | }}} |
| 1345 | |
| 1346 | * Option 2: Linux running on the target board using the {{{gsc_update}}} application which is present in the various Gateworks BSP's (source [https://github.com/Gateworks/gsc_update here]) |
| 1347 | {{{ |
| 1348 | #!bash |
| 1349 | gsc_update -f <firmware.txt> |
| 1350 | }}} |
| 1351 | |
| 1352 | Notes: |
| 1353 | * GSC firmware images can be found with the pre-built firmware images for the various product families |
| 1354 | * using the {{{gsc_update}}} method, there is no validity checking of the firmware file (for transfer errors or for product ID) - updating an invalid image will require you to use the linux jtag_usbv4 application and a JTAG dongle to re-program (via {{{./jtag_usbv4 -m gsp_firmware.txt}}}). Care should be taken to make sure you are updating a valid image meant for your target board. To verify the firmware update completed properly you can query the GSC firmware version register: |
| 1355 | {{{ |
| 1356 | #!bash |
| 1357 | i2cget -f -y 0 0x20 14 |
| 1358 | }}} |
| 1359 | * after re-programming the GSC will revert some of its configuration just as if the coin-cell battery had been removed and replaced (see [#firmware-reset firmware-reset] for details) |
| 1360 | |
| 1361 | |