Changes between Version 8 and Version 9 of newport/firmware


Ignore:
Timestamp:
12/06/2018 11:48:28 PM (5 years ago)
Author:
Ryan Erbstoesser
Comment:

update info for flashing newport

Legend:

Unmodified
Added
Removed
Modified

  • newport/firmware

    v8 v9  
    7979Please Note:
    8080 * '''Linux software is supported for programming Newport (jtag_usbv4 required).''' Windows is not supported at this time.''' (serial console through Windows does work).
    81  * '''JTAG Programming of eMMC has not been made available yet'''. You must boot from a microSD image to program or re-program eMMC flash
     81 * '''JTAG Programming of eMMC has not been made available yet'''. You must boot from a microSD image to program or re-program eMMC flash through TFTP
    8282 * '''JTAG Programming of the GSC firmware is supported by the most recent version of jtag_usbv4''' [http://dev.gateworks.com/jtag/linux/x86/jtag_usbv4 here]
    8383  * [wiki:/newport/firmware-update?action=edit#UpdateGSCFirmwareviaJTAG Guide for GSC update via Jtag]
    … …  
    102102The methods you use to update the firmware depends on what specifically you are trying to update.
    103103
    104 Update the entire device from a Compressed Disk Image ('[wiki:newport/boot boot firmware]' as well as OS):
    105 {{{#!bash
    106 setenv dev 0 # use 'mmc list' to show which device to use for eMMC vs microSD
    107 tftpboot ${loadaddr} xenial-newport.img.gz && gzwrite mmc ${dev} ${loadaddr} ${filesize}
     104Update the entire device from a Compressed Disk Image ('[wiki:newport/boot boot firmware]' as well as entire OS):
     105{{{#!bash
     106setenv ipaddr 192.168.1.1 # sets device IP
     107
     108setenv serverip 192.168.1.146 # sets TFTP server IP
     109
     110setenv dev 0 # sets MMC device to be flashed
     111
     112tftpboot ${loadaddr} xenial-newport.img.gz && gzwrite mmc ${dev} ${loadaddr} ${filesize} # will flash xenial-newport.img.gz which resides in the top most directory of the TFTP server 
    108113}}}
    109114  - **If the image was created using a minimally sized filesystem you will want to resize it after booting to take advantage of the full partition space. For an {{{ext4}}} root filesystem on the primary MMC device run {{{resize2fs /dev/mmcblk0p2}}}.**
    110115
    111116To summarize:
    112 {{{#!bash
    113 setenv ipaddr 192.168.1.1 # sets device IP
    114 
    115 setenv serverip 192.168.1.146 # sets TFTP server IP
    116 
    117 setenv dev 0 # sets MMC device to be flashed
    118 
    119 tftpboot ${loadaddr} xenial-newport.img.gz && gzwrite mmc ${dev} ${loadaddr} ${filesize} # will flash xenial-newport.img.gz which resides in the top most directory of the TFTP server 
    120 }}}
     117
    121118
    122119Updating just the kernel can be done with {{{tftpboot}}} and {{{fatwrite}}}: