@nevtag I am not sure how you are getting it to compile. I just git the latest uboot and did not patch anything. I did a: make mrproper make sheevaplug_config make u-boot.kwb It did not compile. It blew up trying to compile arch/arm/lib/board.c. So the original source does not even clean compile. I use the git command Jeff posted in compiling u-boot. git clone git://git.denx.de/uby ygator - uBoot
There are a couple other threads that talk about this, but I'll go ahead and put the details here. With a proper board/Marvell/sheevaplug/kwimage.cfg file the doimage and dramregs_pp128_A.txt are not needed. To make u-boot you just do the following steps. make mrproper make sheevaplug_config make u-boot.kwb The produced u-boot.kwb is good to go. Some say it is better to padby ygator - uBoot
@DockstarPBX, Yes, I tried to compile u-boot source from Oct 5 and it does not compile. It looks to be that some source files are trying to be compiled without having CONFIG_SYS_ARM_WITHOUT_RELOC defined.by ygator - uBoot
Should be run usb_load_uimage Note: no capital I in uimageby ygator - uBoot
I thought that would have worked since it did on two drives that gave the inquiry error for me. Though I am using my own compiled u-boot. Here is a run down of the usb flash drives that I have tested. Recognized from cold start Sandisk Cruzer Micro's 512MB, 1GB, 4GB, 16GB Microcenter Store Brand 8GB Recognized from cold start, but with error in inquiry. Works if USB is reset fby ygator - uBoot
Well it is a good sign that the device is at least seen. I have a 2GB PNY Attaché that on cold start the device is not even found. Now if I stop autoboot then plug it in then is is found. Here is what I see Marvell>> usb reset (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 2 USB Device(s) found scanning bus for storage deviceby ygator - uBoot
@ecc The machine type for the dockstar was added to u-boot 6 hours ago.by ygator - uBoot
@ecc What is the allow_dirty all about? I noticed in my build u-boot it shows U-Boot 2010.09-rc1-00010-ga12555c-dirtyby ygator - uBoot
I compiled with CONFIG_CMD_MMC defined and I get an error as well. u-boot/common/cmd_mmc.c:50: undefined reference to `mmc_legacy_init' I found this thread regarding SD support for the sheevaplug MMC/SD support in u-boot that might help you.by ygator - uBoot
@Nematocyst I have a flash drive (PNY 4GB Micro Swivel Attaché) that produces the same results: scanning bus for devices... 3 USB Device(s) found scanning bus for storage devices... error in inquiry 0 Storage Device(s) found I experimented with the usb commands and was able to get around it by resetting the usb first. At least my device worked when I did this. At the u-boot proby ygator - uBoot
You were right ecc. Since I have jtag capability I just went ahead and flashed the u-boot I produced and it worked. I am going to do some more testing.by ygator - uBoot
With kwimage.cfg fixed here is what I do now. git clone git://git.denx.de/u-boot.git u-boot cd u-boot wget http://jeff.doozan.com/debian/uboot/uboot.mtd0.patch patch -p1 < uboot.mtd0.patch I use my copy of kwimage.cfg make mrproper make sheevaplug_config make u-boot.kwb perl -e 'for ($i=0;$i<512;$i++){printf("\xFF" x 1024)}' > /tmp/ff.512k cat u-bootby ygator - uBoot
I have Jeff's u-boot already installed. So I let it boot into the clound engine u-boot and loaded my u-boot from there. Here is what I get now padded with FF. Filename 'u-boot.kwb.512k'. Load address: 0x800000 Loading: ################################################################# ###################################### done Bytes transferred = 524288 (80000 heby ygator - uBoot
There were only a couple small differences that I saw and went with what you had, but it still does not work.by ygator - uBoot
I've been digging into this so that I can compile u-boot on the dockstar. Though I don't know why what I produce does not work yet. However, here is what I have found: The ultimate goal here is to produce a u-boot.kwb file. In the case of the mkDockstar.mtd0 it ends up deleting it since it is later produced by using doimage and dramregs_pp128_A.txt files. So instead of doing a maby ygator - uBoot
I was just following the steps on this page. I thought it was strange that it had a TEXT_BASE at 0x600000, but it says to load it at 0x800000. So I tried changing the TEXT_BASE to 0x800000 as you suggested. Looks like to change the TEXT_BASE it justs needs to be changed in two places in mkDockstar.mtd0. This then changes it in board/Marvell/sheevaplug/config.mk. However, this did not workby ygator - uBoot
@mindsmith I'll try it as soon as I am able to compile a good u-boot from the dockstar.by ygator - uBoot
I did the commands below which are what was posted to do with the exception of two things. 1. Did a make -f Makefile_doimage in the tools directory of the pogo uboot source and used it 2. Did not run codesourcery-arm-2009q3.sh since I am compiling natively What I get locks up the dockstar when I tftp it and try to run it. The image that is produced does not equal the image posted either.by ygator - uBoot