Hello,

 

with an old image "Armbian_5.10_Bananapim2_Debian_jessie_4.5.2_nfsboot.raw" I could stop the boot process and use the u-boot dhcp command and the Pi gets propper values from my DHCP Server.

U-Boot SPL 2016.01-armbian (Apr 28 2016 - 10:35:52)
DRAM: 1024 MiB
Trying to boot from MMC


U-Boot 2016.01-armbian (Apr 28 2016 - 10:35:52 +0000) Allwinner Technology

CPU:   Allwinner A31s (SUN6I)
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0)
In:    serial
Out:   vga
Err:   vga
Net:   eth0: ethernet@01c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
scanning bus 0 for devices... 2 USB Device(s) found
Hit any key to stop autoboot:  0 
=> setenv autoload no
=> dhcp
ethernet@01c30000 Waiting for PHY auto negotiation to complete........ done
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 172.16.3.2 (4 ms)
=> printenv ipaddr netmask gatewayip hostname
ipaddr=172.16.3.2
netmask=255.255.0.0
gatewayip=172.16.0.1
hostname=bpi-m2
=>

Stopping U-Boot with an actual image "Armbian_5.11_Bananapim2_Debian_jessie_4.5.4.raw", the dhcp command timed out because no ethernet link could be established.

 

U-Boot SPL 2016.03-armbian (May 11 2016 - 19:22:27)
DRAM: 1024 MiB
Trying to boot from MMC


U-Boot 2016.03-armbian (May 11 2016 - 19:22:27 +0000) Allwinner Technology

CPU:   Allwinner A31s (SUN6I)
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0)
In:    serial
Out:   vga
Err:   vga
Net:   eth0: ethernet@01c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
scanning bus 0 for devices... 2 USB Device(s) found
Hit any key to stop autoboot:  0 
=> setenv autoload no
=> dhcp
ethernet@01c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
ethernet@01c30000: No link.
=> 

Without a working network I can't use U-Boot commands like dhcp and nfs. Is there a way to patch/fix U-Boot v2016.03 or is there an Armbian-style way to stay on U-Boot v2016.01?

Any help would be appreciated. Thanks.

Steve

 

PS: Without stopping the boot process the actual image boots without a problem.

 

 

Without a working network I can't use U-Boot commands like dhcp and nfs. Is there a way to patch/fix U-Boot v2016.03 or is there an Armbian-style way to stay on U-Boot v2016.01?

U-boot 2016.03 broke Ethernet for some devices, so Armbian build system is configured to use 2016.01 for now for sun4i, sun5i and sun7i. Since M2 belongs to sun6i family, it got 2016.03 - I'll add sun6i to exceptions list ASAP.

 

If you are getting 2016.03 via apt upgrade, you may want to install older version (or version from other branch) and prevent upgrading it (for now) with

apt-mark hold linux-u-boot-bananapim2-next
# or whatever package name u-boot for your device has

Thanks for your quick reply, zador.

Most of the time I build new images using compile.sh

 

BTW: Building the M2 image gives the following waring:

[ warn ] ... u-boot_v2016.01_Bananapro_defconfig.patch [ failed ]

Thanks for your quick reply, zador.

Most of the time I build new images using compile.sh

 

BTW: Building the M2 image gives the following waring:

[ warn ] ... u-boot_v2016.01_Bananapro_defconfig.patch [ failed ]

 

Safe to ignore if you are using M2 board.