I tried going past chapter 9 into 10 but now I am getting an error with prumodin. Ideally I want to know how run a very simple pru set-up that I can debug...but going through what ti has to offer, it all done through code composer. Doesn't seem like you used it. Either way I was trying to give yours a shot a and here is where I ended up. root@beaglebone:/home/debian/pru-software-support-package# ls /usr/bin/ | grep pru abspru acpiapru arpru asmpru cgpru clistpru clpru dempru dispru embedpru hexpru ilkpru libinfopru lnkpru nmpru ofdpru optpru prumodin prumodout prumsg strippru xrefpru root@beaglebone:/home/debian/pru-software-support-package# ls /usr/bin/ | grep prumod prumodin prumodout root@beaglebone:/home/debian/pru-software-support-package# ls examples labs Makefile PRU-Package-v5.0-Manifest.html include lib pru_cape ReadMe.txt root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# ls AM335x_PRU.cmd mapfile1 PRU_PID_0.c resource_table_empty.h Makefile PRU_IO_1.c PRU_PID_0.obj result mapfile0 PRU_IO_1.obj resource_table_1.h user_space root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# make clean make: Nothing to be done for 'clean'. root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# make clpru -I/usr/share/ti/cgt-pru/includeSupportPackage -I/usr/share/ti/cgt-pru/include -I/usr/share/ti/cgt-pru/lib --hardware_mac=on -O2 -v3 --display_error_number --endian=little PRU_PID_0.c -z -i/usr/share/ti/cgt-pru/lib -i/usr/share/ti/cgt-pru/include -i/usr/share/ti/cgt-pru/includeSupportPackage -i/usr/share/ti/cgt-pru/includeSupportPackage/am335x --reread_libs --stack_size=0x100 --heap_size=0x100 --library=/usr/share/ti/cgt-pru/lib/rpmsg_lib.lib -m=mapfile0 ./AM335x_PRU.cmd -o ./result/am335x-pru0-fw --library=libc.a <Linking> clpru -I/usr/share/ti/cgt-pru/includeSupportPackage -I/usr/share/ti/cgt-pru/include -I/usr/share/ti/cgt-pru/lib --hardware_mac=on -O2 -v3 --display_error_number --endian=little PRU_IO_1.c -z -i/usr/share/ti/cgt-pru/lib -i/usr/share/ti/cgt-pru/include -i/usr/share/ti/cgt-pru/includeSupportPackage -i/usr/share/ti/cgt-pru/includeSupportPackage/am335x --reread_libs --stack_size=0x100 --heap_size=0x100 --library=/usr/share/ti/cgt-pru/lib/rpmsg_lib.lib -m=mapfile1 ./AM335x_PRU.cmd -o ./result/am335x-pru1-fw --library=libc.a <Linking> gcc ./user_space/prumsg.c -o /usr/bin/prumsg cd result cp ./result/am335x-pru0-fw /lib/firmware cp ./result/am335x-pru1-fw /lib/firmware root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# ls AM335x_PRU.cmd mapfile1 PRU_PID_0.c resource_table_empty.h Makefile PRU_IO_1.c PRU_PID_0.obj result mapfile0 PRU_IO_1.obj resource_table_1.h user_space root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# prumodin /usr/bin/prumodin: line 9: echo: write error: No such device /usr/bin/prumodin: line 10: echo: write error: No such device
Any ideas as to what going on? On Sunday, January 29, 2017 at 1:26:34 PM UTC-8, Ashwini Bhat wrote: > > Ok I did as your procedure says and followed chapter 9. All the outputs > you were looking for in your procedure showed up. Now is there a simple > program I can run to see if the PRU is working and if it is able to toggle > a GPIO pin? I can just see if a pin is being toggled by putting a scope on > it. > > On Sunday, January 29, 2017 at 4:44:48 AM UTC-8, Greg wrote: >> >> I wouldn't update the kernel at this time. Yes, try the procedure and >> see what happens. I think you will be successful. If not, we can work >> through it. >> >> That kernel is the TI version and it should be good to go for sure. If >> not, there are problems we are not going to solve without help! >> It's still not clear to me the differences between the TI and the Bone >> kernels. The TI kernels definitely support the latest Remoteproc. >> >> If you don't need GUI, stick with the IOT image. I've had very good luck >> with it. >> >> >> -- 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/3cc59d8f-ca6f-4512-acd1-6fe5c96eaf5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
