RTOS/TDA2PXEVM: Issue in adding a new code in iss single channel usecase on psdk 3.03 on TDA2px-EVM

Hrishikesh Rajurkar

Part Number: TDA2PXEVM
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

Hello All,

We are working to add EEPROM read/write support for TDA2PX-EVM . We are using psdk3.03 with sysbios all configuration. The build environment is ubuntu 16.04.

Using BSP functions (similar to what is used in ..\packages\ti\drv\vps\src\boards\src\bsp_boardTda2xx.c to read board revision) we have developed a wrapper around EEPROM read functionalities using I2C (i2c instance BSP_DEVICE_I2C_INST_ID_0 and slave address 0x50. The new source file is kept in drv folder and accessed from our use case single channel ISS capture Display

The same has been tested on psdk3.02 in sdcard boot as well as using binaries over CCS and it is working fine.

But when same is ported for psd3.03, we are seeing message as

[IPU1-0] 86.956536 s: CHAINS: Using DCC Profile from Driver
[IPU1-0] 86.967272 s: *** UTILS: CPU KHz = 20000 Khz ***
[IPU1-0] 87.042243 s: Setting Camera Power to 3!!!
[IPU1-0] 87.042335 s: Waiting for 100 milliseconds!!!
[IPU1-0] 87.142255 s: Serilaizer # 0 has I2CAddr 74 !!!
[IPU1-0] 87.159336 s:
[IPU1-0] 87.159641 s: i2cMdSubmitChan: i2c4 transfer to slave address 0x74 failed
[IPU1-0] 87.159732 s: src/bsp_deviceI2c.c @ Line 580:
[IPU1-0] 87.159854 s: I2C4: DEV 0x74: WR 0x07 = 0x28 ... ERROR !!!
[IPU1-0] 87.159946 s: src/bsp_deviceI2c.c @ Line 602:
[IPU1-0] 87.160037 s: I2C4: Error timeout 1 ms!!!
[IPU1-0] 87.160098 s: Could not configure serializer !!!
[IPU1-0] 87.160159 s: Failed to initialize the serializer on camera # 0!!!

after completing capture setting for sensor used OV2775 Sensor 1080p30 - TIDA00113 and when we try to run the use case.

Am I missing some thing here?

Please reply

regards

Hrishikesh

over 7 years ago

0 Rishabh Garg over 7 years ago

TI__Guru 55685 points

Hi Hrishikesh,

There is already a thread on this: e2e.ti.com/.../685677
I have pinged ISS experts to help you on that.
Please don't start duplicate threads.

Regards,
Rishabh

0 Hrishikesh Rajurkar over 7 years ago in reply to Rishabh Garg

Expert 1165 points

Hi Rishabh,
I have closed the older thread e2e.ti.com/.../685677 . I have opened this one with more details and rephrasing. Please treat this as current thread.
regards
Hrishikesh

0 Brijesh Jadav over 7 years ago in reply to Hrishikesh Rajurkar

TI__Guru**** 476575 points

Hrishikesh,

There were some minor changes in 3.3 release, some of the APIs are moved from BSP to vsdk. There should not be any functionality change, so it should work. In fact, it works fine in the release binary. Are you checking released binary?

Rgds,
Brijesh

0 Hrishikesh Rajurkar over 7 years ago in reply to Brijesh Jadav

Expert 1165 points

Hi Brijesh,
Thanks for reply. The 3.3 release is working as it is but when i add new code (a wrapper for EEPROM read/write using bsp functions (Bsp_deviceI2cProbeDevice,Bsp_deviceRawWrite8 and Bsp_deviceRawRead8 APIs) in BSP, i see these error, even if I dont call these functions from vsdk use case.
For 3.2 it worked fine. I have tested with release binaries as well as sd boot AppImae
For 3.3 It is failing in both cases. with error message as in earlier message.
regards
Hrishikesh

0 Brijesh Jadav over 7 years ago in reply to Hrishikesh Rajurkar

TI__Guru**** 476575 points

Hi Hrishikesh,

It seems that your newly added RawRead and RawWrite are creating problem. Can you try reading any other i2c client and see if it works?

Rgds,
Brijesh

0 Hrishikesh Rajurkar over 7 years ago in reply to Brijesh Jadav

Expert 1165 points

Hi Brijesh,
I am using the APIs like Bsp_deviceRawWrite8 and Bsp_deviceRawRead8 and Bsp_deviceI2cProbeDevice in newly added file and i am not calling these functions anywhere though it is in build system. Do you mean to test with another i2c instance and slave address to check its working ?
regards
Hrishikesh

0 Brijesh Jadav over 7 years ago in reply to Hrishikesh Rajurkar

TI__Guru**** 476575 points

Hi Hrishikesh,

No, can you try reading back register values on the same device?

Can you check if without these changes, are you able to configure OV2775?

Is it possible that the i2c address is clashing with OV2775 sensor? Please check.

Regards,

Brijesh

0 Rishabh Garg over 7 years ago in reply to Brijesh Jadav

TI__Guru 55685 points

Hi Hrishikesh,

Is there an update on this?

Regards,
Rishabh

0 Hrishikesh Rajurkar over 7 years ago in reply to Rishabh Garg

Expert 1165 points

Hi Rishabh

Sorry for the late reply as was working with some other issues. But the error of failing to connect to camera sensor was observed by some of collegues also who were not having my changes in their application and it is coming randomly.

I am planning to start my integration from scratch and update again

regards

Hrishikesh

0 Rishabh Garg over 7 years ago in reply to Hrishikesh Rajurkar

TI__Guru 55685 points

Hi Hrishikesh,

Thanks for the update. You can start a new thread in case this one has locked out due to timeout.

Regards,
Rishabh

Processors

Processors forum

RTOS/TDA2PXEVM: Issue in adding a new code in iss single channel usecase on psdk 3.03 on TDA2px-EVM