bootp problems with rpi4

[Matthias Brugger]

Hi Nicolas,

On 21/03/2020 19:57, Nicolas Meaux wrote:
> Hello,
> 
> I use u-boot for raspberry, but i have a different behavior between rpi3b and
> rpi4b.
> * i use the same u-boot source files (2020.04-rc3-00161-g14eb12a3c8)
> * i use the same method for compiling ( make -j4 ARCH=arm
> CROSS_COMPILE=aarch64-linux-gnu- all )
> * i use the same dhcp/tftp server in both case .
> * i just load a different config :  rpi_3_defconfig & rpi_4_defconfig
> 
> When i boot with my rpi3b, it happens the following :
> * 1st bootp ok
> * tftp download boot.scr.uimg file
> * 2nd bootp ok
> * tftp load the "bootfile filename" setup in the dhcp config which is an efi
> application
> * efi application is loaded and the rest of the boot process is fine.
> 
> When i boot with my rpi4b, it happens the following :
> * 1st bootp ok
> * tftp download boot.scr.uimg file
> * 2nd bootp nok and goes into timeout, with a tcpdump on the ethernet interface
> connected to the pi, absolutely 0 bootp requested are made by u-boot at this step.
> 
> ***** U-boot log with rpi3b :
> U-Boot 2020.04-rc3-00161-g14eb12a3c8 (Mar 21 2020 - 18:41:52 +0100)
> 
> DRAM:  948 MiB
> RPI 3 Model B (0xa02082)
> MMC:   mmc at 7e202000: 0, sdhci at 7e300000: 1
> Loading Environment from FAT... WARNING at
> drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> Card did not respond to voltage select!
> In:    serial
> Out:   vidconsole
> Err:   vidconsole
> Net:   No ethernet found.
> starting USB...
> Bus usb at 7e980000: scanning bus usb at 7e980000 for devices... 3 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> Card did not respond to voltage select!
> Card did not respond to voltage select!
> 
> Device 0: unknown device
> Waiting for Ethernet connection... done.
> BOOTP broadcast 1
> BOOTP broadcast 2
> BOOTP broadcast 3
> DHCP client bound to address 10.0.0.3 (2245 ms)
> Using smsc95xx_eth device
> TFTP from server 10.0.0.254; our IP address is 10.0.0.3
> Filename 'boot.scr.uimg'.
> Load address: 0x2400000
> Loading: ################################################## 322 Bytes
>          34.2 KiB/s
> done
> Bytes transferred = 322 (142 hex)
> ## Executing script at 02400000
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> Card did not respond to voltage select!
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> Card did not respond to voltage select!
> Bad Linux ARM64 Image magic!
> Waiting for Ethernet connection... done.
> BOOTP broadcast 1
> BOOTP broadcast 2
> BOOTP broadcast 3
> *** Unhandled DHCP Option in OFFER/ACK: 60
> *** Unhandled DHCP Option in OFFER/ACK: 60
> DHCP client bound to address 10.0.0.3 (2195 ms)
> Using smsc95xx_eth device
> TFTP from server 10.0.0.254; our IP address is 10.0.0.3
> Filename 'snp.efi'.
> Load address: 0x1000000
> Loading: ################################################## 162.7 KiB
>          2.4 MiB/s
> done
> Bytes transferred = 166624 (28ae0 hex)
> Waiting for Ethernet connection... done.
> Using smsc95xx_eth device
> TFTP from server 10.0.0.254; our IP address is 10.0.0.3
> Filename 'dtb/broadcom/bcm2837-rpi-3-b.dtb'.
> Load address: 0x2600000
> Loading: ################################################## 19.1 KiB
>          83 KiB/s
> done
> Bytes transferred = 19530 (4c4a hex)
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> WARNING at drivers/mmc/bcm2835_sdhost.c:411/bcm2835_send_command()!
> Card did not respond to voltage select!
> Scanning disk mmc at 7e202000.blk...
> Disk mmc at 7e202000.blk not ready
> Card did not respond to voltage select!
> Scanning disk sdhci at 7e300000.blk...
> Disk sdhci at 7e300000.blk not ready
> Found 0 disks
> efi_load_pe: Invalid DOS Signature
> iPXE initialising devices...ok
> 
> 
> 
> iPXE 1.20.1+ (g18dc) -- Open Source Network Boot Firmware -- http://ipxe.org
> 
> 
> ***** U-boot log with rpi4b :
> U-Boot 2020.04-rc3-00161-g14eb12a3c8 (Mar 19 2020 - 22:02:29 +0000)
> 
> DRAM:  1.9 GiB
> RPI 4 Model B (0xb03111)
> MMC:   emmc2 at 7e340000: 0, mmcnr at 7e300000: 1
> Loading Environment from FAT... Card did not respond to voltage select!
> In:    serial
> Out:   serial
> Err:   serial
> Net:   eth0: genet at 7d580000
> Hit any key to stop autoboot:  0
> Card did not respond to voltage select!
> Card did not respond to voltage select!
> BOOTP broadcast 1
> BOOTP broadcast 2
> BOOTP broadcast 3
> DHCP client bound to address 10.0.0.4 (2010 ms)
> Using genet at 7d580000 device
> TFTP from server 10.0.0.254; our IP address is 10.0.0.4
> Filename 'boot.scr.uimg'.
> Load address: 0x2400000
> Loading: #
>          332 KiB/s
> done
> Bytes transferred = 340 (154 hex)
> ## Executing script at 02400000
> Card did not respond to voltage select!
> Scanning disk emmc2 at 7e340000.blk...
> Disk emmc2 at 7e340000.blk not ready
> Card did not respond to voltage select!
> Scanning disk mmcnr at 7e300000.blk...
> Disk mmcnr at 7e300000.blk not ready
> Found 0 disks
> efi_load_pe: Invalid DOS Signature
> Card did not respond to voltage select!
> Card did not respond to voltage select!
> Bad Linux ARM64 Image magic!

That should give you a hint. Which file do you try to execute here?

If you don't know, you can try to set xtrace which should give you more
information of the shell commands executed:

setnenv xtrace 1
boot

Regards,
Matthias

> BOOTP broadcast 1
> BOOTP broadcast 2
> BOOTP broadcast 3
> BOOTP broadcast 4
> BOOTP broadcast 5
> BOOTP broadcast 6
> BOOTP broadcast 7
> BOOTP broadcast 8
> BOOTP broadcast 9
> BOOTP broadcast 10
> BOOTP broadcast 11
> BOOTP broadcast 12
> BOOTP broadcast 13
> BOOTP broadcast 14
> BOOTP broadcast 15
> BOOTP broadcast 16
> BOOTP broadcast 17
> 
> Retry time exceeded; starting again
> U-Boot>
> 
> 
> Thx in advance for any help.
> 
> Rgds,
> 
> Nicolas
>