On Mon, Jun 11, 2012 at 07:25:25PM +0200, Luka Perkov wrote: > On Mon, Jun 11, 2012 at 06:30:31PM +0200, Martin Mueller wrote: > > > And can you please also flash it on the device? As I understand you have > > > loaded it over JTAG only... > > > > Yes, that should be the same as loading it via serial to RAM. I'm > > relucant to flash the bootloader, as I have never flashed on before. > > Which image would i need to flash where? Your bootloader seems to live > > at 0x600000 where as the original "Cloud engine uboot 1.1.4" seems to > > live at 0x800000. > > Where did you see that it lives on 0x600000?
Sorry I did a grep for TEXT_BASE, but looked at the iconnect line instead of the dockstar one. > This is how I flash my kirkwood device (0x62118 is the size of loaded > binary): > > tftpboot 0x0800000 u-boot.kwb > nand erase 0x0 0x70000 ; nand write 0x0800000 0x0 0x62118 > > You should flash it on the beginning of the nand chip. Ok, I flashed the new uboot, here is the output: U-Boot 2012.04.01 (Jun 11 2012 - 19:41:27) Seagate FreeAgent DockStar SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Hit any key to stop autoboot: 0 DockStar> It still can't boot my old image on the dockstar, so I suppose I need to flash a new one. It want's to bbot some ubi-stuff, which I don't seem to have. The build just produces jffs2 images. Where to go from here? bye MM -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel