On Wed, Jun 22, 2016 at 10:47:43PM -0300, Daniel Bolgheroni wrote: > On Mon, May 30, 2016 at 12:02:32AM +1000, Jonathan Gray wrote: > > There is now a bootloader for armv7 thanks to kettenis@ > > Recent armv7 snapshots will configure disks to use efiboot and install > > device tree dtb files on a fat partition at the start of the disk. > > > > u-boot kernel images are no longer part of the release but can still > > be built for the time being. We are going to start assuming the > > kernel has been loaded with a dtb file to describe the hardware sometime > > soon. Those doing new installs can ignore the details but here they > > are. > > > > Support for EFI payloads was introduced in u-boot 2016.05, a port > > was recently imported for u-boot along with a patch to prevent > > it from allocating memory from non-populated regions (required for > > non imx platforms). A dtb port with prebuilt dtb files was also added. > > > > If BOOTARM.EFI is placed on fat or ext2 as /efi/boot/bootarm.efi and > > dtb files placed in /, /dtb/ or /dtb/current u-boot will automatically > > load and run it without any boot.scr or uenv.txt needed. efiboot will > > then load kernel images off ffs filesystems it finds. The u-boot > > binaries themselves on the same partition or raw offset remain largely > > board specific. > > After the introduction of U-Boot 2016.05 and the bootloader, I am unable to > boot images via tftpd. It was a very convenient way to test kernels compiled > with a BeagleBone Black to boot a Cubieboard 2. > > I am generating the .umg by hand with the following: > > # mkuboot -a arm -o linux -e 0x40300000 -l 0x40300000 bsd bsd.SUNXI.umg > > This is what was used by distrib/armv7/ramdisk/Makefile before being removed > on > revision 1.13. > > By the way, on Cubieboard 2, I'm using a modified miniroot-cubie-60.fs with > the > u-boot obtained from sysutils/u-boot port and the corresponding > sun7i-a20-cubieboard2.dtb obtained from sysutils/dtb and put on / so u-boot > can > find it. > > Are there any other way to boot via network? I thought of pxe, which u-boot > supports, but armv7 has no pxeboot. > > Thank you.
u-boot 2016.07 will support network access from efi payloads. With the tftp/bootp/rarp/nfs code in libsa it should be possible to create a netboot.efi that will try load root/kernel from nfs. > > -- > output: > > U-Boot 2016.05 (Jun 13 2016 - 23:57:44 -0600) Allwinner Technology > > CPU: Allwinner A20 (SUN7I) > Model: Cubietech Cubieboard2 > I2C: ready > DRAM: 1 GiB > MMC: SUNXI SD/MMC: 0 > *** Warning - bad CRC, using default environment > > In: serial > Out: serial > Err: serial > SCSI: Target spinup took 0 ms. > AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode > flags: ncq stag pm led clo only pmp pio slum part ccc apst > Net: eth0: ethernet@01c50000 > starting USB... > USB0: USB EHCI 1.00 > USB1: USB OHCI 1.0 > USB2: USB EHCI 1.00 > USB3: USB OHCI 1.0 > scanning bus 0 for devices... 1 USB Device(s) found > scanning bus 2 for devices... 1 USB Device(s) found > Hit any key to stop autoboot: 0 > => setenv ipaddr 192.168.1.7; setenv serverip 192.168.1.5; tftpboot > bsd.SUNXI.umg; bootm > Speed: 100, full duplex > Using ethernet@01c50000 device > TFTP from server 192.168.1.5; our IP address is 192.168.1.7 > Filename 'bsd.SUNXI.umg'. > Load address: 0x42000000 > Loading: ################################################################# > ################################################################# > ################################################################# > ################################################################# > ################################################################# > #################### > 3.2 MiB/s > done > Bytes transferred = 5052180 (4d1714 hex) > ## Booting kernel from Legacy Image at 42000000 ... > Image Name: boot > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 5052116 Bytes = 4.8 MiB > Load Address: 40300000 > Entry Point: 40300000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > > Starting kernel ... > > > -- > db >
