Loading Linux Images to a Compact Flash Disk - Revision history

Mgloff at 20:33, 5 March 2018

2018-03-05T20:33:58Z

Mgloff at 20:29, 5 March 2018

2018-03-05T20:29:11Z

Mgloff: Changed --root to --target on put-image script

2014-05-05T17:49:17Z

Changed --root to --target on put-image script

Bserrano at 15:33, 11 April 2014

2014-04-11T15:33:52Z

Bserrano at 21:20, 6 March 2014

2014-03-06T21:20:22Z

Bserrano at 20:58, 6 March 2014

2014-03-06T20:58:16Z

Mdean: Fixed tag.

2013-12-20T02:45:22Z

Fixed tag.

Mgloff at 18:34, 17 December 2013

2013-12-17T18:34:12Z

Mgloff at 18:33, 17 December 2013

2013-12-17T18:33:06Z

Mgloff at 18:30, 17 December 2013

2013-12-17T18:30:54Z

Show changes

@@ Line 16: / Line 16: @@
 * A fully functional Linux desktop.
 * Linux tools installed: <code>tar</code>, and either <code>gzip</code> or <code>bzip2</code> (depending on the image).
-* The EMAC [ftp://ftp.emacinc.com/EMAC_Linux/SDK/Archive/Linux/put-image.tar.gz| put-image] package which provides the <code>put-image</code> script.  The <code>README.TXT</code> file in the package details the steps needed to install the script properly.
+* The EMAC [ftp://ftp.emacinc.com/EMAC_Linux/SDK/Archive/Linux/put-image.tar.gz put-image] package which provides the <code>put-image</code> script.  The <code>README.TXT</code> file in the package details the steps needed to install the script properly.
 Unpack the put-image tar after downloading:

@@ Line 1: / Line 1: @@
 {{#seo:
 |title=Loading Linux Images to a Compact Flash Disk
@@ Line 15: / Line 13: @@
 * The Compact Flash card to hold the firmware.
 * A Compact Flash card reader attached to a computer.
-* The firmware image.
+* The filesystem tar.
 * A fully functional Linux desktop.
-* The package management tools installed: <code>tar</code>, and either <code>gzip</code> or <code>bzip2</code> (depending on the image).
+* Linux tools installed: <code>tar</code>, and either <code>gzip</code> or <code>bzip2</code> (depending on the image).
-* The EMAC package which provides the <code>put-image</code> script.  The <code>README.TXT</code> file in the package details the steps needed to install the script properly.
+* The EMAC [ftp://ftp.emacinc.com/EMAC_Linux/SDK/Archive/Linux/put-image.tar.gz| put-image] package which provides the <code>put-image</code> script.  The <code>README.TXT</code> file in the package details the steps needed to install the script properly.
-The <code>put-image</code> script, and its associated tools, can be downloaded from [https://svn.emacinc.com/listing.php?repname=EMAC+Public+Repository&path=%2FEMAC-OE-2009.03-STABLE%2Ftrunk%2Fcontrib%2Fput-image%2F&rev=0&sc=0| EMAC's Subversion Repository].
+Unpack the put-image tar after downloading:
 <syntaxhighlight lang="bash">
-developer@ldc:~$ svn co https://svn.emacinc.com/public/EMAC-OE-2009.03-STABLE/trunk/contrib/put-image/
+developer@ldc:~$ tar zxvf ~/Downloads/put-image.tar.gz
 </syntaxhighlight>
 {{mbox | type=warning | text= '''WARNING''': Performing the following procedure incorrectly can cause a catastrophic loss of data.  The individual steps should be carefully studied prior to attempting the procedure for the first time.<br /><br /> EMAC cannot be responsible for the loss of data which may result from following this procedure incorrectly. EMAC strongly recommends having a current backup of the data on the development computer before attempting this procedure.}}
@@ Line 109: / Line 92: @@
 <syntaxhighlight lang="console">
-developer@ldc:~$ /path/to/put-image --target=/dev/sdc --boot=/dev/hdc emac-firmware-image.tar.gz
+developer@ldc:~$ /path/to/put-image --target=/dev/sdc --boot=/dev/sda emac-firmware-image.tar.gz
 </syntaxhighlight>

@@ Line 102: / Line 102: @@
 * Now, run the ''put-image'' script as below.
-** The --root option specifies where the card is mounted.
+** The --target option specifies where the card is mounted.
 ** The --boot option specifies the target boot argument.
 ** The last option is the file name of the compressed target root filesystem.
@@ Line 109: / Line 109: @@
 <syntaxhighlight lang="console">
-developer@ldc:~$ /path/to/put-image --root=/dev/sdc --boot=/dev/hdc emac-firmware-image.tar.gz
+developer@ldc:~$ /path/to/put-image --target=/dev/sdc --boot=/dev/hdc emac-firmware-image.tar.gz
 </syntaxhighlight>

@@ Line 1: / Line 1: @@
-{{todo|SEOKWTODO (11.12.13-18:07->KY+);(11.15.13-20:15->MD-)(12.3.13-12:49->KY+);(12.4.13-15:25->MD-);(12.5.13-14:30->KY+);(12.5.13-15:45->MD+)(12.17.13-12:30->MG+)(03.06.14-14:55->BS-)|Klint Youngmeyer|project=oe 4,oe 5,ky,md,mg,bs,SEOKWTODO}}
+{{todo|SEOKWREV (11.12.13-18:07->KY+);(11.15.13-20:15->MD-)(12.3.13-12:49->KY+);(12.4.13-15:25->MD-);(12.5.13-14:30->KY+);(12.5.13-15:45->MD+)(12.17.13-12:30->MG+)(03.06.14-14:55->BS-);(04.11.14-10:30->BS+)|Klint Youngmeyer|project=oe 4,oe 5,ky,md,mg,bs,SEOKWREV}}
 When changing firmware images or creating custom firmware images for your Compact Flash-based machine, it is necessary to perform a few steps to load the firmware image onto the CF card.
 __TOC__

← Older revision		Revision as of 21:20, 6 March 2014
Line 1:		Line 1:
−	{{todo\|SEOKWTODO (11.12.13-18:07->KY+);(11.15.13-20:15->MD-)(12.3.13-12:49->KY+);(12.4.13-15:25->MD-);(12.5.13-14:30->KY+);(12.5.13-15:45->MD+)(12.17.13-12:30->MG+)(03.06.14-14:55->BS+)\|Klint Youngmeyer\|project=oe 4,oe 5,ky,md,mg,bs,SEOKWTODO}}	+	{{todo\|SEOKWTODO (11.12.13-18:07->KY+);(11.15.13-20:15->MD-)(12.3.13-12:49->KY+);(12.4.13-15:25->MD-);(12.5.13-14:30->KY+);(12.5.13-15:45->MD+)(12.17.13-12:30->MG+)(03.06.14-14:55->BS-)\|Klint Youngmeyer\|project=oe 4,oe 5,ky,md,mg,bs,SEOKWTODO}}

	When changing firmware images or creating custom firmware images for your Compact Flash-based machine, it is necessary to perform a few steps to load the firmware image onto the CF card.		When changing firmware images or creating custom firmware images for your Compact Flash-based machine, it is necessary to perform a few steps to load the firmware image onto the CF card.

← Older revision		Revision as of 20:58, 6 March 2014
Line 1:		Line 1:
−	{{todo\|~~Complete~~ (11.12.13-18:07->KY+);(11.15.13-20:15->MD-)(12.3.13-12:49->KY+);(12.4.13-15:25->MD-);(12.5.13-14:30->KY+);(12.5.13-15:45->MD+)(12.17.13-12:30->MG+)\|Klint Youngmeyer\|project=oe 4,oe 5,ky,md,mg,~~Complete~~}}	+	{{todo\|SEOKWTODO (11.12.13-18:07->KY+);(11.15.13-20:15->MD-)(12.3.13-12:49->KY+);(12.4.13-15:25->MD-);(12.5.13-14:30->KY+);(12.5.13-15:45->MD+)(12.17.13-12:30->MG+)(03.06.14-14:55->BS+)\|Klint Youngmeyer\|project=oe 4,oe 5,ky,md,mg,bs,SEOKWTODO}}

	When changing firmware images or creating custom firmware images for your Compact Flash-based machine, it is necessary to perform a few steps to load the firmware image onto the CF card.		When changing firmware images or creating custom firmware images for your Compact Flash-based machine, it is necessary to perform a few steps to load the firmware image onto the CF card.

← Older revision		Revision as of 02:45, 20 December 2013
Line 1:		Line 1:
−	{{todo\|~~Final Draft~~ (11.12.13-18:07->KY+);(11.15.13-20:15->MD-)(12.3.13-12:49->KY+);(12.4.13-15:25->MD-);(12.5.13-14:30->KY+);(12.5.13-15:45->MD+)(12.17.13-12:30->MG+)\|Klint Youngmeyer\|project=oe 4,oe 5,ky,md,mg,Complete}}	+	{{todo\|Complete (11.12.13-18:07->KY+);(11.15.13-20:15->MD-)(12.3.13-12:49->KY+);(12.4.13-15:25->MD-);(12.5.13-14:30->KY+);(12.5.13-15:45->MD+)(12.17.13-12:30->MG+)\|Klint Youngmeyer\|project=oe 4,oe 5,ky,md,mg,Complete}}

	When changing firmware images or creating custom firmware images for your Compact Flash-based machine, it is necessary to perform a few steps to load the firmware image onto the CF card.		When changing firmware images or creating custom firmware images for your Compact Flash-based machine, it is necessary to perform a few steps to load the firmware image onto the CF card.

← Older revision		Revision as of 18:34, 17 December 2013
Line 1:		Line 1:
−	{{todo\|Final Draft (11.12.13-18:07->KY+);(11.15.13-20:15->MD-)(12.3.13-12:49->KY+);(12.4.13-15:25->MD-);(12.5.13-14:30->KY+);(12.5.13-15:45->MD+)\|Klint Youngmeyer\|project=oe 4,oe 5,ky,md,~~FinalDraft~~,mg}}	+	{{todo\|Final Draft (11.12.13-18:07->KY+);(11.15.13-20:15->MD-)(12.3.13-12:49->KY+);(12.4.13-15:25->MD-);(12.5.13-14:30->KY+);(12.5.13-15:45->MD+)(12.17.13-12:30->MG+)\|Klint Youngmeyer\|project=oe 4,oe 5,ky,md,mg,Complete}}

	When changing firmware images or creating custom firmware images for your Compact Flash-based machine, it is necessary to perform a few steps to load the firmware image onto the CF card.		When changing firmware images or creating custom firmware images for your Compact Flash-based machine, it is necessary to perform a few steps to load the firmware image onto the CF card.

@@ Line 21: / Line 21: @@
 developer@ldc:~$ svn co https://svn.emacinc.com/public/EMAC-OE-2009.03-STABLE/trunk/contrib/put-image/
 </syntaxhighlight>
 When the above command is run, the following will be output:
@@ Line 35: / Line 34: @@
 </syntaxhighlight>
 <syntaxhighlight lang="bash">developer@ldc:~$</syntaxhighlight>
 {{mbox | type=warning | text= '''WARNING''': Performing the following procedure incorrectly can cause a catastrophic loss of data.  The individual steps should be carefully studied prior to attempting the procedure for the first time.<br /><br /> EMAC cannot be responsible for the loss of data which may result from following this procedure incorrectly. EMAC strongly recommends having a current backup of the data on the development computer before attempting this procedure.}}
@@ Line 61: / Line 59: @@
 developer@ldc:~$
 </syntaxhighlight>
 The output of the <code>dmesg</code> command shows that the root device node for the Compact Flash card in this case is <code>sdc</code>, and that the only partition found is <code>sdc1</code>.  Inspect the output shown above to see the particular device node on the development PC where the Compact Flash card is mounted. This will be different depending on the configuration of the development PC. The <code>/dev/</code> prefix will go before the device name, but is not shown in the output of <code>dmesg</code>. The device node will start with either <code>sd</code> or <code>hd</code>.  The third letter will specify which of these devices is assigned to the CF card.
@@ Line 71: / Line 68: @@
 /dev/sdc1 on /media/EMAC-OE type ext3 (rw,nosuid,nodev,uhelper=udisks)
 </syntaxhighlight>
 This shows that the device node, <code>/dev/sdc1</code>, is in fact the Compact Flash card.  This is because:
@@ Line 77: / Line 73: @@
 * It '''is''' mounted in the <code>/media</code> directory, where it is expected.  It may alternatively get mounted in <code>/mnt</code>, depending upon the configuration of the Linux distribution in use.
-<br />{{mbox | type=notice | text='''NOTE''': Not all Linux distributions will automatically mount the CF card when it is inserted into the card reader. The CF card must first be mounted in order to be accessible to the operating system. See [http://www.gnu.org/software/libc/manual/html_node/Mount_002dUnmount_002dRemount.html http://www.gnu.org/software/libc/manual/html_node/Mount_002dUnmount_002dRemount.html] for more information about mounting filesystems.}}<br />
+{{mbox | type=notice | text='''NOTE''': Not all Linux distributions will automatically mount the CF card when it is inserted into the card reader. The CF card must first be mounted in order to be accessible to the operating system. See [http://www.gnu.org/software/libc/manual/html_node/Mount_002dUnmount_002dRemount.html http://www.gnu.org/software/libc/manual/html_node/Mount_002dUnmount_002dRemount.html] for more information about mounting filesystems.}}
 * Use <code>fdisk -l</code> to inspect the device node. Use <code>sudo</code> with <code>fdisk</code> to gain the required <code>root</code> privileges to run <code>fdisk</code>
@@ Line 94: / Line 90: @@
 developer@ldc:~$
 </syntaxhighlight>
 * As can be seen from the output of the <code>fdisk -l</code> command above, the disk is 4009 MB in size, which corresponds with the size of the 4 GB Compact Flash being used in this example.
@@ Line 104: / Line 99: @@
 ** The --boot option specifies the target boot argument.
 ** The last option is the file name of the compressed target root filesystem.
 After completion, the ''put-image'' script will output a message indicating success or failure.
@@ Line 111: / Line 105: @@
 developer@ldc:~$ /path/to/put-image --root=/dev/sdc --boot=/dev/hdc emac-firmware-image.tar.gz
 </syntaxhighlight>
 * The ''put-image'' script should automatically unmount the Compact Flash card after the process completes. It is best to check that the Compact Flash card is actually unmounted before unplugging it. Using the ''/dev/sdc1'' example from above, type the following command.
@@ Line 117: / Line 110: @@
 developer@ldc:~$ mount | grep sdc1
 </syntaxhighlight>
 * If the command does not return anything, the Compact Flash card is not mounted and can be removed and inserted into the target device. However, if the command returns something similar to the following listing, the card will need to be unmounted manually.
@@ Line 124: / Line 116: @@
 /dev/sdc1 on /media/EMAC-OE type ext3 (rw,nosuid,nodev,uhelper=udisks)
 </syntaxhighlight>
 * To unmount the Compact Flash card manually, run the following command: