For your info to finish off: as suggested by Robert Nelson, I upgraded to
v3.8.13-bone28. After spending time to get back to where I used to be in
bone20, I can now compile and load the overlay as expected:
>sudo sh -c "dtc -@ -O dtb -o BB-BONE-PRU-00A0.dtbo BB-BONE-PRU-00A0.dts"
>sudo sh -c "echo BB-BONE-PRU > $SLOTS"
pin 12 (44e10830) 00000006 pinctrl-single
and all is well.
Any suggestions on how to load the overlay and have the output come up low?
Thanks.
On Wednesday, October 23, 2013 2:38:27 PM UTC-4, Bit Pusher wrote:
>
> Update, recompiled with different name, and then overlay load appears to
> work
> /lib/firmware\> sudo sh -c "dtc -@ -O dtb -o cape-bone-pru-00A0.dtbo
> BB-BONE-PRU-00A0.dts"
> [19392.918341] bone-capemgr bone_capemgr.9: part_number 'BB-BONE-PRU',
> version 'N/A'
> [19392.918537] bone-capemgr bone_capemgr.9: slot #11: specific override
> [19392.918610] bone-capemgr bone_capemgr.9: bone: Using override eeprom
> data at slot 11
> [19392.918662] bone-capemgr bone_capemgr.9: slot #11:
> 'Bone-Black-PRU,00A0,na,BB-BONE-PRU'
> [19392.918969] bone-capemgr bone_capemgr.9: slot #11: Requesting firmware
> 'cape-bone-pru-00A0.dtbo' for board-name 'Bone-Black-PRU', version '00A0'
> [19392.919456] bone-capemgr bone_capemgr.9: slot #11: dtbo
> 'cape-bone-pru-00A0.dtbo' loaded; converting to live tree
>
> /lib/firmware\> cat $SLOTS
> 0: 54:PF---
> 1: 55:PF---
> 2: 56:PF---
> 3: 57:PF---
> 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
> 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
> 11: ff:P-O-L Bone-Black-PRU,00A0,na,BB-BONE-PRU
>
> /lib/firmware\> sudo cat $PINS | g 44e10830
> pin 12 (44e10830) 00000006 pinctrl-single
>
> I don't understand why unless the name cape-bone-pru-00A0.dtbo is compiled
> into device driver as an over-ride, but since this seems to work, I will go
> on. Still any clarifications or ideas would be appreciated. Thanks.
> Bit Pusher
>
> On Wednesday, October 23, 2013 2:17:15 PM UTC-4, Bit Pusher wrote:
>>
>> Kernel Version: ubuntu-armhf 3.8.13-bone20
>>
>> Overlay File: BB-BONE-PRU-00A0.dts (shown below)
>>
>> Compile: sudo sh -c "dtc -@ -O dtb -o BB-BONE-PRU-00A0.dtbo
>> BB-BONE-PRU-00A0.dts"
>> worked as far as I can tell
>>
>> Loading:
>> /lib/firmware\> echo $SLOTS
>> /sys/devices/bone_capemgr.9/slots
>> sudo sh -c "echo BB-BONE-PRU > $SLOTS"
>> worked as far as I can tell except when dmesg examined
>>
>> Tail of dmesg
>>
>> [14899.144156] bone-capemgr bone_capemgr.9: part_number 'BB-BONE-PRU',
>> version 'N/A'
>> [14899.144246] bone-capemgr bone_capemgr.9: slot #10: specific override
>> [14899.144271] bone-capemgr bone_capemgr.9: bone: Using override eeprom
>> data at slot 10
>> [14899.144289] bone-capemgr bone_capemgr.9: slot #10:
>> 'Bone-Black-PRU,00A0,na,BB-BONE-PRU'
>> [14899.144402] bone-capemgr bone_capemgr.9: slot #10: Requesting firmware
>> 'cape-bone-pru-00A0.dtbo' for board-name 'Bone-Black-PRU', version '00A0'
>> [14899.154045] bone-capemgr bone_capemgr.9: failed to load firmware
>> 'cape-bone-pru-00A0.dtbo'
>> /lib/firmware\>
>>
>> any ideas? Thanks.
>> Bit Pusher
>>
>>
>> /lib/firmware\> cat BB-BONE-PRU-00A0.dts
>> /*
>> * pru dts file BB-BONE-PRU-00A0.dts
>> */
>> /dts-v1/;
>> /plugin/;
>>
>> / {
>> compatible = "ti,beaglebone", "ti,beaglebone-black";
>>
>> /* identification */
>> part-number = "BB-BONE-PRU";
>> version = "00A0";
>>
>> exclusive-use =
>> "P8.12";
>>
>> fragment@0 {
>> target = <&am33xx_pinmux>;
>> __overlay__ {
>> mygpio: pinmux_mygpio{
>> pinctrl-single,pins = <
>> 0x30 0x06
>> >;
>> };
>> };
>> };
>>
>> fragment@1 {
>> target = <&ocp>;
>> __overlay__ {
>> test_helper: helper {
>> compatible = "bone-pinmux-helper";
>> pinctrl-names = "default";
>> pinctrl-0 = <&mygpio>;
>> status = "okay";
>> };
>> };
>> };
>>
>> fragment@2{
>> target = <&pruss>;
>> __overlay__ {
>> status = "okay";
>> };
>> };
>> };
>>
>>
--
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/groups/opt_out.
