Robert,
The dtbo file is present on the system. Below is the serial boot log
U-Boot 2015.04-svn40 (Oct 23 2015 - 08:19:16)
Watchdog enabled
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
reading uEnv.txt
983 bytes read in 6 ms (159.2 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from uEnv.txt
Importing environment from mmc ...
Checking if uenvcmd is set ...
gpio: pin 56 (gpio 56) value is 1
Running uenvcmd ...
924 bytes read in 40 ms (22.5 KiB/s)
6948760 bytes read in 430 ms (15.4 MiB/s)
5082010 bytes read in 329 ms (14.7 MiB/s)
54462 bytes read in 124 ms (428.7 KiB/s)
Kernel image @ 0x82000000 [ 0x000000 - 0x6a0798 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Using Device Tree in place at 88000000, end 880104bd
Starting kernel ...
The uenv.txt on the boot partition is:
##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.
loadaddr=0x82000000
fdtaddr=0x88000000
rdaddr=0x88080000
initrd_high=0xffffffff
fdt_high=0xffffffff
##These are needed to be compliant with Debian 2014-05-14 u-boot.
loadximage=load mmc 0:2 ${loadaddr} /boot/vmlinuz-${uname_r}
loadxfdt=load mmc 0:2 ${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}
loadxrd=load mmc 0:2 ${rdaddr} /boot/initrd.img-${uname_r}; setenv rdsize
${filesize}
loaduEnvtxt=load mmc 0:2 ${loadaddr} /boot/uEnv.txt ; env import -t
${loadaddr} ${filesize};
check_dtb=if test -n ${dtb}; then setenv fdtfile ${dtb};fi;
loadall=run loaduEnvtxt; run check_dtb; run loadximage; run loadxrd; run
loadxfdt;
mmcargs=setenv bootargs console=${console} ${optargs} no_console_suspend=1
vt.global_cursor_default=0 consoleblank=0 ${cape_disable} ${cape_enable}
root=/dev/mmcblk0p2 rootfstype=${mmcrootfstype} ${cmdline}
uenvcmd=run loadall; run mmcargs; bootz ${loadaddr} ${rdaddr}:${rdsize}
${fdtaddr};
Thanks for your help.
On Thursday, November 5, 2015 at 2:07:23 PM UTC-5, RobertCNelson wrote:
>
> On Thu, Nov 5, 2015 at 12:24 PM, jason <[email protected] <javascript:>>
> wrote:
> > I am attempting to update my beaglebone black Rev C to the 4.1 kernel
> from
> > https://github.com/RobertCNelson/bb-kernel and filesystem from
> >
> https://rcn-ee.com/rootfs/eewiki/minfs/debian-8.2-minimal-armhf-2015-09-07.tar.xz
>
> >
> > uname -a: Linux arm 4.1.10-bone16 #2 Tue Oct 27 19:53:33 EDT 2015 armv7l
> > GNU/Linux
> >
> > I am having an issue loading capes from the kernel command line.I
> downloaded
> > and installed the bb.org overlays per the eewiki instructions without
> issue,
> > however capemgr will not load the dtbo files on boot. I can load them
> > manually without an issue after the kernel boots or by specifying them
> in
> > /etc/default/capemgr. This behavior appears similar to what would occur
> when
> > the .dtbo is not loaded into the initrd, however I have run the
> > /opt/scripts/tools/developers/update_initrd.sh and it made no
> difference. Is
> > there a step I might have missed along the way.
>
> Sounds like either the initrd is not being used or the dtbo objects
> aren't present..
>
> Make sure this file:
>
>
> https://raw.githubusercontent.com/rcn-ee/repos/master/bb-customizations/suite/jessie/debian/dtbo
>
>
> exists
>
> /usr/share/initramfs-tools/hooks/dtbo
>
> If you can please add a serial boot log, i want to see what u-boot's
> doing with the initrd. ;)
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
