• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 101 subscribers
  • Views 731 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP L137 and PRUSS

Marco Del Fiasco
Prodigy 110 points
Other Parts Discussed in Thread: OMAP-L137, OMAP-L138

Hello, I see that a new document regarding the PRU inside OMAP L137 was added these days on the device application notes section. Since PRUSS was used for ARM booting only, I taught it was not fully supported for the L137. So I need a confirmation about this: is the PRU fully functional on OMAP L137 devices?

Thank you.

  • 0
    TI__Mastermind 29141 points

    Yes, it is.  The L137 data sheet and user guides will be updated in upcoming weeks to show the PRU.

  • 0 in reply to Gus Martinez
    Intellectual 590 points

    Hi Gus,

     

     I'm currently working with a OMAP-L137 trying to use the PRUSS, but there is no documentation on the PRUSS in the OMAP-137 Product Folder

    as to how use it from linux, for the OMAP-L138 there are some examples but these dont seem to work on the OMAP-L137, also my OMAP-L137

    silicon revision is the first I'm not sure if the PRUSS functionality was available for that revision?

     Could you give me any pointers as to how adapt the examples for the 137?

     

    Thanks

     

  • 0 in reply to Haroldo
    TI__Prodigy 385 points

     The Programmable Real-Time Unit Subsystem (PRUSS) consists of:

    • 

    • 

    • 

    The two PRUs can operate completely independently or in coordination with each other. The PRUs can also work in coordination with the device level host CPU. This is determined by the nature of the program which is loaded into the PRUs instruction memory. Several different signaling mechanisms are available between the two PRUs and the device level host CPU.

    The PRUs are optimized for performing embedded tasks that require manipulation of packed memory-mapped data structures, handling of system events that have tight realtime constraints and interfacing with systems external to the device.

    The PRUSS documentation (peripheral guide) is on the external wiki: (http://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit)

    A Switched Central Resource (SCR) for connecting the various internal and external masters to the resources inside the PRUSS.     An interrupt controller (INTC) for handling system interrupt events. The INTC also supports posting events back to the device level host CPU.Two programmable real-time units (PRU0 and PRU1) and their associated memories.

     

     

  • 0 in reply to Sam DeMora
    Intellectual 590 points

    Hi Sam,

     

     Thanks for the quick response, I appreciate the info you provided about the PRUSS.

    I'm also interested in a guide or info of how to compile the PRUSS linux loader examples

    for the omap-137 da830 platform.

    which as you can see in this page http://processors.wiki.ti.com/index.php/PRU_Linux_Application_Loader

    are specified for the omap-l138 and the da850 plataform but not for the l137!

    I have followed this examples changing the compiler target architecture but there is also a different defconfig

    file for each architecture and for the da830 there aren't  some of the choices that are portrayed in the compiling

    instructions.

    I guess this post belongs more to the embedded forum.