Broken U-Boot packages?

[Tim Kientzle]

> On Jun 14, 2015, at 1:42 PM, Erik Moe <e.moe at rcn.com> wrote:
> 
> I'm booting off a Beaglebone Black SD image that I built two days ago using a slightly modified version of crochet that uses the u-boot from package.  This is what my boot image looks like:
> 
> root at beaglebone:~ # ls /boot/msdos/
> bbone.dtb       bboneblk.dtb    mlo             ubldr
> bbone.dts       bboneblk.dts    u-boot.img      uenv.txt

Thanks.  That gives me another data point to play with.

Tim

P.S.  Care to share your patches?

> 
> Erik
> 
> 
>> On Jun 14, 2015, at 1:20 PM, Tim Kientzle <tim at kientzle.com> wrote:
>> 
>> Has anyone else had success building images with the U-Boot *packages*?
>> 
>> I’m updating Crochet to use U-Boot from ports/packages for RPI and Beaglebone, but I get non-bootable images (generally with U-boot failing to identify the disk partitioning) when I use the package.  Here’s what I’ve tried so far:
>> 
>> * RPi built with U-Boot from package - non-bootable
>> * RPi built with U-Boot port compiled locally - works
>> * Beaglebone Black with U-Boot from package - non-bootable
>> 
>> Today I hope to try booting an old white Beaglebone and building the u-boot-beaglebone port locally to see if that follows the pattern.
>> 
>> For the record, my ports tree is up-to-date and I’m installing the packages onto a recent FreeBSD-CURRENT amd64 VM via:
>> 
>> $ pkg install sysutils/u-boot-rpi
>> 
>> Cheers,
>> 
>> Tim
>> 
>> _______________________________________________
>> freebsd-arm at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
>