Changes between Version 44 and Version 45 of newport

Timestamp:

02/12/2018 09:42:44 PM (6 years ago)

Author:

Tim Harvey

Comment:

updated instructions regarding updating Boot Firmware to account for preparing image with custom kernel/script/env

newport

@@ -160 +160 @@
 [=#serial-ethernet-uboot]
 === 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].
+If updating firmware via Bootloader/Serial/Ethernet (recommended for speed) 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].
 
 The following instructions assume your board target IP address is 192.168.1.1 and you have a TFTP server at 192.168.1.146. Adjust environment according to your network via 'setenv ipaddr <ipaddr>' and 'setenv serverip <serverip>'.
@@ -169 +169 @@
  * use {{{mmc list}}} to see how they are configured
 
-Examples:
- * Update just the '[wiki:newport/boot boot firmware]' (everything up to and including the Bootloader) ([https://github.com/Gateworks/images-newport/raw/master/firmware-newport.img firmware image]):
-{{{#!bash
-setenv dev 0 # use 'mmc list' to show which device to use for eMMC vs microSD
-tftpboot ${loadaddr} firmware-newport.img && mmc write ${loadaddr} 0 8000 # update first 16MB
-}}}
- * Update the entire device from a Compressed Disk Image ('[wiki:newport/boot boot firmware]' as well as OS):
+The methods you use to update the firmware depends on what specifically you are trying to update.
+
+Update the entire device from a Compressed Disk Image ('[wiki:newport/boot boot firmware]' as well as OS):
 {{{#!bash
 setenv dev 0 # use 'mmc list' to show which device to use for eMMC vs microSD
 tftpboot ${loadaddr} xenial-newport.img.gz && gzwrite mmc ${dev} ${loadaddr} ${filesize}
 }}}
-  - 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.
+  - 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}}}.
+
+Updating just the kernel can be done with {{{tftpboot}}} and {{{fatwrite}}}:
+{{{#!bash
+# kernel
+tftpboot $loadaddr kernel.itb && fatwrite mmc $dev:1 $loadaddr kernel.itb $filesize
+# bootscript
+tftpboot $loadaddr newport.scr && fatwrite mmc $dev:1 $loadaddr newport.scr $filesize
+}}}
+
+Updating the [wiki:newport/boot 'Boot firmware'] (everything up to and including the Bootloader) requires preparing a boot image that contains your desired partition table, boot firmware, kernel, bootscript and U-Boot environment:
+ * on Linux development host with the Newport BSP in a shell that has the env setup:
+{{{#!bash
+IMG=myimage.img
+KERNEL=linux/arch/arm64/boot/Image
+cp firmware-newport.img $(IMG)
+# create kernel.itb with compressed kernel image
+cp $(KERNEL) vmlinux
+gzip -f vmlinux
+./newport/mkits.sh -o kernel.its -k ${PWD}/vmlinux.gz -C gzip -v "Newport Kenrel"
+mkimage -f kernel.its kernel.itb
+# copy kernel.itb into FAT12 filesystem
+fatfs-tool -i $(IMG) cp kernel.itb /
+# create bootscript (customize ubuntu.scr as needed)
+mkimage -A arm64 -T script -C none -d newport/ubuntu.scr ./newport.scr
+# copy newport.scrinto FAT12 filesystem
+fatfs-tool -i $(IMG) cp newport.scr /
+}}}
+ * on a Newport booted to the bootloader:
+{{{#!bash
+setenv dev 0 # use 'mmc list' to show which device to use for eMMC vs microSD
+tftpboot ${loadaddr} myimage.img && mmc write ${loadaddr} 0 8000 # update first 16MB
+mmc rescan # re-scan the mmc devices in case the partition table changed
+}}}
 
 
 [=#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']:
+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
+}}}
+
+You can also easily update the [wiki:newport/boot 'Boot Firmware']. First prepare a boot image that contains your desired partition table, boot firmware, kernel, bootscript and U-Boot environment (see example above). Then on a booted Newport:
 {{{#!bash
 cd /tmp
-wget http://dev.gateworks.com/newport/firmware-newport.img
-dd if=firmware-newport.img of=/dev/mmcblk0
+wget http://dev.gateworks.com/newport/myimage.img
+dd if=myimage.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 this overwrites the partition-table, the U-Boot environment, and the FAT12 filesystem which are things you might have customizations in.**
 
 Note that if you want to update the root filesystem itself from within Linux you can only do this by either: