CE>> mw 0x800000 0xffff 0x40000

CE>> tftpboot 0x800000 openwrt-kirkwood-dockstar-u-boot.bin

Using egiga0 device

TFTP from server 192.168.0.7; our IP address is 169.254.254.253; sending through gateway 192.168.0.1

Filename 'openwrt-kirkwood-dockstar-u-boot.bin'.

Load address: 0x800000

Loading: T T T T T T T T T T

Retry count exceeded; starting again

Using egiga1 device

TFTP from server 192.168.0.7; our IP address is 169.254.254.253; sending through gateway 192.168.0.1

Filename 'openwrt-kirkwood-dockstar-u-boot.bin'.

Load address: 0x800000

Loading: T T T T T T T T T T

Retry count exceeded; starting again

-----------------

which ip should I use ?
the real ip of my tftp server or the general broadcast ?

that depends on the netmasks you are using. but easiest would be to set your dockstars ip to 192.168.0.x where x is something between 1 and 254, which is not in use by any other device. so 8 might be a good idea.

Nothing seems to happen

CE>> tftpboot 0x800000 openwrt-kirkwood-dockstar-u-boot.bin

Using egiga0 device

TFTP from server 192.168.0.11; our IP address is 192.168.0.37

Filename 'openwrt-kirkwood-dockstar-u-boot.bin'.

Load address: 0x800000

Loading: T T T T T T T T T T

Retry count exceeded; starting again

Using egiga1 device

TFTP from server 192.168.0.11; our IP address is 192.168.0.37

Filename 'openwrt-kirkwood-dockstar-u-boot.bin'.

Load address: 0x800000

Loading: T T T T T T T T T T

Retry count exceeded; starting again

Here is my conf :

netmask=255.255.255.0

gatewayip=192.168.0.254

ipaddr=192.168.0.37

eth1addr=00:10:75:1a:d6:1b

ethact=egiga1

ethaddr=00:10:75:1A:D6:1B

cesvcid=FUSYBS7LT67ZCZQ7Q96E6C5K46

ceserialno=2GEP1JAY

ceboardver=REDSTONE:1.0

bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000

serverip=192.168.0.11

my server is running

nobody     804     1  0 21:12 ?        00:00:00 /usr/sbin/atftpd --daemon --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 /tftpboot

in /tftpboot everything is 777

I've tried with cross cable and with direct cable to no avail...

Use the command

ping $(serverip)

in u-boot to verify connectivity to your TFTP server.  If that's OK, check your TFTP server logs and configuration.

finally I changed managed to get the tftp working.
installed everything without errors
but at the final stage

FTP from server 10.5.5.1; our IP address is 10.5.5.2

Filename 'openwrt-kirkwood-Dockstar-jffs2-128k.img'.

Load address: 0x6400000

Loading: #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         ############################################################

done

Bytes transferred = 1968128 (1e0800 hex)

I FORGOT to type the last 2 lines :

nand erase 0x500000 0xfb00000
nand write.e 0x6400000 0x500000 0x200000

and typed instead boot

CE>> boot

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x100000 --   0% complete.
Reading data from 0x10a000 --   1% complete.
Reading data from 0x114000 --   2% complete.
Reading data from 0x11e800 --   3% complete.
Reading data from 0x128800 --   4% complete.
Reading data from 0x133000 --   5% complete.
Reading data from 0x13d000 --   6% complete.
Reading data from 0x147800 --   7% complete.
Reading data from 0x151800 --   8% complete.
Reading data from 0x15c000 --   9% complete.
Reading data from 0x166000 --  10% complete.
Reading data from 0x170800 --  11% complete.
Reading data from 0x17a800 --  12% complete.
Reading data from 0x185000 --  13% complete.
Reading data from 0x18f000 --  14% complete.
Reading data from 0x199800 --  15% complete.
Reading data from 0x1a3800 --  16% complete.
Reading data from 0x1ae000 --  17% complete.
Reading data from 0x1b8000 --  18% complete.
Reading data from 0x1c2800 --  19% complete.
Reading data from 0x1cc800 --  20% complete.
Reading data from 0x1d7000 --  21% complete.
Reading data from 0x1e1000 --  22% complete.
Reading data from 0x1eb800 --  23% complete.
Reading data from 0x1f5800 --  24% complete.
Reading data from 0x1ff800 --  25% complete.
Reading data from 0x20a000 --  26% complete.
Reading data from 0x214000 --  27% complete.
Reading data from 0x21e800 --  28% complete.
Reading data from 0x228800 --  29% complete.
Reading data from 0x233000 --  30% complete.
Reading data from 0x23d000 --  31% complete.
Reading data from 0x247800 --  32% complete.
Reading data from 0x251800 --  33% complete.
Reading data from 0x25c000 --  34% complete.
Reading data from 0x266000 --  35% complete.
Reading data from 0x270800 --  36% complete.
Reading data from 0x27a800 --  37% complete.
Reading data from 0x285000 --  38% complete.
Reading data from 0x28f000 --  39% complete.
Reading data from 0x299800 --  40% complete.
Reading data from 0x2a3800 --  41% complete.
Reading data from 0x2ae000 --  42% complete.
Reading data from 0x2b8000 --  43% complete.
Reading data from 0x2c2800 --  44% complete.
Reading data from 0x2cc800 --  45% complete.
Reading data from 0x2d7000 --  46% complete.
Reading data from 0x2e1000 --  47% complete.
Reading data from 0x2eb800 --  48% complete.
Reading data from 0x2f5800 --  49% complete.
Reading data from 0x2ff800 --  50% complete.
Reading data from 0x30a000 --  51% complete.
Reading data from 0x314000 --  52% complete.
Reading data from 0x31e800 --  53% complete.
Reading data from 0x328800 --  54% complete.
Reading data from 0x333000 --  55% complete.
Reading data from 0x33d000 --  56% complete.
Reading data from 0x347800 --  57% complete.
Reading data from 0x351800 --  58% complete.
Reading data from 0x35c000 --  59% complete.
Reading data from 0x366000 --  60% complete.
Reading data from 0x370800 --  61% complete.
Reading data from 0x37a800 --  62% complete.
Reading data from 0x385000 --  63% complete.
Reading data from 0x38f000 --  64% complete.
Reading data from 0x399800 --  65% complete.
Reading data from 0x3a3800 --  66% complete.
Reading data from 0x3ae000 --  67% complete.
Reading data from 0x3b8000 --  68% complete.
Reading data from 0x3c2800 --  69% complete.
Reading data from 0x3cc800 --  70% complete.
Reading data from 0x3d7000 --  71% complete.
Reading data from 0x3e1000 --  72% complete.
Reading data from 0x3eb800 --  73% complete.
Reading data from 0x3f5800 --  74% complete.
Reading data from 0x3ff800 --  75% complete.
Reading data from 0x40a000 --  76% complete.
Reading data from 0x414000 --  77% complete.
Reading data from 0x41e800 --  78% complete.
Reading data from 0x428800 --  79% complete.
Reading data from 0x433000 --  80% complete.
Reading data from 0x43d000 --  81% complete.
Reading data from 0x447800 --  82% complete.
Reading data from 0x451800 --  83% complete.
Reading data from 0x45c000 --  84% complete.
Reading data from 0x466000 --  85% complete.
Reading data from 0x470800 --  86% complete.
Reading data from 0x47a800 --  87% complete.
Reading data from 0x485000 --  88% complete.
Reading data from 0x48f000 --  89% complete.
Reading data from 0x499800 --  90% complete.
Reading data from 0x4a3800 --  91% complete.
Reading data from 0x4ae000 --  92% complete.
Reading data from 0x4b8000 --  93% complete.
Reading data from 0x4c2800 --  94% complete.
Reading data from 0x4cc800 --  95% complete.
Reading data from 0x4d7000 --  96% complete.
Reading data from 0x4e1000 --  97% complete.
Reading data from 0x4eb800 --  98% complete.
Reading data from 0x4f5800 --  99% complete.
Reading data from 0x4ff800 -- 100% complete.

4194304 bytes read: OK

## Starting application at 0x02000000 ...

undefined instruction

pc : [<03cdc98c>]          lr : [<02000008>]

sp : 005fe5a4  ip : 005fe134     fp : 005fe5c0

r10: 00000000  r9 : ffffe806     r8 : 005fffcc

r7 : 005fe9e5  r6 : 00000002     r5 : 005ff1dc  r4 : 02000000

r3 : 00000000  r2 : f1012000     r1 : 005ff1dc  r0 : ea000012

Flags: nZCv  IRQs off  FIQs off  Mode SVC_32

Resetting CPU ...

and now the device seems completely dead
no flashing,no response at the minicom ...
Is there a way to get it going ?
Please help with an advice ??