• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 285 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.

TDA4VM: TDA4VM I2C slave can not trigger the interrupt function

xiujuan tang
Prodigy 20 points
Part Number: TDA4VM


Hello, dear support

I'm working with I2C slave in TDA4VM product, from xds I can see interrupt status bit was set, and looks a byte was in the data register, but looks I can never trigger my interrupt function.

/* Register interrupts */
(void)I2C_osalRegisterInterrupt(&interruptRegParams,&(object->hwi));

I think in the code this line register the interrupt function, is there anything missing?

I2C slave in MCU2_0 which running the tirtos.

Br

Tangxiujuan

  • 0
    Prodigy 20 points

    Here is the register details. In the I2C_DATA  0xAA was sent from master side.

    From I2C_IRQSTATUS_RAW AAS bit was set, so means the slave address master access met the address set in I2C_OA register.

    But it looks the interrupt handling can not be triggered.

  • 0 in reply to xiujuan tang
    TI__Guru**** 484405 points

    Hi,

    Sorry, did not get the question, are you using i2c in slave mode? Please note that PDK support i2c in master mode only. 

    In master, we are able to configure on-board devices using i2c, did not see interrupt issue. 

    Few questions,

    1, which SDK are you using?

    2, which i2c instance are you using?

    3, does the polling mode work fine?

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Prodigy 20 points

    I know the sdk does not support slave mode, but from the the driver code, I try to update the code and make it support slave.

    1. SDK is: ti-processor-sdk-rtos-j721e-evm-07_02_00_06

    2. Instance is: I2C1

    3. I must make I2C works in slave mode, so I have to use interrupt.

    I think it should works, problem now is looks the interrupt is not triggered. 

  • 0 in reply to xiujuan tang
    TI__Guru**** 484405 points

    ok, is the polling mode work fine? can you check the interrupt status in status register and confirm that interrupt is really generated?

    Regards,

    Brijesh