Changes between Version 14 and Version 15 of newport

Timestamp:

12/14/2017 10:33:54 PM (8 years ago)

Author:

Tim Harvey

Comment:

added firmware version details and instructions on creating a bootable microSD

newport

@@ -123 +123 @@
 
 
+[=#firmware-version]
+= Firmware Versioning =
+You can determine the firmware version of various portions of the firmware by looking for banners on the serial console. For example:
+{{{#!bash
+Gateworks Newport SPL (ea21abc Tue Dec 12 23:42:48 UTC 2017)
+
+GSC     : v49 0x832c WDT:disabled board temp:61C
+RTC     : 0
+Model   : GW6304-B
+...
+NOTICE:  Booting Trusted Firmware
+NOTICE:  BL1: v1.3(release):OCTEONTX_SDK_6_2_0_build_26
+NOTICE:  BL1: Built : 15:30:07, Dec  4 2017
+NOTICE:  CHIP UniqueID not set
+...
+U-Boot 2017.09-rc1-00023-g1fd1415 (Dec 12 2017 - 15:42:30 -0800) for Cavium OcteonTX CN81XX ARM V8 Core
+...
+}}}
+ - The above shows the version of the BDK used as the Secondary Program Loader (SPL) is 'ea21abc' built on Tue Dec 12 23:42:48 2017. The git sha of 'ea21abc'.
+ - The above shows the version of the ATF (ARM Trusted Firmware) is v1.3 built on Dec 4 2017.
+ - The above shows the version of U-Boot is '2017.09-rc1-00023-g1fd1415' built on Dec 12 2017.
+
+
 [=#firmware-update]
 = Updating Firmware =
@@ -129 +152 @@
 There are two methods for updating firmware:
  * on a live board using Serial Console and Ethernet ('''Note that currently the eMMC FLASH can only be updated on a live board booted from either eMMC or microSD''')
+ * on removable storage (ie recovery microSD)
  * using a GW16099 JTAG dongle (see [#jtag below]) ('''Note that currently only the GSC firmware can be updated via JTAG''')
 
@@ -149 +173 @@
 To update just the 'firmware' (everything up to and including the Bootloader) ([https://github.com/Gateworks/images-newport/raw/master/firmware-newport.img firmware image]):
 {{{#!bash
-mmc dev 0 # use 'mmc list' to show which device is which
+mmc dev 0 # use 'mmc list' to show which device is which and select eMMC
 tftpboot ${loadaddr} firmware-newport.img && mmc write ${loadaddr} 0 8000
 }}}
@@ -155 +179 @@
 To update the 'firmware' as well as the root filesystem ([https://github.com/Gateworks/images-newport/raw/master/xenial-newport.img.gz xenial-newport.img.gz]):
 {{{#!bash
-mmc dev 0 # use 'mmc list' to show which device is which
+mmc list # see which device is emmc vs sd
+setenv dev 0 # use device of emmc assuming booted from emmc
+# using tftp server
 tftpboot ${loadaddr} xenial-newport.img.gz && gzwrite mmc ${dev} ${loadaddr} ${filesize}
 }}}
+
+
+[=#microsd]
+== Creating a microSD recovery image ==
+If your primary boot won't boot for some reason (ie, you corrupted it during development) you can boot from a microSD (see [#bootdevice here]).
+
+To create a bootable microSD meant for recovery purposes only needing the Bootloader you can use [https://github.com/Gateworks/images-newport/raw/master/firmware-newport.img firmware-newport.img]:
+ * On a Linux host:
+{{{#!bash
+DEVICE=/dev/sdc # set to the microSD on your host
+sudo dd if=firmware-newport.img of=$DEVICE
+}}}
+  - '''Be careful to set the DEVICE above to the device the microSD appears as on your Linux host - you do not want to overwrite part of your hosts filesystem'''
+ * On a Newport board booted from eMMC:
+{{{#!bash
+mmc list # if booted from eMMC you should see microSD as dev 1
+mmc dev 1 # select microSD
+tftpboot ${loadaddr} firmware-newport.img && mmc write ${loadaddr} 0 8000
+}}}
+
+To create a bootable microSD with the Gateworks Ubuntu image (takes longer):
+ * On a Linux host:
+{{{#!bash
+DEVICE=/dev/sdc # set to the microSD on your host
+zcat xenial-newport.img.gz | sudo dd of=$DEVICE
+# re-partition with a 3.5MB DOS partition (required by BDK) and a Linux partition at 16MB
+printf "3072,8191,1,,\n32768,,L,,\n" | sudo sfdisk -uS $DEVICE
+}}}
+  - we re-partition so that the full size of your microSD is available as the firmware image has partitions setup for a 8GiB device. Even though the partition table grows to the size of your device you still need to run {{{resize2fs /dev/mmcblk0p2}}} after bootup to grow the partition to fit the space in the table.
+  - while you could use U-Boot on a running board to program a microSD you would not be able to adjust it's partition table easily to take advantage of a larger disk.