Announcements
IMPORTANT: Cypress Developer Community is transitioning on October 20th. To learn more and be prepared for this change, check out our latest announcement.
cancel
Showing results for 
Search instead for 
Did you mean: 

USB Superspeed Peripherals

AkCh_1378701
New Contributor

Hi sir,

here, we made a custom CX3 baseboard, but encountering an issue that, appinit init sequence failed,  at MipicsiInit function.

i guess that is kind of self init for CSI RX inside the CX3 chip,  not for camera TX..

i have a CX3 EVB, for comparison with the custom board, both without camera module connected, based on identical firmware programmed in between boards.

the CX3 EVB doesn't have that issue. but custom board has..   i was wondering what cause the error, could you give an advice how to further debug that?

thanks

CHEN

0 Likes
1 Solution
YangyangC_06
Employee

That is correct. CX3 will configure the MIPI block inside via I2C communication. Find detailed informaiton in the CX3 TRM below

https://www.cypress.com/documentation/technical-reference-manuals/ez-usb-cx3-technical-reference-man...

The addres of the MIPI block is 0x0E(W) and 0x0F(R).

Try to check if you have another I2C device which has the same address, or if you have made a correct hardware design.

View solution in original post

0 Likes
5 Replies
YangyangC_06
Employee

Could your code work on Denebola board?

0 Likes
AkCh_1378701
New Contributor

yes, the code works on Denebola board..  but it doesn't work on the custom made board..

0 Likes
AkCh_1378701
New Contributor

Hi sir

it is found that i2c bus, there is no ack issue, the slave address sent from the i2c master is 0x0e or 0x0f..

is it possible, i2c master of cx3 sends to i2c slave devices, which is inside cx3 chip? 

thanks

0 Likes
YangyangC_06
Employee

That is correct. CX3 will configure the MIPI block inside via I2C communication. Find detailed informaiton in the CX3 TRM below

https://www.cypress.com/documentation/technical-reference-manuals/ez-usb-cx3-technical-reference-man...

The addres of the MIPI block is 0x0E(W) and 0x0F(R).

Try to check if you have another I2C device which has the same address, or if you have made a correct hardware design.

View solution in original post

0 Likes
AkCh_1378701
New Contributor

Thanks sir,

we found that the root cause was the external i2c circuitry having an level shift related issue.  it was resolved, and mipicsiinit function returns no error..

0 Likes