Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 11 Jun 2014 01:38 PM by  Adam Ford
GPIO_140 and 141 access
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Fabrice MESPLOU
New Member
New Member
Posts:5


--
11 Jun 2014 08:02 AM

    Hi

     

    I would use the GPIOs 140 (PCM_DR) and 141 (PCM_DX)  with Linux BSP.

    But refering to the documentation, we must put this I/O in tri-state as they are plugged to TPS65950 chip. It seems that I must use i2C bus, but how can I configure this 2 pins from Linux point of view ?

     

    Best regards.

    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    11 Jun 2014 01:38 PM
    If you don't have swcu050g.pdf from TI, I would suggest you download it from TI. It has a complete description of the I2C registers on the TPS65950. http://www.ti.com/product...0/technicaldocuments


    To read and write the I2C registers in Linux, the tools you'll need are i2cset and i2cget. They should be located in the /usr/sbin directory
    If for some reason you don't have them or you expect to support block transfers, you can look here http://support.logicpd.co...aft/104/Default.aspx for instructions on building a newer version.


    In order to set the VIF_TRI_EN, you'll need to set bit 2 of of the VOICE_IF register (0x0f) in address group 0x49 (See Table 14-28 for details)

    /usr/sbin/i2cset -f -y 1 0x49 0x0f 0x04

    to test if this was successful, you can read the i2c bus with:

    i2cget -f -y 1 0x49 0x0f

    Let us know if you have any other issues,

    adam
    You are not authorized to post a reply.