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.

DS90UB954-Q1: Different answers of 16 bit address readouts from sensor in ALP in Python

Part Number: DS90UB954-Q1
Other Parts Discussed in Thread: DS90UB953-Q1EVM, , ALP,

Hello,

we use the DS90UB953-Q1EVM and DS90UB954-Q1EVM with the included sensor. We tried to read the Register to validate the writes after initialisiation used from "ovt_1280_1080_30fps_REMOTE_RevE2_ID7a.py".

To write and read the register we used the command from the thread "DS90UB954-Q1: Can I do 32 bit address writes in ALP in Python?" . But with different readouts we got different results and we don´t know why:

Texas Instruments - Analog LaunchPAD
© 2007-2019 Texas Instruments Inc. All Rights Reserved
The variable "board" contains the selected daughter board object. The variable "alpBoards" contains a list of ALP Board objects present on this machine.

>board.WriteI2C(0xC4, 0x31, [0x29*** Running ovt_1280_1080_30fps_REMOTE_RevE2_ID7a_only_init.py ***
OVT10640 Reset
*** Script execution time 0 min 5.210 sec ***
>
board.WriteI2C(0xC4, 0x31, [0x29, 0x80])
board.ReadI2C(0xC4, 0x31, [0x29, 0x01])
[17]
board.ReadI2C(0xC4, 0x31, [0x29, 0x01])
[1]
board.ReadI2C(0xC4, 0x31, [0x29, 0x01])
[0]
board.ReadI2C(0xC4, 0x31, [0x29, 0x01])
[19]
board.ReadI2C(0xC4, 0x31, [0x29, 0x01])
[0]
board.ReadI2C(0xC4, 0x31, [0x29, 0x01])
[0]
board.ReadI2C(0xC4, 0x31, [0x29, 0x01])
[0]
board.ReadI2C(0xC4, 0x31, [0x29, 0x01])
[0]
board.ReadI2C(0xC4, 0x31, [0x29, 0x01])
[60]
board.ReadI2C(0xC4, 0x31, [0x29, 0x01])
[149]

Best regards
Andy
  • Hi,

    The read command itself looks okay but do you know if this specific register has any clear on read bits? I'm wondering if this is a status register and therefore the values are changing. Additionally, have you tried reading any other registers? If so, is it doing the same thing?

    Regards,
    Mandeep Singh