Hello everyone, I'm trying to run an example of PRU to flash a led and I'm 
using P9_41 and P9_27, but to no working.

Can someone help me?

I created a dts and accredited that is correct, see the output of the 
show-pins.pl script:
P9.31 / hdmi audio clk           100 A13 fast rx down 7 gpio 3.14
P9.29 / hdmi audio fs            101 B13 fast rx down 7 gpio 3.15
P9.30                            102 D12 fast rx down 7 gpio 3.16
P9.28 / hdmi audio data          103 C12 fast rx down 7 gpio 3.17
P9.42b                           104 B12 fast rx down 7 gpio 3.18
*P9**.27*                            105 C13 fast         7 gpio 3.19       
 pruss@4a300000 (pinmux_pru_pru_pins)
*P9**.41*                            106 D13 fast         7 gpio 3.20       
 pruss@4a300000 (pinmux_pru_pru_pins)
P9.25 / audio osc                107 A14 fast rx down 7 gpio 3.21
P9.41 / jtag emu3                109 D14 fast rx down 7 gpio 0.20


Here my DTS:
/dts-v1/;
/plugin/;

#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/pinctrl/am33xx.h>

 / {
   // This determines which boards can use this DTS overlay
   compatible = "ti,beaglebone", "ti,beaglebone-green", 
"ti,beaglebone-black";

   // I think part-number is supposed to correspond with the filename,
   // so we'd save this as "PRU-GPIO-MTV-00A0.dts".
   part-number = "PRU-GPIO-MTV";

   version = "00A0";

   exclusive-use =
      "P9.41", "P9.27", "pru0";

   fragment@0 {
    target = <&am33xx_pinmux>;
    __overlay__ {
      example_pins: pinmux_pru_pru_pins {

       pinctrl-single,pins = <
         0x1a8 0x0f
         0x1a4 0x0f
       >;
      };
    };
   };

   // This enables the PRU and assigns the GPIO pins to it for use in EGP 
mode.
   fragment@1 {
    target = <&pruss>;
    __overlay__ {
      status = "okay";
      pinctrl-names = "default";
      pinctrl-0 = <&example_pins>;
    };
   };
 };


Em domingo, 5 de novembro de 2017 12:51:29 UTC-2, Jason Kridner escreveu:
>
>
>
> > On Nov 5, 2017, at 8:54 AM, Robert Nelson <[email protected] 
> <javascript:>> wrote: 
> > 
> >> On Sun, Nov 5, 2017 at 12:26 AM, Alek Mabry <[email protected] 
> <javascript:>> wrote: 
> >> Everything seems to work up until: 
> >> 
> >> debian@beaglebone:/var/lib/cloud9/2ecf864e1b3f250bad82c0eae12b7b64$ 
> sudo 
> >> config-pin p9.30 pruout 
> >> 
> >> P9_30 pinmux file not found! 
> >> 
> >> bash: /sys/devices/platform/ocp/ocp*P9_30_pinmux/state: No such file or 
> >> directory 
> >> 
> >> Cannot write pinmux file: 
> /sys/devices/platform/ocp/ocp*P9_30_pinmux/state 
> > 
> > P9_30 = hdmi audio 
> > 
> > https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays 
> > 
> > So you add: 
> > 
> > disable_uboot_overlay_audio=1 
> > 
> > to /boot/uEnv.txt 
>
> Looks like I chose a bad pin for a good default demo. This is a different 
> pin than used for the on-board LED. I tried to show both a PRU GPIO (via 
> p9.30) and an OCP GPIO via the on-board LED. 
>
> So, the LED still blinks because it is a different line that is controlled 
> via the OCP GPIO rather than the PRU GPIO.   
>
> > 
> > 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] <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYg3zMOM3xtcd19zv-FMBG-idkaLzcsW84M7XXpT_bzgaw%40mail.gmail.com.
>  
>
> > 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/835363cf-feed-475b-8bbc-88a62f498e4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to