On Sat, Oct 16, 2004 at 07:56:41PM +0530, ravi.aloor@wipro.com wrote:
- Now I already have BDI-new.cfg file in my /tftpboot/ directory on my
PC. I pinged BDI. Response is OK. Then I made 'telnet' to BDI. The following is the brief response.
VERIFY [<offset>] [<file> [<format>]] verify a program file to target memory PROG [<offset>] [<file> [<format>]] program flash memory <format> : SREC, BIN, AOUT, ELF or COFF ERASE [<address> [<mode>]] erase a flash memory sector, chip or block <mode> : CHIP, BLOCK or SECTOR (default is sector) ERASE <addr> <step> <count> erase multiple flash sectors UNLOCK <addr> <step> <count> unlock multiple flash sectors FLASH <type> <size> <bus> change flash configuration FENA <addr> <size> enable autoamtic programming to flash memory FDIS disable autoamtic programming to flash memory DELAY <ms> delay for a number of milliseconds SELECT <core> change the current core len : the number of bits 1..256 bx : a data byte, two hex digits HOST <ip> change IP address of program file host PROMPT <string> defines a new prompt string CONFIG display or update BDI configuration CONFIG <file> [<hostIP> [<bdiIP> [<gateway> [<mask>]]]] HELP display command list QUIT terminate the Telnet session
# CONFIG: cannot open BDI-new.cfg # CONFIG: cannot open BDI-new.cfg Core#0>
Means, it is not getting my BDI-new.cfg file even though the file is in /tftpboot/ directory on my PC while my PC is working as TFTP server. Why it is BDI is not able to read BDI-new.cfg ?
Try:
chmod a+r /tftpboot/BDI-new.cfg
That should fix it assuming tftp is properly configured and enabled on your RH8 development host.
-- Regards, George