Stop Paint Coming Off Clothes Line

RANT: Who can now actually run mail server?

is promised, it continues with references to DockStar

uBoot order to translate its own call for not a lot ...

cross compiler / toolchain for arm

uBoot sources

patches for submarines for the DockStar

my adjustments for memory and LEDs

Those who do not all want, you can simply download the finished binary, but must then with the living standard options or customize the options in Flash. My version is the U-boat is here
. Caution: It does not seem to boot any kernel with it. Please test before!
The toolchain you get to the instructions
here and then it goes on
4. ahsoftware further
uBoot with.

At the end there are still adjustments for LEDs and memory of me: In the file

board / Marvell / SheevaPlug / sheevaplug.h

you can choose how you want to have the LEDs set at startup. The following lines simply turn on the orange LED to signal the boot process: # define SHEEVAPLUG_OE_LOW (~ (0)) / * This is for DockStar: * / # define SHEEVAPLUG_OE_HIGH (~ ((1 led on -. Thus we switch on * / / * the yellow one above * /

much more important is the correct configuration of the memory, so that the later-starting Linux tries to access non-existing memory ..

find this option in the definition of the image of the CPU in the configuration file

board / Marvell / SheevaPlug / kwbimage.cfg There the DATA definition is on the street 0xFFD01504 change:

DATA 0xFFD01504 0x07FFFFF1 # CS [0] n Size Register - 07 = 128MB for DockStar

 << 15) )) /* output enable gpio47 (32+15) = orange,   */
                                                  /*               gpio46 (32+14) = green led */
#define SHEEVAPLUG_OE_VAL_LOW    (1 << 29)        /* USB_PWEN low                             */
#define SHEEVAPLUG_OE_VAL_HIGH    0               /* output low => Who now a comfortable command prompt will have the boot loader, edit the file still fast 

include / configs / sheevaplug.h

and add the following lines: # define

CONFIG_SYS_HUSH_PARSER # define # define CONFIG_AUTO_COMPLETE CONFIG_SYS_PROMPT_HUSH_PS2> # define CONFIG_CMDLINE_EDITING Finally, I wanted the customize the default boot options:

 # define CONFIG_BOOTCOMMAND \\ "$ {x_bootcmd_usb}" \\ "$ {setenv bootargs x_bootargs x_bootargs_root}} $ {echo cmdline: $ bootargs {}," \\ "run x_bootload_kernel m_usb_boot;" \\ "reset" / * If we just failed loading from USB reset, my experience what did the second time the device will be found * / [...] # define CONFIG_EXTRA_ENV_SETTINGS \\ "x_bootargs = console = ttyS0, 115200 mtdparts =" CONFIG_MTDPARTS \\ "x_bootargs_root = root = / dev/sda1 ro rootdelay = 5 \\ 0" \\ "= x_bootload_kernel ext2load usb 0-1 0x800000 / boot / uImage \\ 0" \\ "m_usb_boot = if ext2load usb 0-1 0x1100000 / boot / uInitrd; then bootm 0x800000 0x1100000, 0x800000 bootm else, fi, \\ 0" \\ "x_bootcmd_usb start = usb \\ 0 "

This looks the u-boot-boot on the usb stick after a uImage and uInitrd and, if available, using initrd. flashing the uBoot

 The most delicate operation is the flash of uBoot. For testing, it is recommended that the existing boot loader to the new uBoot via network or usb stick to load into memory and jump directly to (use the given bin-file). Who wants to flash his own uBoot should always remember not to accidentally flash the binary but always the boot file (KWB). 

I do that easily with the serial console and a tftp server: setenv ipaddr 10.1.1.17

; setenv ipaddr 10.1.1.1; tftp 0x6400000 u-boot.kwb nand nand erase 0x40000 0x0 0x0 0x40000 0x6400000 write reset 

And if you were lucky, as I do not need a JTAG adapter ...