Bootie - Revision history

0xdeadbabe: /* The Bootie Environment */

2011-10-01T14:15:33Z

The Bootie Environment

2011-10-01T14:13:46Z

pixi and pre2 bootie menu

2011-08-31T05:22:38Z

Running Bootie commands

2011-08-31T05:22:04Z

Added Pre 3 help

2011-08-27T07:55:07Z

change formatting on example in multimage section

2011-08-26T00:03:44Z

Added info on image formats supported.

2011-08-22T23:31:47Z

edit for grammer and clarity

2011-08-22T02:20:23Z

2010-06-30T06:40:56Z

2010-05-14T21:30:39Z

@@ Line 193: / Line 193: @@
 == The Bootie Environment ==
-===The default environment of Pre phones during boot follows:===
+=== Pre ===
 <pre><nowiki>
@@ Line 215: / Line 215: @@
 </nowiki></pre>
-===The boot environment on a TouchPad (3.0.2) follows:===
+=== Pre 2 ===
 <pre><nowiki>

@@ Line 36: / Line 36: @@
 	diag            : perform diag operations: write, boot, verify
 	poweroff        : power off completely
 </nowiki></pre>
@@ Line 114: / Line 144: @@
          vibrator        : enable/disable the vibrator
          chg             : charger command
 </nowiki></pre>

@@ Line 9: / Line 9: @@
 The following is an example of using novaterm to run the bootie command "help":
 <pre><nowiki>
@@ Line 36: / Line 38: @@
 </nowiki></pre>
-For a Pre 3, the command set is greatly extended:
+=== Pre 3 ===
 <pre><nowiki>

@@ Line 34: / Line 34: @@
 	diag            : perform diag operations: write, boot, verify
 	poweroff        : power off completely
 </nowiki></pre>

@@ Line 99: / Line 99: @@
 * simple images are just the uImage as produced by kernel build process.
-* multi images that have both the kernel and a ramdisk. Both the kernel and the ramdisk must be processed with mkimage first (kernel is processed by the build). It is important to pass -C none to mkimage when generating the ramdisk file, otherwise Bootie refuses to recognize it. Then generate the multi image like this: mkimage -A arm -T multi -C none -n 'test-multi-image' -d arch/arm/boot/uImage:/tmp/uRamdisk /tmp/uMulti
+* multi images that have both the kernel and a ramdisk. Both the kernel and the ramdisk must be processed with mkimage first (kernel is processed by the build). It is important to pass -C none to mkimage when generating the ramdisk file, otherwise Bootie refuses to recognize it. Then generate the multi image like this:
 When Bootie detects such a multi image, it uses bootargs-ramdisk variable as kernel argument instead of just bootargs, so no need to do any extra actions when trying to feed such a multi-image into the Bootie.

← Older revision		Revision as of 00:03, 26 August 2011
Line 91:		Line 91:
	novacom get file://klog		novacom get file://klog
	</nowiki></pre>		</nowiki></pre>
		+
		+	== Image formats accepted ==
		+
		+	It looks like Bootie accepts images generated with mkimage from u-boot tools.
		+
		+	There are apparently two kinds of images:
		+
		+	* simple images are just the uImage as produced by kernel build process.
		+	* multi images that have both the kernel and a ramdisk. Both the kernel and the ramdisk must be processed with mkimage first (kernel is processed by the build). It is important to pass -C none to mkimage when generating the ramdisk file, otherwise Bootie refuses to recognize it. Then generate the multi image like this: mkimage -A arm -T multi -C none -n 'test-multi-image' -d arch/arm/boot/uImage:/tmp/uRamdisk /tmp/uMulti
		+
		+	When Bootie detects such a multi image, it uses bootargs-ramdisk variable as kernel argument instead of just bootargs, so no need to do any extra actions when trying to feed such a multi-image into the Bootie.

@@ Line 1: / Line 1: @@
-'''Current Version''': 191.4 for WebOS 1.4.1 <BR>
+'''Current Version''': 191.4 introduced with WebOS 1.4.1 <BR>
-Old version : 145.2.6 for WebOS 1.0.3
+Old version : 145.2.6 introduced with WebOS 1.0.3
-stage3 bootloader of the device, unpacked from the end of boot.bin. loaded to **0x82000000** in memory and looks very similar to iBoot from the iPhoneOS devices.
+Bootie is the stage3 bootloader of webOS devices. It is unpacked from the end of boot.bin, and loaded to **0x82000000** in memory. Bootie looks very similar to iBoot from the iPhoneOS devices.
 Getting into bootie mode is as easy as holding the volume-up key while plugging the phone into USB while the phone is in the "off" state.  The novaterm/novaproxy programs can then be used to talk to bootie.
-The example help:
+== Running Bootie commands ==
 <pre><nowiki>
@@ Line 34: / Line 36: @@
 </nowiki></pre>
-The default environment during boot:
+== The Bootie Environment ==
 <pre><nowiki>
@@ Line 56: / Line 60: @@
 </nowiki></pre>
-Here is the boot environment on a TouchPad (3.0.2):
+===The boot environment on a TouchPad (3.0.2) follows:===
 <pre><nowiki>
 T   ? = -1000
@@ Line 79: / Line 84: @@
 </nowiki></pre>
-Another trick while bootie is active:
+== Additional commands ==
   novacom get file://klog

← Older revision		Revision as of 06:40, 30 June 2010
Line 55:		Line 55:
	autoboot = fsboot		autoboot = fsboot
	</nowiki></pre>		</nowiki></pre>
		+
		+
		+	Another trick while bootie is active:
		+
		+	novacom get file://klog