Hi Mark! Thanks to your posting on another topic, I was able to solve my problem. It turned out the original image flashed on the 4G onboard chip was still supplying the uEnv.txt so the new image on the SD card was not picking up any changes I would make to the uEnv.txt file on the SD card. Once I wiped out the original image, using the 'dd' command, everything starting working. Your book and supplied examples are *Excellent* and have helped me make progress.
Thanks again. Bill Bitner On Fri, Oct 19, 2018 at 10:19 AM Mark A. Yoder <mark.a.yo...@gmail.com> wrote: > Bill: > Which kernel are you running? (uname -a) I discovered yesterday that > the PRUs didn't work for my students running 4.9, but those running the > newer 4.14 had no trouble. > > --Mark > > p.s. Check out the PRU Cookbook (https://github.com/MarkAYoder/PRUCookbook) > for more examples. > > On Friday, October 19, 2018 at 7:33:58 AM UTC-4, wjbi...@gmail.com wrote: >> >> Hi! >> >> I just picked up a beaglebone black for a new project. I'd like to use >> the PRU's and as such tried to get >> "Hello World" from this link http://theduchy.ualr.edu/?p=996 >> working. The programs all compile but I can't get them >> to run. The major hint I have is looking at /sys/class/remoteproc/ >> shows me only remoteproc0. >> PRU 0 & 1 'don't exist'. I've not modified anything in the boot >> sequence yet. I've looked at >> >> https://groups.google.com/forum/#!category-topic/beagleboard/pru/4P9NdglojBo >> >> which lead me to trying >> echo "4a334000.pru0" > /sys/bus/platform/drivers/pru-rproc/unbind >> >> However, this simply gave me permission denied, despite the fact I was >> root. >> >> lsmod shows >> >> pru_rproc 28672 0 >> pruss 16384 1 pru_rproc >> pruss_intc 16384 1 pru_rproc >> >> but not the virtio_rpmsg_bus or other things that seem to be important. >> >> Not sure where to go.. Any help would be appreciated. >> >> Thanks. >> >> Bill Bitner >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/3lVWzlusOIU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/a6fefe59-1e0a-4ac0-b7d0-7170b8019fcb%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/a6fefe59-1e0a-4ac0-b7d0-7170b8019fcb%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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOYP4dhMiZ_AFZ7wb%3D_oG_gXgvOdgmk8H3GwPOFgu2TX834_6Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
