I wanted to add on to this that when I switch the Device Tree Blob file extension to ".dtbo" instead of ".dtb" I get the error: -bash: echo: write error: File exists instead of the file not found error I was getting previously.
On Friday, November 11, 2016 at 1:27:22 PM UTC-5, Zach B wrote: > > Hi everyone, > > So I messed around with my beaglebone a little bit last night. I worked > out the issues in my device tree source file so it is now compiled but I > can't seem to get anything to echo properly to "slots" > I compile my ".dtb" file but when I go to call the comman: > echo PRU-GPIO-BLINK > /sys/devices/platform/bone_capemgr/slots > I continually get the error: > -bash: echo: write error: No such file or directory > Is there are a different way to enable my device overlay or set the pins > to the correct mode for the PRU? I have even tried copying, compiling and > attempting to export the device tree overlay example from adafruit and > still no luck. > > The names of my files in /lib/firmware are as follows: > PRU-GPIO-BLINK.dts > PRU-GPIO-BLINK-00A0.dtb > The part-number name in the .dts file is "PRU-GPIO-BLINK". Am I still > missing something? I can post the updated ".dts" file if it would help. > > P.S. I have two questions since I am still relatively new at this: > 1) What is a blacklist and why was it necessary to export to the .conf > file to enable the remote_proc? > 2) What is dmesg and where do I check them? Are you referring to > "/var/log/syslog"? > > Zach > > > On Thursday, November 10, 2016 at 9:27:47 AM UTC-5, Greg wrote: >> >> Once you get everything solid, please take a look at dmesg after boot. >> I'm curious to see if you get successful PRU firmware start-up. >> >> Greg >> >> On Thursday, November 10, 2016 at 8:28:23 AM UTC-5, Zach B wrote: >>> >>> Hey everyone, I wanted to give an update. I got the remote_proc to turn >>> on last night. It was as simple as updating my repo like Robert had >>> mentioned. I also made the correction that Brett mentioned about the pins. >>> There is still something wrong in my device overlay file that is causing an >>> "invalid arguement" error but I am going to try and sort that out tonight. >>> I'll post again with the corrected version once I get it working and can >>> use the PRU. >>> >>> Thanks again for your help. >>> >> -- 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/88569e41-83bc-41f0-ab19-e3e1e59ecb01%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
