Choosing uboot/uImage for Guru Server

[pingtoo]

I will upload the correct version later. I am a little bit of concern of you using the version that will load on 0x600000 because your previous post about during your tftp session loading to 0x600000 hung your plug. like I explained earlier the only one time I got that condition is when I was playing with cpu cache. I am not sure what is your plug condition that may cause the session freeze so if you want to try out the production version just be sure you have some back out plan, i.e. using openocd to re-flash you old u-boot.

One option you can consider is to chain load u-boot. use you existing u-boot in NAND chain load the u-boot successful boot linux. to do that you can tftp the uploaded version to memory address 0x800000 then flash it to NAND storage address 0x80000. Once flash successfully you can setup you existing u-boot default load u-boot from NAND@0x80000 to Memory@0x800000. then use the "go" command just like you did in tftp session.

The version I will be uploading will be latest from Das u-boot 2011-03 with minor patches to test speed up in native mem{cpy,move} and fix a small IDE problem.

Good luck

[crunch]

chainloading sounds like a smart idea. I flashed uboot using openocd once on this plug after I bricked it. I suspect that some of my issues could be from the various steps I took to unbrick. I am tempted to clear the entire NAND, but that could be too drastic. I don't want to make a paperweight...

[pingtoo]

@crunch, here are promised u-boot 2011-03 boot at 0x600000.

I upload two versions. the u-boot.bin is use to run from memory. the u-boot.kwb is use to flush in to NAND. To run from memory it must be at 0x600000, To flush any where is fine just dont mix with running u-boot (start from 0x1F954000 upward)

Good luch

[crunch]

I realize now that I might've been flashing .bin images onto my plug - that could be one of my problems because it looks like the .kwb file contains an additional header. Perhaps that's a container of some sort, or just a marker for the flash device to indicate a file? 

 I'm going to flash the flipflip uboot tonight after I finish a memory test. After that I'll load these images and let you know what comes back.

[ppmt]

I had the same issue crunch until I realise that the kwb file works

Like you not sure what the difference is or when you use the bin rather than the kwb!

may be pingtoo knows

[pingtoo]

The Kirkwood SoC's can boot directly from NAND FLASH, SPI FLASH, SATA etc. using its internal bootRom support.

The .kwb contain a checksum and some instructions to direct internal bootrom where to load next bootloader and where to go next.

[crunch]

OK tried this uboot build. If I tftp it to 0x600000, my plug hangs. If I tftp it to 0x800000, I can receive the file but go 0x800000 hangs. Makes sense I guess if it's compiled for 0x600000...

I was successful in flashing the flipflip uboot version to NAND (U-Boot 2010.09-02612-g27fb783-dirty). So now I should have more options, such as USB, etc.