No decision?
In order to give you a further lift, you can make the example pruss_toggle running by simply executing
sudo modprobe libpruio
This manually loads the lkm from the RCN package (enabling the pinmuxing capability).
Regards
PS
From my point of view it’s worth the effort to install auto-loading. And you’ve to care about the double binaries.
Well my friend I was trying but it is not working, I installed the lkm my friend @DTJF
debian@beaglebone:~/libpruio/src$ ls
c_examples c_include config doc examples lkm pruio python
debian@beaglebone:~/libpruio/src$ cd c_examples
debian@beaglebone:~/libpruio/src/c_examples$ ls
1 button.c led pruss_toggle pwm_cap.c rb_file.c
1.c CMakeLists.txt led.c pruss_toggle.c pwmled sos.c
button io_input.c performance.c pru_toggle pwmled.c stepper.c
button2.c irig.c pruss_add.c pwm_cap qep.c
debian@beaglebone:~/libpruio/src/c_examples$ ./pruss_toggle
P8_11 configuration failed (pinmux missing)
Rony Vargas
I asked a question twice, and I didn’t hear your answer.
Please speak a little louder, my friend.
Well packeges my friend @DTJF
Rony Vargas
Well, you wasted 5 days.
[sidenote]
Please consider, that I’m not a native speaker. From my point of view, it’s OK when we talk in my mother tongue. Or I can offer to continue in your mother tongue, but in that case you should try to speak in clear words and avoid slang speaking. Better say
I don’t want to build from git-source. Instead, I’d like to use the pre-build packages from the PPA
Because your statement
sounds like you’re talking about good packages.
Note: each time I don’t get what you’ve in mind, both of us are loosing time.
[/sidenote]
Back to the topic: we’ve to
So for the first point execute (answer ‘yes’ to the question from line 2)
cd libpruio/build
sudo xargs rm < install_manifest.txt && rm -r *
ldconfig -p | grep pruio
and post the output (copy/paste text only, no pictures).
Regards
ok my friend, now it is working the program of the pru_toggle my friend @DTJF
root@beaglebone:/home/debian/libpruio/src/c_examples# ./pruss_toggle
instructions loaded, starting PRU-0
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
→ Frequency: 0 MHz, Duty: 0 %
root@beaglebone:/home/debian/libpruio/src/c_examples#
Best Regards,Rony Vargas
Hello my friend @DTJF , my friend I have a question with this configuration about this link Beaglebone PRU Coding in C (catch22eu.github.io), this is similar with the configuration of your library but with differents headers files?
Hey DTJF,
I was going through your article (great work) and noticed that libpruio is only for Wheezy and Jessie. I am using buster on a BBB AM3358 Debian 10.3 2020-04-06 4GB SD IoT. And I would like to keep using this due to some restrictions. So just wanted to know if I should use Jessie or Wheezy? Would any of them work?
Is there a newer method to use PRU with python?
I am new to embedded so please go easy on me. 
Thanks
Found your post right now, sorry for the late answer.
Beside the Wheezy and Jessie packages, I created an image (IoT) with pre-installed libpruio for burning onto an SD card (4MB). That’s the most easy way to test, if the library meets your needs. Find details at
Regards
