[Bug 201813] sysutils/u-boot-cubox-hummingboard: No valid device tree blob found
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Jul 24 12:14:16 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201813
Bug ID: 201813
Summary: sysutils/u-boot-cubox-hummingboard: No valid device
tree blob found
Product: Ports & Packages
Version: Latest
Hardware: arm
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: ian at FreeBSD.org
Reporter: mikael.urankar at gmail.com
CC: freebsd-arm at FreeBSD.org
Flags: maintainer-feedback?(ian at FreeBSD.org)
CC: freebsd-arm at FreeBSD.org
Assignee: ian at FreeBSD.org
Created attachment 159142
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=159142&action=edit
boot fix
Hi,
I'm seeing this error on a cubox i4pro with the snapshot image:
U-Boot SPL 2013.10-rc4 (Jul 22 2015 - 21:50:39)
<snip>
FreeBSD/armv6 U-Boot loader, Revision 1.2
(root at releng2.nyi.freebsd.org, Wed Jul 22 22:10:10 UTC 2015)
DRAM: 2048MB
Number of U-Boot devices: 2
U-Boot env: loaderdev='mmc 0'
Found U-Boot device: disk
Checking unit=0 slice=<auto> partition=<auto>... good.
/boot/kernel/kernel data=0x592a9c+0x3d564 syms=[0x4+0x60540+0x4+0x5bc47]
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
No valid device tree blob found!
CuBox-i U-Boot > printenv SetupFdtfile
SetupFdtfile=env exists fdt_file || env set fdt_file
${fdt_soc}-${fdt_board}.dtb;
CuBox-i U-Boot > printenv fdt_file
fdt_file=imx6q-.dtb
CuBox-i U-Boot > printenv fdt_board
## Error: "fdt_board" not defined
The attached patch fixes the problem:
CuBox-i U-Boot > printenv fdt_file
fdt_file=imx6q-cubox-i.dtb
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list