I am running into the same problem with 4.4.9-ti-r25 (debian), using the Makefile.
On Thursday, May 26, 2016 at 11:09:20 PM UTC+2, JD Morise wrote: > > Hi, > > I would like to get communication up and running between ARM and PRU, by > following the TI Example 5 "RPMsg communication between ARM and PRU". > > The system is a BBB with debian, kernel 4.1.15-ti-rt-r43. All 3 modules > are loaded, here is the snippet of the lsmod: > > pruss_remoteproc 15296 2 > rpmsg_pru 4683 0 > virtio_rpmsg_bus 13437 1 rpmsg_pru > > dmesg ourput is posted below, I however don't see any problems or errors. > However the device file /dev/rpmsg_pru* is not created at all, although > the rpmsg_host seems to be online. What am I missing? Where to look for > error messages or problems? > > Could it be a problem with the device tree? I don't have any device tree > overlays loaded, apart from the cape_universaln > > > Best Regards, JD > > [ 137.089974] pruss-rproc 4a300000.pruss: 8 PRU interrupts parsed > [ 137.090107] pruss-rproc 4a300000.pruss: memory dram0: pa 0x4a300000 > size 0x2000 va e0b68000 > [ 137.090153] pruss-rproc 4a300000.pruss: memory dram1: pa 0x4a302000 > size 0x2000 va e0b6c000 > [ 137.090193] pruss-rproc 4a300000.pruss: memory shrdram2: pa 0x4a310000 > size 0x3000 va e0b70000 > [ 137.090231] pruss-rproc 4a300000.pruss: memory intc: pa 0x4a320000 > size 0x2000 va e0b74000 > [ 137.090270] pruss-rproc 4a300000.pruss: memory cfg: pa 0x4a326000 > size 0x2000 va e0b78000 > [ 137.106091] pruss-rproc 4a300000.pruss: creating platform devices for > PRU cores > [ 137.117092] pru-rproc 4a334000.pru0: memory iram: pa 0x4a334000 > size 0x2000 va e0b7c000 > [ 137.117188] pru-rproc 4a334000.pru0: memory control: pa 0x4a322000 > size 0x400 va e0b80000 > [ 137.117231] pru-rproc 4a334000.pru0: memory debug: pa 0x4a322400 > size 0x100 va e0b82400 > [ 137.128119] remoteproc1: 4a334000.pru0 is available > [ 137.128152] remoteproc1: Note: remoteproc is still under development > and considered experimental. > [ 137.128169] remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and > backward compatibility isn't yet guaranteed. > [ 137.137153] remoteproc1: powering up 4a334000.pru0 > [ 137.137211] remoteproc1: Booting fw image am335x-pru0-fw, size 79096 > [ 137.137332] pru-rproc 4a334000.pru0: version 0 event_chnl_map_size 1 > event_chnl_map 00000394 > [ 137.137356] pru-rproc 4a334000.pru0: sysevt-to-ch[59] -> 1 > [ 137.137375] pru-rproc 4a334000.pru0: skip intr mapping for chnl 0 > [ 137.137395] pru-rproc 4a334000.pru0: chnl-to-host[1] -> 1 > [ 137.137413] pru-rproc 4a334000.pru0: skip intr mapping for chnl 2 > [ 137.137431] pru-rproc 4a334000.pru0: skip intr mapping for chnl 3 > [ 137.137449] pru-rproc 4a334000.pru0: skip intr mapping for chnl 4 > [ 137.137467] pru-rproc 4a334000.pru0: skip intr mapping for chnl 5 > [ 137.137485] pru-rproc 4a334000.pru0: skip intr mapping for chnl 6 > [ 137.137503] pru-rproc 4a334000.pru0: skip intr mapping for chnl 7 > [ 137.137520] pru-rproc 4a334000.pru0: skip intr mapping for chnl 8 > [ 137.137538] pru-rproc 4a334000.pru0: skip intr mapping for chnl 9 > [ 137.137563] pruss-rproc 4a300000.pruss: SYSEV59 -> CH1 (CMR14 > 0x01000000) > [ 137.137584] pruss-rproc 4a300000.pruss: CH1 -> HOST1 (HMR0 0x00000100) > [ 137.137607] pruss-rproc 4a300000.pruss: configured system_events = > 0x0800000000000000 intr_channels = 0x00000002 host_intr = 0x00000002 > [ 137.137626] remoteproc1: starting PRU0: entry-point = 0x0 > [ 137.137642] remoteproc1: remote processor 4a334000.pru0 is now up > [ 137.137798] remoteproc1: kicking vqid 0 on PRU0 > [ 137.137965] virtio_rpmsg_bus virtio0: rpmsg host is online > [ 137.138120] remoteproc1: registered virtio0 (type 7) > [ 137.138351] pru-rproc 4a334000.pru0: PRU rproc node > /ocp/pruss@4a300000/pru@4a334000 probed successfully > [ 137.138733] pru-rproc 4a338000.pru1: memory iram: pa 0x4a338000 > size 0x2000 va e0b9c000 > [ 137.138813] pru-rproc 4a338000.pru1: memory control: pa 0x4a324000 > size 0x400 va e0b9a000 > [ 137.138855] pru-rproc 4a338000.pru1: memory debug: pa 0x4a324400 > size 0x100 va e0ba0400 > [ 137.160141] remoteproc2: 4a338000.pru1 is available > [ 137.160177] remoteproc2: Note: remoteproc is still under development > and considered experimental. > [ 137.160194] remoteproc2: THE BINARY FORMAT IS NOT YET FINALIZED, and > backward compatibility isn't yet guaranteed. > [ 137.163512] pru-rproc 4a338000.pru1: booting the PRU core manually > [ 137.163552] remoteproc2: powering up 4a338000.pru1 > [ 137.163871] remoteproc2: Booting fw image am335x-pru1-fw, size 33580 > [ 137.163953] remoteproc2: starting PRU1: entry-point = 0x0 > [ 137.163972] remoteproc2: remote processor 4a338000.pru1 is now up > [ 137.164033] pru-rproc 4a338000.pru1: PRU rproc node > /ocp/pruss@4a300000/pru@4a338000 probed successfully > > -- 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/70f5e1b5-a3ca-4501-8772-660e10604507%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
