On Wed, Sep 23, 2015 at 2:50 AM, Rick Mann <[email protected]> wrote: > TL;DR: pruss_uio works on -ti-r9, not on -ti-r15 or -ti-r16. > > I re-read this thread carefully: > > > https://groups.google.com/forum/#!msg/beagleboard/0bG2lt9Xy_U/2FgquA60IQAJ > > Decided the only thing I hadn't tried was being on the kernel jalodi used. > So, I installed -ti-r9, set uEnv.txt to: > > $ cat /boot/uEnv.txt > uname_r=4.1.4-ti-r9 > dtb=am335x-boneblack-emmc-overlay.dtb > cmdline=coherent_pool=1M quiet > > ##Example v4.1.x > #cape_disable=bone_capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN > #cape_enable=bone_capemgr.enable_partno=BB-ENABLE-PRU > > uuid=69f859b1-c308-41c9-8ca7-a3d0042031e8 > > Booted, then: > > root@beaglebone:/home/debian# echo BB-ENABLE-PRU > > /sys/devices/platform/bone_capemgr/slots > root@beaglebone:/home/debian# dmesg | grep pru > [ 114.058915] pruss_uio 4a300000.pruss: pins are not configured from the > driver > > Then tried running my code. It was able to load the PRU, and execute the > code, and light up the ws281x LEDs I have connected. > > Side note: it promptly locked up because I had the current limit set too low > on the power supply to support the LEDs, so voltage sagged. Increased the > current limit, and it's working much better now.
YOu should be save up to: 4.1.5-ti-r10 as in 4.1.6-ti-r11 ti merged a bunch of remoteproc changes: Here's the ti diff: https://github.com/RobertCNelson/ti-linux-kernel/compare/cc8cb4e2deb0fdb26e1bd884abab3f32451f0f35...54cf3481dbece37ef7d4d825a4dbfccb146cc931 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]. For more options, visit https://groups.google.com/d/optout.
