U-Boot UMS on APF & OPOS - Revision history

SebastienSz: /* Links */ add link the the OPOS8MM eMMC data partition page

2021-05-21T13:23:30Z

Links: add link the the OPOS8MM eMMC data partition page

← Older revision		Revision as of 15:23, 21 May 2021
Line 97:		Line 97:
	==Links==		==Links==
	* [[EMMC_OPOS6UL#User_Data_partition_layout\|OPOS6UL eMMC Data partition]]		* [[EMMC_OPOS6UL#User_Data_partition_layout\|OPOS6UL eMMC Data partition]]
			* [[EMMC_OPOS8MM#User_Data_partition_layout\|OPOS8MM eMMC Data partition]]

	[[Category:U-Boot]]		[[Category:U-Boot]]

SebastienSz at 08:05, 25 March 2019

2019-03-25T08:05:29Z

← Older revision		Revision as of 10:05, 25 March 2019
Line 38:		Line 38:
	<pre class="host">		<pre class="host">
	$ sudo umount /media/usb1 (if partition is auto-mounted)		$ sudo umount /media/usb1 (if partition is auto-mounted)
	$ sudo mkfs.ext4 -L ROOTFS -O ^64bit /dev/sdc2		$ sudo mkfs.ext4 -L ROOTFS -O ^64bit,^metadata_csum,uninit_bg /dev/sdc2
	</pre>		</pre>

JulienB at 15:21, 27 February 2018

2018-02-27T15:21:24Z

← Older revision		Revision as of 17:21, 27 February 2018
Line 1:		Line 1:
	This page gather instructions for using U-Boot's USB Mass Storage gadget mode (or UMS) usage on [[APF6]] and [[OPOS6UL]]. This mode allows you to flash rootfs images bigger than the available module RAM, ex: > 200MBytes on the [[OPOS6UL]]. Indeed ''run update_rootfs'' script uses RAM to store images while uploading from TFTP, which can be short for big rootfs. UMS also allows you to backup your rootfs on your Host.		This page gather instructions for using U-Boot's USB Mass Storage gadget mode (or UMS) usage on [[APF6]] and [[OPOS6UL]](NANO). This mode allows you to flash rootfs images bigger than the available module RAM, ex: > 200MBytes on the [[OPOS6UL]](NANO). Indeed ''run update_rootfs'' script uses RAM to store images while uploading from TFTP, which can be short for big rootfs. UMS also allows you to backup your rootfs on your Host.

	* First, keep your USB debug cable and connect a second USB cable on [[APF6_Dev]] or [[OPOS6ULDev]]'s OTG port.		* First, keep your USB debug cable and connect a second USB cable on [[APF6_Dev]] or [[OPOS6ULDev]]'s OTG port.

JulienB: /* Links */

2017-07-21T09:58:17Z

Links

← Older revision		Revision as of 11:58, 21 July 2017
Line 91:		Line 91:
	$ ls /media/mmc/boot/		$ ls /media/mmc/boot/
	</pre>		</pre>

			==Troubleshots==
			* UMS was reported not working on Windows 7/8 hosts with Virtual Box Ubuntu 15.04 emulated machines...

	==Links==		==Links==

JulienB at 10:35, 13 July 2017

2017-07-13T10:35:27Z

← Older revision		Revision as of 12:35, 13 July 2017
Line 1:		Line 1:
	~~Infos~~ for U-Boot's USB Mass Storage gadget mode (or UMS) usage on [[APF6]] and [[OPOS6UL]]. This mode allows you to flash rootfs bigger than the available module RAM, ex: > 200MBytes on the [[OPOS6UL]]. Indeed ''run update_rootfs'' script uses RAM to store images while uploading from TFTP, which can be short for big rootfs.		This page gather instructions for using U-Boot's USB Mass Storage gadget mode (or UMS) usage on [[APF6]] and [[OPOS6UL]]. This mode allows you to flash rootfs images bigger than the available module RAM, ex: > 200MBytes on the [[OPOS6UL]]. Indeed ''run update_rootfs'' script uses RAM to store images while uploading from TFTP, which can be short for big rootfs. UMS also allows you to backup your rootfs on your Host.

	* First, keep your USB debug cable and connect a second USB cable on [[APF6_Dev]] or [[OPOS6ULDev]]'s OTG port.		* First, keep your USB debug cable and connect a second USB cable on [[APF6_Dev]] or [[OPOS6ULDev]]'s OTG port.
Line 41:		Line 41:
	</pre>		</pre>

			==Update your rootfs==
	* Then, you have 2 methods to update your rootfs:		* Then, you have 2 methods to update your rootfs:
	{\| class="wikitable"		{\| class="wikitable"
Line 79:		Line 80:
	BIOS>		BIOS>
	</pre>		</pre>

			==Backup your rootfs==
			<pre class="host">
			$ sudo dd if=/dev/sdc2 of=/home/xxx/rootfs_xxx.ext4 (takes time ;-) )
			</pre>

			* check if it succeed:
			<pre class="host">
			$ sudo mount -o loop /home/xxx/rootfs_xxx.ext4 /media/mmc/
			$ ls /media/mmc/boot/
			</pre>

			==Links==
			* [[EMMC_OPOS6UL#User_Data_partition_layout\|OPOS6UL eMMC Data partition]]

	[[Category:U-Boot]]		[[Category:U-Boot]]

JulienB at 10:00, 13 July 2017

2017-07-13T10:00:43Z

← Older revision		Revision as of 12:00, 13 July 2017
Line 29:		Line 29:
	</pre>		</pre>
	{{Warning\| Before doing the following procedure, be sure that your device name is correct. '''You can erase all your Host datas if you do it wrong !!!'''}}		{{Warning\| Before doing the following procedure, be sure that your device name is correct. '''You can erase all your Host datas if you do it wrong !!!'''}}
	* The rootfs is under the sdc2 and is named "~~rootfs~~". In debian/ubuntu it might be auto-mounted under ''/media/usb1'', if no other USB key is present on system and if you activated auto-mounting.		* The rootfs is under the sdc2 and is named "ROOTFS". On your debian/ubuntu Host it might be auto-mounted under ''/media/usb1'', if no other USB key is present on system and if you activated auto-mounting.
	<pre class="host">		<pre class="host">
	$ ls /media/usb1/		$ ls /media/usb1/

SebastienSz at 07:28, 3 April 2017

2017-04-03T07:28:36Z

← Older revision		Revision as of 09:28, 3 April 2017
Line 38:		Line 38:
	<pre class="host">		<pre class="host">
	$ sudo umount /media/usb1 (if partition is auto-mounted)		$ sudo umount /media/usb1 (if partition is auto-mounted)
	$ sudo mkfs.ext4 -L ROOTFS /dev/sdc2		$ sudo mkfs.ext4 -L ROOTFS -O ^64bit /dev/sdc2
	</pre>		</pre>

JulienB: add some precisions

2017-03-29T09:28:52Z

add some precisions

← Older revision		Revision as of 11:28, 29 March 2017
Line 18:		Line 18:
	</pre>		</pre>

	Here the device is ''/dev/sdc'' and all partitions have been automounted by the ~~host~~:		Here the device is ''/dev/sdc'' and all partitions have been automounted by the Host:

	<pre class="host">		<pre class="host">
Line 28:		Line 28:
	[26830.268450] EXT4-fs (sdc1): mounted filesystem without journal. Opts: (null)		[26830.268450] EXT4-fs (sdc1): mounted filesystem without journal. Opts: (null)
	</pre>		</pre>
	{{Warning\| Before doing the following procedure, be sure that your device name is correct. '''You can erase all your ~~host~~ datas if you do it wrong !!!'''}}		{{Warning\| Before doing the following procedure, be sure that your device name is correct. '''You can erase all your Host datas if you do it wrong !!!'''}}
	* The rootfs is under the sdc2 and is named "rootfs". In debian/ubuntu it's auto-mounted under ''/media/usb1'' if no other USB key is present on system.		* The rootfs is under the sdc2 and is named "rootfs". In debian/ubuntu it might be auto-mounted under ''/media/usb1'', if no other USB key is present on system and if you activated auto-mounting.
	<pre class="host">		<pre class="host">
	$ ls /media/usb1/		$ ls /media/usb1/
Line 37:		Line 37:
	* To flash entire rootfs, first erase all files on this partition:		* To flash entire rootfs, first erase all files on this partition:
	<pre class="host">		<pre class="host">
	$ sudo umount /media/usb1		$ sudo umount /media/usb1 (if partition is auto-mounted)
	$ sudo mkfs.ext4 /dev/sdc2		$ sudo mkfs.ext4 -L ROOTFS /dev/sdc2
	</pre>		</pre>

			* Then, you have 2 methods to update your rootfs:
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 64:		Line 65:
	</pre>		</pre>
	\|\|		\|\|
	* One alternative way to untaring ~~might be~~ to use ''dd'':		* One alternative way to untaring is to use ''dd'':
	<pre class="host">		<pre class="host">
	$ sudo dd if=/tftpboot/xxx-rootfs.ext4 of=/dev/sdc2		$ sudo dd if=/tftpboot/xxx-rootfs.ext4 of=/dev/sdc2
	</pre>		</pre>
			(replace xxx with the name of your module)
	\|}		\|}

JulienB at 09:16, 29 March 2017

2017-03-29T09:16:32Z

← Older revision		Revision as of 11:16, 29 March 2017
Line 10:		Line 10:
	* On your Host computer you should see the [[eMMC]] partition like a standard USB key.		* On your Host computer you should see the [[eMMC]] partition like a standard USB key.
	<pre class="host">		<pre class="host">
	$ dmesg		$ dmesg \| tail
	[...]		[...]
	[26828.348088] sd 13:0:0:0: [sdc] Mode Sense: 0f 00 00 00		[26828.348088] sd 13:0:0:0: [sdc] Mode Sense: 0f 00 00 00

JulienB: precision why using UMS

2017-03-29T09:13:59Z

precision why using UMS

← Older revision		Revision as of 11:13, 29 March 2017
Line 1:		Line 1:
	Infos for U-Boot's USB Mass Storage gadget mode (or UMS) usage on [[APF6]] and [[OPOS6UL]].		Infos for U-Boot's USB Mass Storage gadget mode (or UMS) usage on [[APF6]] and [[OPOS6UL]]. This mode allows you to flash rootfs bigger than the available module RAM, ex: > 200MBytes on the [[OPOS6UL]]. Indeed ''run update_rootfs'' script uses RAM to store images while uploading from TFTP, which can be short for big rootfs.

	* First, keep your USB debug cable and connect a second USB cable on [[APF6_Dev]] or [[OPOS6ULDev]]'s OTG port.		* First, keep your USB debug cable and connect a second USB cable on [[APF6_Dev]] or [[OPOS6ULDev]]'s OTG port.
Line 8:		Line 8:
	\|		\|
	</pre>		</pre>
	* On your ~~host~~ computer you should see the [[eMMC]] partition like a standard USB key.		* On your Host computer you should see the [[eMMC]] partition like a standard USB key.
	<pre class="host">		<pre class="host">
	$ dmesg		$ dmesg