PRUSS and OMAPL137

Although there are no dedicated GPO/GPI pins for the PRU in OMAP-L137, it can still use any available pin in GPIO mode as PRU I/O.

The OMAP-L138 does have its own GPO/GPI pins, but future revisions of OMAP-L137 will most likely not add this.

Jeff

Jeff,

How can it use GPIO pins? There are no address lines in constant table to address GPIO module.

Also I`d like to use PRUSS to access my PLM  with the EMIFA in async mode, but it seems there is only SDRAM mode avaliable

See this wiki article:

http://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit#Constants_Table

Footnote 1 states:

Constants not in this table can be created ’on the fly’ by two consecutive LDI #16 instructions. These constants are just ones that are expected to be commonly used, enough so to be hard-coded into the PRU constants table.

Although these are not hard-coded in the constant table, they can still be accessed.

Jeff

Thank you!

I`m clear now. I can proceed any memory to memory transfer using sbbo/lbbo instructions.

For example I can transfer 2 bytes from EMIFA async 2 area to the internal RAM of the PRUSS.

And what should I do to get an interrupt from the GPIO pin to the PRUSS?

Have you checked out the documentation for the PRU interrupt controller? That should tell you everything you need to know:

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

Jeff

Thank you!

I think I should use ECAP to catch an external events from my PLM.