Changes between Version 41 and Version 42 of newport

Timestamp:

02/08/2018 10:23:10 PM (6 years ago)

Author:

Tim Harvey

Comment:

added section regarding updating firmware from Linux

newport

@@ -152 +152 @@
 [=#serial-ethernet]
 == Update Firmware via Serial Console and Ethernet ==
-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).
+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) - see [#recovery newport/recovery] for details.
 
 
 [=#serial-ethernet-uboot]
-=== Update Firmware via Serial Console and Ethernet from Bootloader ==
+=== Update Firmware via Serial Console and Ethernet from Bootloader ===
 If 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].
 
@@ -178 +178 @@
 }}}
   - 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.
+
+
+[=#serial-ethernet-linux]
+=== Update Firmware via Serial Console and Ethernet from Linux ===
+If booted to Linux on a board you can easily update the [wiki:newport/boot 'Boot Firmware']:
+{{{#!bash
+cd /tmp
+wget http://dev.gateworks.com/newport/firmware-newport.img
+dd if=firmware-newport.img of=/dev/mmcblk0
+}}}
+ * Note above we are writing to {{{/dev/mmcblk0}}} and not a partition
+ * Use {{{/dev/mmcblk1}}} for the secondary MMC device (ie microSD)
+ * Note that Newport boards only supports MMC based boot devices
+
+If 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):
+{{{#!bash
+mount /dev/mmcblk0p1 /mnt
+cp kernel.itb /mnt
+cp newport.scr /mnt
+}}}
+
+Note that if you want to update the root filesystem itself from within Linux you can only do this by either:
+ a) updating portions of the live filesystem that are not in use (ie package updates)
+ b) booting to a kernel+ramdisk (ie [wiki:buildroot buildroot) and imaging the disk