Hi Greg, Thank you for your reply! Friday, I found what I was doing wrong: I was using am335X-boneblack.dts instead of am335X-boneblack-emmc-overlay.dts. This wrong dts was pinmuxing my target pin to HDMI, and I was not able to exploit config-pin. Therefore, I edited am335X-boneblack-emmc-overlay.dts by enabling remoteproc as in your guide, then used config-pin to configure my target pin to pruout. Finally, everything was blinking :-)
To summarize: 1. edit am335x-boneblack-emmc-overlay.dts to enable remoteproc; 2. edit /boot/uEnv.txt to use as dtb "am335x-boneblack-emmc-overlay"; 3. config pin as pruout via "config-pin". Now, in order to learn how to use the whole system, I am moving forward the examples :-) Regards, Lorenzo Il giorno sabato 14 gennaio 2017 02:17:13 UTC+1, Greg ha scritto: > > Hi Lorenzo- > > An important file to view is the kernel log. At the command line: > > dmesg > > You should be able to find messages in this log which indicate success or > failure of PRU firmware loading. > > Did you successfully modify the Device tree in order to enable the > RemoteProc kernel drivers? This is a relatively new requirement. > A more recent project includes the steps to enable RemoteProc: > > https://github.com/Greg-R/pru-pid-motor > > Regards, > Greg > -- 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/a678b3bb-5a35-40d3-aee0-7bd3ac00b5ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
