Changes between Version 41 and Version 42 of newport


Ignore:
Timestamp:
02/08/2018 02:23:10 PM (2 weeks ago)
Author:
Tim Harvey
Comment:

added section regarding updating firmware from Linux

Legend:

Unmodified
Added
Removed
Modified
  • newport

    v41 v42  
    152152[=#serial-ethernet]
    153153== Update Firmware via Serial Console and Ethernet ==
    154 The quickest and easiest way to update your firmware is via Serial Console and Ethernet. You can do this either in the U-Boot bootloader (recommended) or within a Linux OS. If your primary boot device is corrupt, then you can boot via an alternate boot device (ie microSD).
     154The quickest and easiest way to update your firmware is via Serial Console and Ethernet. You can do this either in the U-Boot bootloader (recommended) or within a Linux OS. If your primary boot device is corrupt, then you can boot via an alternate boot device (ie microSD) - see [#recovery newport/recovery] for details.
    155155
    156156
    157157[=#serial-ethernet-uboot]
    158 === Update Firmware via Serial Console and Ethernet from Bootloader ==
     158=== Update Firmware via Serial Console and Ethernet from Bootloader ===
    159159If using U-Boot (recommended) you need to setup a TFTP server to host the files for transfer. Alternatively you could load firmware files from removable storage (microSD, mSATA, or USB for example) however the transfer rate is typically very slow compared to Gigabit Ethernet. For details on setting up a TFTP server see [wiki:tftpserver here].
    160160
     
    178178}}}
    179179  - If using Ubuntu you will want to run {{{resize2fs /dev/mmcblk0p2}}} to resize the partition to expand to the available anytime after the first. This is because {{{xenial-newport.img.gz}}} is a compressed disk image created with a minimal root filesystem to keep flashing time down to a minimum for fast updates.
     180
     181
     182[=#serial-ethernet-linux]
     183=== Update Firmware via Serial Console and Ethernet from Linux ===
     184If booted to Linux on a board you can easily update the [wiki:newport/boot 'Boot Firmware']:
     185{{{#!bash
     186cd /tmp
     187wget http://dev.gateworks.com/newport/firmware-newport.img
     188dd if=firmware-newport.img of=/dev/mmcblk0
     189}}}
     190 * Note above we are writing to {{{/dev/mmcblk0}}} and not a partition
     191 * Use {{{/dev/mmcblk1}}} for the secondary MMC device (ie microSD)
     192 * Note that Newport boards only supports MMC based boot devices
     193
     194If booted to Linux on a board you can also update the kernel and bootscript fairly easily by mounting the FAT12 filesystem and copying the file(s):
     195{{{#!bash
     196mount /dev/mmcblk0p1 /mnt
     197cp kernel.itb /mnt
     198cp newport.scr /mnt
     199}}}
     200
     201Note that if you want to update the root filesystem itself from within Linux you can only do this by either:
     202 a) updating portions of the live filesystem that are not in use (ie package updates)
     203 b) booting to a kernel+ramdisk (ie [wiki:buildroot buildroot) and imaging the disk
    180204
    181205