dhcp: doesn't seem to set serverip like other u-boot builds?

[colemickens]

edit: (I hate that "enter" in the title box will just post an empty issue, this has been a github thing for years and I still trigger it sometimes, sorry)

will send the actual content as a separate post for the sake of email users.

[colemickens]

When I issue dhcp on a VisionFive u-boot build, it gets a lease, but:

1. the router doesn't really recognize it, it sees the client but doesn't acknowledge that it gave it an IP?
2. I can see the u-boot client get an IP, presumably via DHCP response, but it doesn't set serverip. I (confirmed minutes ago) have Raspberry Pi clients that dhcp/tftp boot into u-boot and then further PXE boot into linux. So they're getting the correct tftp/pxe information from my router, yet...

VisionFive #dhcp
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.63.253 (109 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET

[colemickens]

I do also apologize, I don't really know u-boot's code or your changes enough to know if this is even something that would be board specific or not. However, based on all docs I've read, just calling dhcp should normally result in serverip being set.

[colemickens]

Is this maybe related?

• Enable NET_RANDOM_ETHADDR for temporary solution, because micrel_ksz8xxx
  driver does not support DM_ETH yet, so cannot read MAC address directly.

ref: 4992090

[colemickens]

note, I also had to do this:

setenv pxefile_addr_r 0x88200000

which hopefully would be set for me

[colemickens]

The PROXY_DHCP setting was the culprit. I did manage to get a build of Tow-Boot working that netboots properly from my network like other tow-boot/upstream u-boot builds do.