u-boot: does not netboot quite the same as tow-boot

[colemickens]

(I'm not sure where else to put this for now, other than wondering if we should just get a tow-boot branch going? cc: @Madouura - I have done a fair bit of work in tow-boot, getting highly customizable rpi support and radxazero1 support going, though I've not had a chance to review those with samueldr or send them)

Tow-Boot flavors of u-boot play fine with my local network, properly getting a lease and discovering the tftp/netboot server via the DHCP lease.

However, it doesn't seem like the nixpkgs build does; it seems to get a lease but doesn't seem to be discovering the tftp server correctly.

U-Boot 2022.04-VisionFive (Jan 01 1980 - 00:00:00 +0000)StarFive

CPU:   rv64imafdc
Model: StarFive VisionFive V1
DRAM:  8 GiB
Core:  13 devices, 9 uclasses, devicetree: separate
MMC:   mmc@10000000: 0, mmc@10010000: 1
Loading Environment from SPIFlash... SF: Detected gd25lq128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

StarFive EEPROM format v1

--------EEPROM INFO--------
Vendor : StarFive Technology Co., Ltd.
Product full SN: VF7100A1-2204-D008E000-00000134
data version: 0x1
PCB revision: 0x1
BOM revision: A
Ethernet MAC address: 6c:cf:39:00:01:33
--------EEPROM INFO--------

In:    serial@12440000
Out:   serial@12440000
Err:   serial@12440000
Net:   dwmac.10020000
Autoboot in 2 seconds
dwmac.10020000 Waiting for PHY auto negotiation to complete.. done
Speed: 1000, full duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
DHCP client bound to address 192.168.63.253 (3866 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.63.253 (105 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
MMC CD is 0x1, force to True.
MMC CD is 0x1, force to True.
Card did not respond to voltage select! : -110

[colemickens]

If I manually call:

setenv serverip 192.168.1.10
bootp

then I get:

*** Warning: no boot file name; using 'C0A83FFD.img'                                                                                                                                        
Using dwmac.10020000 device                                                                                                                                                                 
TFTP from server 192.168.1.10; our IP address is 192.168.63.253                                                                                                                             
Filename 'C0A83FFD.img'.

which is okay, I haven't made a payload for it yet... and maybe this is a riscv64/visionfive thing, but I was hoping it was going to load a kernel+initrd rather than an image. (again, what I'm used to with Tow-Boot)

[colemickens]

I think this is a visionfive/u-boot issue: starfive-tech/u-boot#34

Also, I should have been using pxe instead of bootp to get the similar tow-boot pxe behavior. I think I see the patch that makes tow-boot try pxe as part of it's curated boot flow. When I set the serverip and call pxe, I see it behaving more like what I was expecting.

Going to close this because I just feel like this is probably a starfive u-boot issue to address.