first u can check if ur TFTP server accesses are fine. see if uImage first accessible from TFTP server. from a machine run "tftp 192.168.1.100 get uImage" (so u can figure out where the problem is - tftp access or h/w wiring)
On Fri, Aug 6, 2010 at 2:03 PM, PREMRAJ SV <svpre...@gmail.com> wrote: > Hello all, > I am involved in poting Android into Hawkboard OMAP L138. I > have compiled root file system and kernel image. On porting i am using CROSS > CABLE, Network cable to trsansfer files in Nfs.. > I have installed the packages- nfs-kernel-server, tftp-hpa. > > Edited the path of location of root file system in /etc/exports. > Edited the path of location of tftpboot kernel uImage in > /etc/default/tftp-hpa > > started nfs-kernel-server and tftp-hpa. > > Now setting the arguments in CUTECOM. IP addresses of target and host like, > > setenv ipaddr <board-ip> > setenv serverip <nfs-server-ip> > setenv bootargs mem=128M console=ttyS2,115200n8 root=/dev/nfs rw > nfsroot=<nfs-server-ip>:/data/target ip=<board-ip>::<gateway- > ip>:<netmask>:hawkboard:eth0:off nolock,rsize=1024,wsize=1024 rootdelay=2 > init=/init > > Now when i try to load kernel image by, > > tftpboot 0xc0700000 uImage > > kernel is not getting loaded showing the message, > > TFTP from server 192.168.1.100; our IP address is 192.168.1.101 > Filename 'uImage'. > Load address: 0xc0700000 > Loading: *\0x08T T T T T T T T T T T T T T T T T T T T > Retry count exceeded; starting again > > > > > What must be the issue.. does all the cables i used is a rhigt one?? help > me fix this issue... > > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting