*Background Information:*
I am using a standard Beaglebone Black with the latest version of Angstrom
(2013.09.04) loaded.
I developed software to that uses eqep2 on the Beaglebone Black and it
works well, I get the correct results from the quadrature counter.
*Problem Description:*
A problem is that the related Device Tree Overlay in conjunction with the
Cape Manager cause my BBB boot-up time to extend beyond 60 seconds, and it
seems to be related to the cape manager trying to load cape firmware as the
snippet from the boot-up sequence, shown below, suggests.
However, in essence I do not have an actual cape, I merely assign the eqep2
pins to P8.39, 40, 41 and 42 using a Device Tree Overlay and then access
the eqep2 registers
using mmap in my software, and as mentioned earlier it works as expected.
[ 0.480195] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status
-22
[ 0.487510] pinctrl-single 44e10800.pinmux: could not request pin 21 on
device pinctrl-single
[ 60.501312] bone-capemgr bone_capemgr.9: failed to load firmware
'bone_eqep2-00A0.dtbo'
systemd-fsck[90]: Angstrom: clean, 49347/112672 files, 304984/449820 blocks
[ 68.329939] libphy: PHY 4a101000.mdio:01 not found
[ 68.335035] net eth0: phy 4a101000.mdio:01 not found on slave 1
.---O---.
| | .-. o o
| | |-----.-----.-----.| | .----..-----.-----.
| | | __ | ---'| '--.| .-'| | |
| | | | | |--- || --'| | | ' | | | |
'---'---'--'--'--. |-----''----''--' '-----'-'-'-'
-' |
'---'
The Angstrom Distribution beaglebone ttyO0
*Question(s):*
Is there a way to prevent the Cape Manager to actually load cape firmware?
Is there a different way to speed up the boot time?
Regards
Becker
--
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.
