OK Success. Got it working.
I blended two types of overlays I have seen on the web, this is what the
final working version looked like. My notable changes were in fragment 1 -
pru_pru_pins_pinmux { } addition and the compatible =
"bone-pinmux-helper"; (whatever that is :) seemed helpful)
I also in fragment 0 set a basic output pinmux to mode / settings of 0x05
(simple output).
Thank-you everyone for digging in!
*/dts-v1/;*
*/plugin/;*
*/ {*
* compatible = "ti,beaglebone", "ti,beaglebone-black";*
* /* identification */*
* part-number = "BB-BONE-PRU";*
* version = "00A0";*
* /* state the resources this cape uses */*
* exclusive-use =*
* /* the pin header uses */*
* "P9.27", /* pru0: pr1_pru0_pru_r30_5 */*
* /* the hardware IP uses */*
* "pr1_pru0_pru_r30_5";*
* fragment@0 {*
* target = <&am33xx_pinmux>;*
* __overlay__ {*
* pru_pru_pins: pinmux_pru_pru_pins {*
* pinctrl-single,pins = <*
* 0x1A4 0x05 // CS P9_27 pr1_pru0_pru_r30_5, MODE5 | OUTPUT |*
* >;*
* };*
* };*
* };*
* fragment@1 {*
* target = <&ocp>;*
* __overlay__ {*
* pru_pru_pins_pinmux {*
* compatible = "bone-pinmux-helper";*
* status = "okay";*
* pinctrl-names = "default";*
* pinctrl-0 = <&pru_pru_pins>;*
* };*
* };*
* };*
*};*
Now I get the proper pin config - P9.27 = Pin 105
pin 100 (44e10990.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 101 (44e10994.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 102 (44e10998.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 103 (44e1099c.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 104 (44e109a0.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 105 (44e109a4.0): ocp:pru_pru_pins_pinmux (GPIO UNCLAIMED) function
pinmux_pru_pru_pins group pinmux_pru_pru_pins
pin 106 (44e109a8.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 107 (44e109ac.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 108 (44e109b0.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 109 (44e109b4.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 110 (44e109b8.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 111 (44e109bc.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 112 (44e109c0.0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
On Monday, November 7, 2016 at 11:21:46 PM UTC-7, Neil Jubinville wrote:
>
> I am working on a generic * 0x1A4 0x05* mode setting, just sitting down
> now for some more punishment.
>
> two other good resources on this are
> http://www.ofitselfso.com/BeagleNotes/UsingDeviceTreesToConfigurePRUIOPins.php
>
> and this video at this time https://youtu.be/wui_wU1AeQc?t=630 it talks
> about the config pin byte structure.
>
> I read another post about a guy having a similar issue to me in that the
> pin was not responding on the dtb/o at
> https://groups.google.com/forum/?hl=en#!category-topic/beagleboard/pru/k6RACGRSwfc
>
> turns out he was blocked by the HDMI - on P8
>
> Make me wonder if some how these P9 pins in Roberts base dtb are somehow
> allocated. I'll have to dig in deeper.
>
> Neil
>
>
> On Monday, November 7, 2016 at 7:40:21 PM UTC-7, William Hermans wrote:
>>
>> Then here: http://beaglebone.cameon.net/home/pin-muxing says a couple of
>>> my assumptions were wrong. 0x25h seems correct.
>>
>>
>>
>> Blah, I got it wrong again. Seems 0xD was correct. But anyway, you have
>> the means to do what you need. Just make sure you read the second link
>> correctly. I got it wrong at first look because instead of reading what
>> each bit Fields is intended to mean, I made assumptions again . . . like
>> disabled = 0 when actually according to that page disabled = 1 . . .
>>
>> On Mon, Nov 7, 2016 at 7:22 PM, Greg <[email protected]> wrote:
>>
>>> YES, that is the rub!
>>>
>>> Robert's description of what to do had to be stared at a bit, but
>>> actually it is very easy and it worked first time.
>>>
>>> I've got a BB Green, so I will re-iterate the particular steps required
>>> for Remoteproc:
>>>
>>> 1. Clone Robert's github repository:
>>> git clone https://github.com/RobertCNelson/dtb-rebuilder
>>>
>>> 2. cd dtb-rebuilder/
>>> cd src/arm
>>>
>>> 3. Now you will need to find and edit the top of the device tree dts
>>> file.
>>> For BBG, this is:
>>> am335x-bonegreen.dts
>>>
>>> The only thing you have to do is to uncomment:
>>> /* #include "am33xx-pruss-rproc.dtsi" */
>>>
>>> unquote the line:
>>> #include "am33xx-pruss-rproc.dtsi"
>>>
>>> Save and exit.
>>>
>>> 4. cd /etc/modprobe.d
>>> Create a new file named:
>>> pruss-blacklist.conf
>>>
>>> Add this single line to the file:
>>> blacklist uio_pruss
>>>
>>> Save and exit.
>>>
>>> 5. cd back to dtb-rebuilder
>>>
>>> make
>>> sudo make install
>>> sudo reboot
>>>
>>> After the above process, PRUs entries appear in
>>> /sys/bus/platform/devices, and the RPMsg example with character device in
>>> /dev is working!
>>>
>>> I will add the above process steps to the chapter on PRU compiler set-up
>>> in my Remoteproc ADC github project.
>>>
>>> Thanks!
>>> Greg
>>>
>>> --
>>> 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/4431b19a-668e-44bc-890d-9b2dc92c46b8%40googlegroups.com
>>>
>>> <https://groups.google.com/d/msgid/beagleboard/4431b19a-668e-44bc-890d-9b2dc92c46b8%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/50214abc-07a3-4a0e-8607-69b56370acf3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
