I think it's pretty well documented here. However you could always write up an eLinux or whatever wiki page . . . I do have my own web page http://www.embeddedhobbyist.com/ with stuff on it that is important to me. But this information for using UIO on TI kernels I feel is largely useless. Because
The method for enabling either / or will likely change in the future. Right now, personally I'm still favoring *bone* kernels, and I know I'm not alone. This is really a trivial "fix". Or something that is really easy to remember how to do. @Robert, any idea on if TI plans on cleaning up the kernel module mess that now "infests" TI kernels ? using something like 50M + memory needlessly . . . On Tue, Jul 19, 2016 at 9:52 AM, Joseph Heller <[email protected]> wrote: > Finally, that worked William (&John &Robert)! I did a small check with an > LED and am able to with it on/off now via the PRU and uio. > > For your consideration, I wonder how you feel like to document this more > structurally so others can benefit from it? I was offset by some older > posts on the forum. Next thing I just though about is to make more use of > the .deb functionality instead of relying on script or instructions. For > instance uio "conflicts" with remoteproc in reality, but both reside on the > same sd-card image. Otherwise, I also understood the PRU's are not that > much used, so maybe it;s not worth the effort to invest in this. > > Anyway, thanks again for the help, I'd be glad to inform/post the end > result of my project somewhere once my time-critical part of c code as > transferred to the PRU. > > On Monday, July 18, 2016 at 10:30:35 PM UTC+2, William Hermans wrote: > >> Well, not to mention you installed a *bone* kernel anyhow. So what we're >> talking about is really moot. e.g. a topic for a different discussion. >> >> So. . . back on topic . . . >> >> *Download suitable linu image and reboot:* >> william@beaglebone:~$ sudo apt-get install linux-image-4.4.14-ti-r34 >> william@beaglebone:~$ sudo reboot >> >> *Install git and check your dtc version:* >> william@beaglebone:~$ sudo apt-get install git >> william@beaglebone:~$ dtc -v >> Version: DTC 1.4.1 >> >> *Clone the git into a suitable location:* >> william@beaglebone:~$ cd dev >> git clone -b 4.4-ti https://github.com/RobertCNelson/dtb-rebuilder >> dtb-4.4-ti --depth=1 >> william@beaglebone:~/dev$ cd dtb-4.4-ti/ >> >> *Edit the needed board file( this will be different for every situation )* >> william@beaglebone:~/dev/dtb-4.4-ti$ nano >> src/arm/am335x-boneblack-emmc-overlay.dts >> change: >> /* #include "am33xx-pruss-uio.dtsi" */ >> to: >> #include "am33xx-pruss-uio.dtsi" >> >> *Build from source, and install the board file:* >> william@beaglebone:~/dev/dtb-4.4-ti$ make >> william@beaglebone:~/dev/dtb-4.4-ti$ sudo make install >> >> *Blacklist the remoteproc drivers:* >> william@beaglebone:~/dev/dtb-rebuilder$ sudo nano >> /etc/modprobe.d/pruss-blacklist.conf >> blacklist pruss >> blacklist pruss_intc >> blacklist pru-rproc >> william@beaglebone:~/dev$ sudo reboot >> >> *Test to see if the device tree file loaded successfully:* >> william@beaglebone:~$ lsmod |grep uio >> uio_pruss 4928 0 >> uio_pdrv_genirq 3539 0 >> uio 8822 2 uio_pruss,uio_pdrv_genirq >> >> On Mon, Jul 18, 2016 at 1:12 PM, Robert Nelson <[email protected]> >> wrote: >> >>> >>> >>> On Mon, Jul 18, 2016 at 3:08 PM, Joseph Heller <[email protected]> >>> wrote: >>> >>>> small progress here; >>>> 4.4.x-ti r34 did not result in any good (only remoteproc as far as I >>>> could tell), no uio. >>>> >>>> Therefore went for the bone version, non -rt: >>>> >>>> cd /opt/scripts/tools/ >>>> sudo git pull >>>> sudo ./update_kernel.sh --bone-kernel --lts-4_4 >>>> >>>> which gave me >>>> kernel 4.4.15-bone11 >>>> >>>> and a new dmesg after loading my dtbo: >>>> [Mon Jul 18 19:44:48 2016] pruss_uio 4a300000.pruss: pins are not >>>> configured from the driver >>>> [Mon Jul 18 19:44:49 2016] bone-pinmux-helper >>>> ocp:pinctrl_generated_pinmux: could not find pctdev for node >>>> /ocp/interrupt-controller@48200000, deferring probe >>>> >>> >>> ^ looks like you aren't using the dtc compiler for v4.1.x+ targets.. >>> >>> 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]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYgfQYcKT89EihmpdnORK%3D7t9M3zG7gG1SozLtQpaTtQJA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/beagleboard/CAOCHtYgfQYcKT89EihmpdnORK%3D7t9M3zG7gG1SozLtQpaTtQJA%40mail.gmail.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/1a79bfd0-ddcf-4f32-a6af-95635e067fef%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/1a79bfd0-ddcf-4f32-a6af-95635e067fef%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/CALHSORqchZxuP3ovVeoJWoVHS%2BGThZwkxTxF62mYFkvmDKSJkg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
