VxWorks issue Can't load boot file -

I have an industrial robot arm on which VxWorks is running in the controller. I am very new to VxWorks when I tried to use FTP, the password was a problem. After going through Vxworks boot process, I can not get the system to boot now. I get the following screen via hyper terminal.

  VxWorks System Boot Copyright 1984-2002 Wind River Systems, Inc. CPU: PC Pantium Version: VxWorks5.5.1 Bsp Version: 1.2 / 2 Manufacturing Date: November 3, 2006, 09:55:58 'Press' to stop automatic boot ... Auto booting ... Boot device: ATA unit Number: 0 Processor Number: 0 Host Name: NITT File Name: / ATA / vxWorks Inet Ethernet (E): 19 2.168.0.253: 4747 Host Inset (H): 19 2.168.0.255 User (U): FTP Password (PW): PW Flag (F): 0x00 Other (O): FII USB Disk Device ... USB Link, Usb Stack driver, the sole dis 2.02 (build 1.31.2006), Stebli Reg 1:10 Copyright Softkonaks LLC, 1999. All rights reserved ... UHCI USB controller initial ... boot file can not be loaded !! I look briefly help men ... [vxworks boot] :? ? - Print this list - Boot (Load & Go) P Print Boot Params C - Change Boot Parameter L Load Boot File G Adders - Go to Adres De Aders [, N] - Display Memory M Eders - Modify Memory F Eders Nbytes, value-fill memory t adrs, adrs, nbytes - copy memory e-print Fatal exceptions v - Print boot logo with version n netif - print network interface device address $ dev (0, procnum) host: / file h = # E = # B = # g = # u = usr [pw = passwd] f = # tn = targetname = script o = other boot div Q: ata = ctrl, drive file name: / ata0 / vxWorks boot device: usbstbl file name: / usbdsk0 / vxWorks boot flags: 0x02 - load local system symbols 0x04 - do not do 0bx002 Autoboot - Quick AutoBoot (no count No) 0x20 - Disable login security 0x40 - Use boot on GPS T boot parameter 0x80 - Use tftp to get boot image 0x100 - Proxy erpeps use available boot devices: Enhanced Network Devices fei0 fei1 ata usbstbl [ VxWorks Boot]:   
 The system was booted without PC first Is there any error in the parameter?   
 
 
 The system has been configured to load from the Eta device, You can see:  
  Available boot devices: Enhanced Network Devices fei0 fei1 ata usbstbl  
 
 is present. Therefore, most likely that the file  / ATA / vxworks  no longer exists, perhaps it has been removed, or is probably corrupt, or the disk has been formatted. What you can see on the disk using the ls command: 
 
  ls / ata   
 You are able to recover using another boot method Can be configured, such as download a boot image via the network or assuming that   is a form of removable storage, by copying a vxworks image on the system . 
 
 By using a USB device, you can modify the boot configurations temporarily to load vxworks from USB (you will need to modify the boot device and file name settings), Or use the bootloader shell command to copy the boot file to the target. 
 
  Copy the file from the USB  
 
 Using a PC, copy the WzxWorks image to the USB device - it does not matter You know that 
 
  cp / usbdsk0 / vxWorks / ata0 / vxWorks 
 
 
 
 
 Code>