Changes between Version 6 and Version 7 of provisioning

Timestamp:

07/14/2020 08:29:54 PM (4 years ago)

Author:

Cale Collins

Comment:

added newport provisiong section. Removed arbitrary search terms.

provisioning

@@ -185 +185 @@
 }}}
 
-Other key words
- * procure, procurement , copy , jtag upload , production
+= Provisioning root file system from live Newport board
+
+It's always best to create your rootfs from scratch when able.  If you're prevented from doing so it is possible to provision the root file system from some Newport boards without too much difficulty.  Newport SBC's are capable of booting from both eMMC and MMC.  The boot device can be selected by the GSC performing a 5x press on the power button.  To provision the root filesystem of located on the eMMC boot from MMC, create an image of the eMMC partition 2 on the MMC, then compress so it can be loaded on other boards.  
+
+== Requirements
+
+* A Newport board with MMC card slot and push button (GSC must be configured to accept push button input—this is default)
+* A MMC with capacity enough to accommodate full size of eMMC (8GB) along with BSP for performing recovery.  Recommended would be a minimum 16GB or 32GB card.    
+* A desktop computer with Linux natively installed. This workstation must have a drive capable of accepting an MMC and have packages for DD and Mount.  
+
+
+== On your workstation
+
+Download a Gateworks pre-built image.  All of our images include the tools necessary to perform this operation, though Ubuntu will likely be the easiest to work with.  
+{{{
+wget -N http://dev.gateworks.com/newport/images/focal-newport.img.gz
+}}}
+
+Insert a micro SD card into your workstation and identify the device name it's been assigned.  This can be done using a variety of methods, for example the "dmesg" output.  In this example the MMC is "/dev/sdb"
+
+Image the MMC.
+{{{
+zcat focal-newport.img.gz | sudo dd of=/dev/sdb bs=4M
+}}}
+
+Remove the SD card from your workstation. 
+
+== On your Newport SBC
+
+Insert the SD card into the SD card reader, then apply power to the SBC (or otherwise turn it on).  5x press the power button, you will see the status LED turn off and back on.  The BDK will display microSD as MMC0.
+
+Example output:
+
+{{{
+        Gateworks Newport SPL (12.7.0-96865d0 Tue Jul 7 21:19:32 UTC 2020)
+
+        GSC     : v55 0xe7e2 RST:BOOT_WDT2 Thermal Protection Enabled
+        Temp    : Board:34C/86C CPU:42C/100C
+        Model   : GW6400-B1
+        MFGDate : 09-23-2019
+        Serial  : 802864
+        RTC     : 8
+        SoC     : CN8020-800BG676-SCP-P12-G 1024KB 800/550MHz 0xa2 Pass 1.2 
+        MMC0    : microSD
+        MMC1    : eMMC
+}}} 
+
+Proceed to boot to Linux user-space.  Once there if you would like to check the rootfs you're about to image the rootfs of the eMMC is located at /dev/mmcblk1p2.
+
+** Optional: **
+{{{
+mount /dev/mmcblk1p2 /mnt
+
+ls /mnt #this will display the eMMC's rootfs
+
+umount /mnt
+}}}
+
+Image the partition to a file.
+{{{
+dd if=/dev/mmcblk1p2 of=myrootfs.img
+}}}
+
+"sync" the filesystem and power board off
+{{{
+sync
+#remove power
+}}}
+
+Remove MMC from the SBC.  
+
+== Create an image
+
+Navigate to the "/tmp" directory on your workstation.  In actuality this can be any directory that you have read and write permissions, "/tmp" should only be used if you don't care what happens to these files later.    
+{{{
+cd /tmp
+}}}
+
+Insert the MMC into the SD card reader on your workstation, as before note the the name the device is assigned.  Because we created our image in within the rootfs we will need to mount the second partition, for example "/dev/sdb2":
+{{{
+sudo mount /dev/sdb2 /mnt/
+
+ls /mnt/
+}}}
+Copy the image you created of mmcblk1p2 into "/tmp"
+{{{
+cp /mnt/myrootfs.img .
+}}}
+Executing the command "file" on this file will return that it is ext4 filesystem data and the volume name is "rootfs".
+
+Example:
+{{{
+        user@workstation:/tmp$ file myrootfs.img 
+        myrootfs.img: Linux rev 1.0 ext4 filesystem data, UUID=951f19a1-cc54-4a07-9b7f-41a54ea8acb4, volume name "rootfs" (needs journal recovery) (extents) (64bit) (large files) (huge files)
+}}}
+
+Add boot firmware and create a gzipped image.  
+* Download boot firmware 
+{{{
+wget http://dev.gateworks.com/newport/boot_firmware/firmware-newport.img
+}}}
+* name it however you please
+{{{
+cp firmware-newport.img myimg-newport.img
+}}}
+* Create a disk image containing the root filesystem and boot firmware.  The boot firmware is 16M so we will "dd" the rootfs using this offset.  
+{{{
+dd if=myrootfs.img of=myimg-newport.img bs=16M seek=1
+}}}
+* gzip the image so it can be installed using standard methods on other Newport boards. 
+{{{
+gzip -k -f myimg-newport.img 
+}}}
+Be mindful that the image size can't exceed the total DRAM of the board you plan to install it on if you're using the bootloader command "tftpboot".  The "update_all", and "update_rootfs" scripts both use this command
+{{{
+ls -lh myimg-newport.img.gz #size must be less than total DRAM of board
+}}}
+
+== Flash this image to a Newport SBC:
+
+In the bootloader:
+{{{
+GW6400-B1> setenv ipaddr 192.168.1.52
+GW6400-B1> setenv serverip 192.168.1.56
+GW6400-B1> setenv image myimg-newport.img.gz
+GW6400-B1> setenv dev 0
+GW6400-B1> run update_all 
+}}}
+
+
+