On Wed, Dec 21, 2016 at 12:08:34PM +0800, CARL DONG wrote: > Matthieu! Thanks so much for your help! I'll try it out and let you know > how it goes. > > Is there a certain flavor of `sysutils/u-boot` that I need to install? I > see on OpenPorts.se that there are 2 flavors: > > 1. 'aarch64', and > 2. 'arm'. > > Not sure if that's referring to the architecture of the compiling machine > or the machine we're compiling for.
The architecture in the package name is the architecture the u-boot images are built for. You can install the packages themselves on any architecture. In this case you'd want u-boot-arm. Note that there are two possible targets that apply here one that uses 6x_bootscript /usr/local/share/u-boot/nitrogen6q/u-boot.imx and one that doesn't /usr/local/share/u-boot/mx6qsabrelite/u-boot.imx Given your current u-boot looks for 6x_bootscript, I'd try the nitrogen6q one first. That appears to be what matthieu is using as well. If you can take notes when updating the version of u-boot in spi flash then we could reuse them in INSTALL.armv7. Almost all the other systems load u-boot from an sd/mmc device. > > Anyways, thanks so much for the help. Have a great day sir! > > On Tue, Dec 20, 2016 at 10:24 PM, Matthieu Herrb <matth...@herrb.eu> wrote: > > > On Tue, Dec 20, 2016 at 08:58:50PM +0800, CARL DONG wrote: > > > I see that "Boundary Devices SABRE Lite/BD-SL-i.MX6" is listed as > > supported > > > on the armv7 page, but I'm unable to get it working because of the EFI > > > interface requirement for the firmware. > > > > > > 1. `run findfdt` outputs `## Error: "findfdt" not defined` > > > 2. `bootefi` is an unknown command > > > > > > I believe this is because the device was shipped with U-Boot > > > 2015.07-15072-g45cfc85, and the latest branch the vendor's released is > > > based on v2016.03 ( > > > https://github.com/boundarydevices/u-boot-imx6/tree/boundary-v2016.03). > > > According to 'INSTALL.armv7', we need U-Boot 2016.07 or newer. > > > > > > Would love to know if there are other ways to boot in. > > > > Yes. You need to use the u-boot from ports. iirc there is no way on > > the sabre lite to start u-boot from an SD card or from the the net; > > you first need to flash it using the 'upgradeu' command from the > > shipped U-Boot that will read a file called 'u-boot.imx' on the SD > > card and flash it. > > > > I have a sabre lite board running at home. My notes below are from > > last july. I haven't tried to upgrade to a more recent u-boot. Things > > may have changed a bit. > > > > Once you have a working u-boot flashed, you will need to hack a > > '6x_bootscript' boot script a bit to actually launch the EFI boot > > program. > > > > Here is my 6x_bootscript.txt: > > > > ---cut--- > > load ${dtype} ${disk}:1 0x13000000 imx6q-sabrelite.dtb > > load ${dtype} ${disk}:1 0x10800000 efi/boot/bootarm.efi > > bootefi 0x10800000 0x13000000 > > echo "Error loading uefi boot loader" > > ---cut--- > > > > I converted it to a u-boot script using the following command: > > > > mkimage -A arm -T script -C none -n 'boot script' -d 6x_bootscript.txt > > 6x_bootscript > > > > and copied it in the DOS partition of my hard-drive. > > > > > > Note: If flashing U-boot fails, you need a windows or Linux machine to > > unbrick it : > > https://boundarydevices.com/unbricking-nitrogen6x-sabre-lite-i-mx6-board/ > > https://www.element14.com/community/community/designcenter/single-board- > > computers/sabrelite/blog/2014/04/01/getting-started-with-sabre-lite-imx6 > > > > I needed that unbrick procedure a number of times before I got u-boot > > working. So make sure to get familiar with the procedure before > > starting... > > > > -- > > Matthieu Herrb > >
