bootp
I'm using u-boot 1.0.0 on a xilinx embedded ppc 405 and I see the follow unexplained behavior:
if I do a bootp <address> <filename> it always bootp's the filename stored in environment variable bootfile rather than the filename I specify in the command line. If I have no bootfile env variable it tries to bootp a garbage file name.
If I use tftpboot <address> <filename> it gets the file name on the cmd line.
I don't think this is expected behavior. Is that incorrect? Any ideas what I'm doing wrong?
Quoted 7 lines · In message <[email protected]> you wrote:
I'm using u-boot 1.0.0 on a xilinx embedded ppc 405 and I see the follow unexplained behavior:
if I do a bootp <address> <filename> it always bootp's the filename stored in environment variable bootfile rather than the filename I specify in the command line. If I have no bootfile env variable it tries to bootp a garbage file name.
What does the reply packet sent by your BOOTP server contain exactly?
Best regards,
Wolfgang Denk
Signature · 3 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de If God had a beard, he'd be a UNIX programmer.