I was grepping /sys/kernel/debug/pinctrl/44e10800.pinmux/pins for 994 -B 4 
-A4 

and loading my overlay manually: "echo openpegasus > 
/sys/devices/platform/bone_capemgr/slots"

According to dmesg it seems like it accepts my overlay without error.

I'll keep the above in mind when I try to load it by default on boot.

/Jason

On Friday, December 16, 2016 at 1:41:28 PM UTC-5, William Hermans wrote:
>
> So whatever way that works for you, is the right way. But yes, in my own 
>> opinion loading from uEnv.txt is the proper way. As the pin configurations 
>> take place the quickest possible after a boot. 
>>
>>
>>    1. So you need the overlay in /lib/firmware of course.
>>    2. Then you need to add the overlay to the 
>>    cape_enable=bone_capemgr.enable_partno= line in uEnv.txt
>>    3. Finally you'll need to update the initramfs
>>
>> To update the initramfs You need to:
>>
>> william@beaglebone:~$ cd /opt/scripts/
>> william@beaglebone:/opt/scripts$ git pull /* So you need to sudo apt-get 
>> install git - If not already installed */
>>
>> william@beaglebone:/opt/scripts$ cd tools/developers/
>>
>> william@beaglebone:/opt/scripts/tools/developers$ sudo ./update_initrd.sh
>>
>> william@beaglebone:/opt/scripts/tools/developers$ sudo reboot
>>
>> Then your custom overlay will be "injected" into the initramfs, and 
>> properly load at boot.
>>
>
>
> On Fri, Dec 16, 2016 at 11:39 AM, William Hermans <[email protected] 
> <javascript:>> wrote:
>
>> Jay,
>>
>> If by "updating" you mean your overlay isn't loading at boot. That would 
>> be because the overlay is not in the initramfs. Which is needed for the 
>> latest images. I actually posted on the groups about this a few days go, so 
>> I'll find my post and copy paste the procedure here.
>>
>> If this is not what you mean, post back and describe in more detail what 
>> you mean by "updating".
>>
>> On Fri, Dec 16, 2016 at 11:23 AM, Jay Doobie <[email protected] 
>> <javascript:>> wrote:
>>
>>> Hi TJF: is there some place I can find more info on the DT's across 
>>> kernels?  I'm using 4.4.30-ti-r64.  I have access to the PRU, and I think 
>>> my DT isn't updating anything (even though it seems to install properly).  
>>> My DT can be seen here:
>>>
>>>
>>> https://github.com/doobie42/OpenPegasus/blob/master/dto/openpegasus-00A0.dtsi
>>>
>>> Thanks,
>>> Jason
>>>
>>> On Friday, December 16, 2016 at 11:06:35 AM UTC-5, TJF wrote:
>>>>
>>>> Hello Jay!
>>>>
>>>> You need not adapt the device tree when you use a bone kernel. (The 
>>>> device tree fixup is for TI kernels only.)
>>>>
>>>> Am Freitag, 16. Dezember 2016 05:44:26 UTC+1 schrieb Jay Doobie:
>>>>>
>>>>> I figured out what happened, it wasn't am335x-boneblack.dts, but 
>>>>> am335x-boneblack-wireless.dts.  Seems like I can talk to the PRU, but I 
>>>>> don't see it doing what it should be doing.  Need to grab a copy of 
>>>>> prudebug and see if I can debug what the PRU is trying to do vs. is doing.
>>>>>
>>>>
>>>> PRU software is independant from the kernel. Once the driver is loaded 
>>>> accordingly, all should work. (Exept the PWM outputs of the eHRPWM modules 
>>>> in the PWMSS subsystems.)
>>>>
>>>> Regards
>>>>
>>> -- 
>>> 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] <javascript:>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/beagleboard/62ff2009-8a84-49d7-b8e4-b71f2bdd3867%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/beagleboard/62ff2009-8a84-49d7-b8e4-b71f2bdd3867%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/255d6cdc-7ba5-4d31-9f81-dbb1c96bba9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to