MobileRead Forums - View Single Post

knc1 · 06-23-2012, 10:07 AM

[QUOTE=wlaf;2124990]Using "setenv rdinit /bin/sh" I got:

Code:

uboot> setenv rdinit /bin/sh
uboot> boot

You need to add that to the existing command line argument strings.
You __must__ use the equals sign.

U-boot contains a small shell, when you print all of the environment variables, you are reading shell scripting.

So you need to modify one of the existing arguments (notice multiple environment variables that are referred to by name).

The rest of your post just shows that the rdinit=/bin/shell argument was never passed along with the rest of the command line arguments.

It does not matter what the problems with the hardware storage media might be, you will be running "memory resident" without reference to the eMMC device.

06-23-2012, 10:07 AM	#61
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	[QUOTE=wlaf;2124990]Using "setenv rdinit /bin/sh" I got: Code: uboot> setenv rdinit /bin/sh uboot> boot You need to add that to the existing command line argument strings. You __must__ use the equals sign. U-boot contains a small shell, when you print all of the environment variables, you are reading shell scripting. So you need to modify one of the existing arguments (notice multiple environment variables that are referred to by name). The rest of your post just shows that the rdinit=/bin/shell argument was never passed along with the rest of the command line arguments. It does not matter what the problems with the hardware storage media might be, you will be running "memory resident" without reference to the eMMC device.