I have the same problem and using kernel 4.4.9-ti-rt-r26.

In my case, the rpmsg_pru is not loaded when booting or when you modprobe 
pru_rproc. I can't see the added device in /dev.



On Sunday, May 29, 2016 at 11:30:30 PM UTC+8, Greg wrote:
>
> Hi Torben-
>
> I got that image to work.  Here is a summary of the steps.  Note that I am 
> ssh-ing to a BBG as root.
>
> 1.  Flash IOT image to micro-sd.
> 2.  Insert micro-sd into BBG slot, press boot and power buttons and 
> release.
> 3.  ssh [email protected] <javascript:>
> 4.  uname -r to verify kernel -> 4.4.9-ti-r25  YES, it is the correct 
> kernel.
> 5.  apt-get update
> 6.  cd / and then find . -name cgt-pru, and the path is 
> /usr/share/ti/cgt-pru.  This is the location of the PRU library and 
> includes.
>      However, the clpru compiler binary is not there:
>      which clpru
>      /usr/bin/clpru
>      So the compiler binary is in a different location.  This is a problem 
> for the labs make files.
>      cd /usr/share/ti/cgt-pru
>      mkdir bin
>      ln -s /usr/bin/clpru clpru
>      So now the make files will find the compiler executable in the 
> correct location via the link.
> 7.  cd /home/debian
>      git clone git://
> git.ti.com/pru-software-support-package/pru-software-support-package.git
>      This will clone a copy of the latest pru support package.
> 8.  cd into lab_5 in the package:
>      cd lab_5/solution/PRU_Halt
>      make
>      This will fail, it is looking for environment variable $PRU_CGT
>      export PRU_CGT=/usr/share/ti/cgt-pru
>      Now try make again.  It should succeed.
> 9.  cd gen
>      cp PRU_Halt.out am335x-pru0-fw
>      cp am335x-pru0-fw /lib/firmware
> 10.  Now cd into the PRU_RPMsg_Echo_Interrupt1 directory in the same lab_5.
>        Edit main.c as follows:
> //#define CHAN_NAME "rpmsg-client-sample"
> #define CHAN_NAME "rpmsg-pru"
> 11.  Now almost the same as #9, this time for pru1:
>      cd gen
>      cp PRU_RPMsg_Echo_Interrupt1.out am335x-pru1-fw
>      cp am335x-pru1-fw /lib/firmware
> 12.  Reboot
> 13.  cd /dev look for rpmsg_pru31 device file.  It will be there!
>
> Hopefully I did not miss any of the steps.  Let me know if this helps.
>
> 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/e498fe32-2d1f-4d42-8f59-dcd530cd25de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to