
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?

In message E1Awx0E-000193-Ly@server4.anonymousnetworks.com 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
participants (2)
-
ppc user
-
Wolfgang Denk