• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 308 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.

dsplink pinmux adjustment on startup with linux on omapl138

Alan Guinan
Prodigy 10 points
Other Parts Discussed in Thread: TPS65070

Hello,

I'm working on a project which using the omapl138-SOM1, running Linux, and using dsplink. When DSPLink starts up, we have observed I2C communications to the TPS65070 power management chip, and have observed some changes to the pinmux settings on the chip.

Some of these interfere with settings which we require in the Linux environment (GPIO's, I2C lines, etc), and I would like to know where/why these changes are taking place. I know that they happen prior to our DSP code's main function, but am not sure if it is done by DSP BIOS or the linux side DSPLink module. Any help would be very appreciated.

We are using DSPLink v1.65.01.06, DSP BIOS v5.41.11.38, linuxutils v v3.22.00.02(fr CMEM), and linux kernerl v2.6.37(distributed with Davinci-PSP-SDK 3.21.00.14).

  • 0
    TI__Expert 6860 points

    DspLink does power up the DSP and load the DSP application.  Looking at DSPLink specifically, I don't see anything specific that is touching the I2C peripheral.  Could it be in the Linux kernel?  The kernel configuration on this device has drivers that use the I2C, I'm at least aware that the ALSA driver is enable by default (there may be others).