Hi,
Have anyone used AM1705 Programmable Real-Time Unit Subsystem as I2C & UART. Can anyone provide procedure or steps to how to create PRUSS I2C & UART drivers for linux platform.
Please reply to the above query
Thank you
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.
Hi,
Have anyone used AM1705 Programmable Real-Time Unit Subsystem as I2C & UART. Can anyone provide procedure or steps to how to create PRUSS I2C & UART drivers for linux platform.
Please reply to the above query
Thank you
For the PRU UART, you can find more information here, http://focus.ti.com/dsp/docs/thirdparty/catalog/devtoolsproductfolder.tsp?actionPerformed=productFolder&productId=7177.
For the PRU I2C, I'm don't believe TI has developed a software implementation for it.
--Christina
The source code for
Mistral's UART driver can be found at:
http://mistralsolutions.com/pes-support/support-downloads/l13x-daughter-card-documentation-software.html
After applying the patch, the Mistral UART code is found under
drivers/serial/omapl_pru. This code, along with those in the PRU Firmware
Source Files (hal directory), could serve as a model for an I2C driver.
An I2C implementation could reuse the files in pru/hal/common (found within the
PRU Firmware Source Files). Additionally, the PRU assembly code for UART
is located in pru/firmware/uart.
The PRU pins that can be used depend on what other chip peripherals the
customer requires. I recommend using the pinmux utility (http://focus.ti.com/dsp/docs/litabsmultiplefilelist.tsp?sectionId=3&tabId=409&literatureNumber=sprab06a&docCategoryId=1&familyId=1621).
In the utility, check the peripheral boxes required by the customer and see
which PRU pins do not conflict with these peripherals.
Thanks to Melissa Watkins for the above inputs!
Best Regards
Feroz