On Thu, Nov 30, 2017 at 7:55 AM, <flueratorula...@gmail.com> wrote: > Hi Kumar, > > I am also having some troubles with rpmsg, having migrated from 4.4 to 4.9. > > Your instructions seem to work fine, at least when I run my program for the > first time. If I want to change the firmware for the PRU, I have to remove > the pru_rproc module, but when I load the module again I no longer have the > 3 directories remoteproc0, remoteproc1 and remoteproc2, but instead I have > remoteproc0, remoteproc3 and remoteproc4. If I ignore that and try to run my > program again I get a bunch of messages from syslogd@beaglebone and > everything ends with a segmentation fault. > > If I try to use the new files, remoteproc3 and remoteproc4, I get the > following errors (output of dmesg): > [ 1765.434025] remoteproc remoteproc3: 4a334000.pru0 is available > [ 1765.434147] pru-rproc 4a334000.pru0: PRU rproc node > /ocp/pruss_soc_bus@4a326000/pruss@4a300000/pru@4a334000 probed successfully > [ 1765.441036] remoteproc remoteproc4: 4a338000.pru1 is available > [ 1765.441157] pru-rproc 4a338000.pru1: PRU rproc node > /ocp/pruss_soc_bus@4a326000/pruss@4a300000/pru@4a338000 probed successfully > [ 1765.685583] remoteproc remoteproc3: powering up 4a334000.pru0 > [ 1765.686156] remoteproc remoteproc3: Booting fw image am335x-pru0-fw, size > 80748 > [ 1765.686896] ti-pruss 4a300000.pruss: event 16 (req. channel 2) already > assigned to channel 2 > [ 1765.700540] pru-rproc 4a334000.pru0: failed to configure pruss intc -17 > [ 1765.709720] remoteproc remoteproc3: Failed to process post-loading > resources: -17 > [ 1765.719518] remoteproc remoteproc3: Boot failed: -17 > [ 1765.796012] remoteproc remoteproc4: powering up 4a338000.pru1 > [ 1765.796519] remoteproc remoteproc4: Booting fw image am335x-pru1-fw, size > 80748 > [ 1765.801629] ti-pruss 4a300000.pruss: event 18 (req. channel 3) already > assigned to channel 3 > [ 1765.810696] pru-rproc 4a338000.pru1: failed to configure pruss intc -17 > [ 1765.821230] remoteproc remoteproc4: Failed to process post-loading > resources: -17 > [ 1765.831046] remoteproc remoteproc4: Boot failed: -17 > > So the events are still assigned to the previous channels? > Can you please help me understand what's happening? First of all, what are > these remoteproc1,2,etc. files (are they somehow related to the channels > used to communicate with the PRU?), why do remoteproc1/2 disappear from > /sys/class/remoteproc but the events are still assigned to them? And > finally, how can I reload the firmware in case of a change?
TI changed a few things, if you were using the v4.4.x-ti remoteproc pru option, it's best to downgrade to v4.4.x.. It'll takes us a while to adapt to those changes. 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYiCrYmG3kY3Kz4Yjec08Dx0%2BGu%2BEWFHWMQGtinFOhKaDQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
