Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

On Fri, Jul 8, 2016 at 3:36 PM, Mark A. Yoder wrote: > Robert: > I uncovered an minor bug when upgrading to 4.4.12-ti-r32 > > apt-get install linux-image-4.4.12-ti-r32 > Reading package lists... Done > Building dependency tree > Reading state information... Done >

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

Robert: I uncovered an minor bug when upgrading to 4.4.12-ti-r32 apt-get install linux-image-4.4.12-ti-r32 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: linux-firmware-image-4.4.12-ti-r32 The following NEW packages will be

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

On Thu, Jun 30, 2016 at 1:00 PM, wrote: > I was actually using 4.4.9-ti-rt-r26 and v5.0 of the pru software package > when it did not load the rpmsg_pru. > > On Friday, July 1, 2016 at 1:46:40 AM UTC+8, john3909 wrote: >> >> Wonderful. If you change to the V4.4 kernel, you

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

Then I’m wondering if Robert had pulled in these changes from the https://git.ti.com/rpmsg V4.4 repo. If not, then the V4.0.2 examples should work fine. Regards, John > On Jun 30, 2016, at 11:00 AM, engkan2...@gmail.com wrote: > > I was actually using

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

I was actually using 4.4.9-ti-rt-r26 and v5.0 of the pru software package when it did not load the rpmsg_pru. On Friday, July 1, 2016 at 1:46:40 AM UTC+8, john3909 wrote: > > Wonderful. If you change to the V4.4 kernel, you must update to PRU V5.0 > examples because there is a change from

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

Wonderful. If you change to the V4.4 kernel, you must update to PRU V5.0 examples because there is a change from mailbox to interrupt event. Regards, John > On Jun 30, 2016, at 8:23 AM, engkan2...@gmail.com wrote: > > Hi John! > > It is working now. I tried 4.1 and 4.4.9-ti-rt-r25. The

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

What does lsmod show? Regards, John > On Jun 28, 2016, at 6:55 AM, engkan2...@gmail.com wrote: > > I've changed my kernel to the same version as the poster (I'm using ubuntu). > I still don't see the device in /dev. > > [ 17.581262] pru-rproc 4a338000.pru1: sysevt-to-ch[18] -> 3 > [

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

I've changed my kernel to the same version as the poster (I'm using ubuntu). I still don't see the device in /dev. [ 17.581262] pru-rproc 4a338000.pru1: sysevt-to-ch[18] -> 3 [ 17.581274] pru-rproc 4a338000.pru1: sysevt-to-ch[19] -> 1 [ 17.581286] pru-rproc 4a338000.pru1: skip intr mapping

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

I tried what you did but I am using 4.4.9-ti-rt-r26. I am still not seeing the /dev/rpmsg_pru*. Was this changed in recent kernel versions? I have been trying to solve this since yesterday. On Monday, March 28, 2016 at 9:10:11 PM UTC+8, lucas wrote: > > Wow it worked :) Thank you, John! > >

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

Hi Lucas, Good to hear this is working for you. Now for the real work ;-) Regards, John > On Mar 28, 2016, at 6:10 AM, lucas wrote: > > Wow it worked :) Thank you, John! > > Short summary how to get it working: > > 1.) Compile PRU_RPMsg_LED0 project in CCS > 2.)

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

Wow it worked :) Thank you, John! Short summary how to get it working: 1.) Compile PRU_RPMsg_LED0 project in CCS 2.) Transfer PRU_RPMsg_LED0.out onto beaglebone into the /lib/firmware directory 3.) Set symbolic link: sudo ln -s PRU_RPMsg_LED0.out am335x-pru0-fw 4.) restart 5.) modprobe

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

Don’t include the .ko extension when using modprobe. Regards, John > On Mar 23, 2016, at 9:32 AM, lucas wrote: > > Sorry forgot to copy the error message for the modprobe command: > > root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# modprobe >

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

Sorry forgot to copy the error message for the modprobe command: root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# modprobe virtio_rpmsg_bus.ko modprobe: FATAL: Module virtio_rpmsg_bus.ko not found. On Wednesday, March 23, 2016 at 5:27:12 PM UTC+1, lucas wrote: > > Hi John,

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

Hi John, thank you very much for your answer. I am using the 4.1.15-ti-rt-r43 kernel. It's the kernel that came with the debian image from the beaglebone website. Only the pruss_remoteproc module seems to be loaded on boot: # lsmod Module Size Used by 8021q

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

Hi Lucas, This seems to work just fine for me. What kernel version are you using? I’m using V4.1.13-ti-r33. As you can see, all remoteproc/rpmsg kernel modules are loaded automatically at boot time. [ 16.251480] pruss-rproc 4a30.pruss: 8 PRU interrupts parsed

[beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

I am trying to use rpmsg from user space. I am following the PRU training of TI (http://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs#Part_1:_Linux_Command_Line_LED_Toggling) I use the latest beaglebone black image (Debian 8.3 2016-01-24 from