• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 101 subscribers
  • Views 157 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: How to solve the problem of interruption in reading and writing sensor registers when adding a new driver？

Wei Wang
Prodigy 30 points
Part Number: TDA4VM

Tool/software:

Hi, TI experts,

During the process of adding a new driver in TDA4 VM, we found that there was an interrupt when reading or writing to the sensor register address 0xffff, which means that the subsequent sensor registers will no longer be written. 

Is this the reason for the conflict between the sensor register address and the default 0xffff end address in TDA4? And how to solve this problem?

  • 0
    TI__Mastermind 20935 points

    Hi,

    Which driver are you trying to add?

    Regards,

    Josiitaa

  • 0 in reply to Josiitaa RL
    Prodigy 30 points

    Hi, Josiitaa,

     We are trying to add driver of Sony IMX623

  • 0
    TI__Guru**** 427045 points

    Hi,

    Which interrupt are you seeing when writing to address 0xFFFF? Is sensor configured via i2c and are you writing to address 0xFFFF? 

    As such there should not be conflict because i2c is different interface and this address just goes to i2c driver. lets first identify which interrupt is getting generated.. and is it exactly generated when you enable write to this register? 

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Prodigy 30 points

    Hi,Brijesh,

     the sensor is configured via I2C, the log is shown in figure.

    It can be seen that addresses after 0xffff cannot be written. 

  • 0 in reply to Wei Wang
    TI__Guru**** 427045 points

    Hi 

    To check it further, is it possible to skip writing to 0xFFFF register and see if it progresses? I am really doubtful that register address 0xFFFF is causing error interrupt. 

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Prodigy 30 points

    Hi, Brijesh,

    I placed the 0xffff register in the first register of the sensor, the log shows that subsequent registers cannot be written. The registers that could be written before are now unable to be written because they are located after 0xffff.  I think the register address 0xffff is the cause of the interrupt

    Then,  I skipped writing to register 0xffff, and the log showed that reading and writing could continue. 

    But it will still interrupt, the interrupt register is 0x002f, and the interrupt log is shown in the figure.

    What do you think is the reason for the interrupt in register writing？

  • 0 in reply to Wei Wang
    TI__Guru**** 427045 points

    Hi Wang,

    Strange, is it possible to connect CCS + JTAG to see where the core is? Is there some abort that you are seeing? As such, there shouldn't be, because these values just to the I2C driver for the transfer.. 

    Regards,

    Brijesh