• Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 216 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.

PRU availability?

Alistair Lowe
Prodigy 150 points
Other Parts Discussed in Thread: OMAPL138

Hello TI,

I notice in EZSDK 5.03 that PRU examples are not yet ready. When will a general tool to assemble user code be made available?

Many thanks

  • Intellectual 570 points

    Ditto, same question in my head.

     

    The current trunk has this in the config, though, which makes it sound like soon if not now:

     

    config UIO_PRUSS

            tristate "Texas Instruments PRUSS driver"

            depends on ARCH_DAVINCI_DA850 || SOC_OMAPAM33XX

            help

              PRUSS driver for OMAPL138/DA850/AM18XX/AM33XX devices

              PRUSS driver requires user space components, examples and user space

              driver is available from below SVN repo - you may use anonymous login

     

              https://gforge.ti.com/gf/project/pru_sw/

     

              More info on API is available at below wiki

     

              http://processors.wiki.ti.com/index.php/PRU_Linux_Application_Loader

     

              To compile this driver as a module, choose M here: the module

              will be called uio_pruss.

  • in reply to Christopher Piggott
    Intellectual 570 points

    http://processors.wiki.ti.com/index.php/PRU_Linux_Application_Loader

    Definitely look at that link, it explains how the whole thing is supposed to work.  Still not clear on if this is same for AM33XX.  It's funny that it says you need RT patches though.  Maybe that's to give it adequate performance when using the UIO style userspace driver.

    For my application I don't mind writing a simple device driver, if I can find a template that would show me how to map it in.  I woudln't want to hack the kernel up TOO much.  Lookinat at include/linux/platform_data/uio_pruss.h in the trunk of the arago git, the only thing really defined is pintc_base which I think has to do mostly with interrupts, not finding the actual device in the memory map.