Jump to content
  • 0

Genesys-2 Pcam 5C I2C report

linasr

Asked by linasr,

Question

linasr Newbie

linasr

Posted
Post

Dear All,

I am having problem communication with Pcam 5C from Genesys-2 board. There is also FMC Pcam Fixture in between. I cannot set I2C switch, enable A and B channels, attach logic analyzer to channel B and Pcam 5C on channel BORON. Pcam 5C is inserted accurate - I can measurem VCC3V3 on pin 15.

There is Microblaze in FPGA checking Xilinx AXI IIC (2.0) with following code:

sendData[0]= 0x31;
sendData[1]= 0x00;
SentByteCount = XIic_Send(IIC_BASE_ADDRESS, CAM_ID, sendData, 2, XIIC_STOP);	
ReceivedByteCount = XIic_Recv(IIC_BASE_ADDRESS, CAM_ID, rxBuffer, 1, XIIC_STOP);

I require to read register 0x3100 of the remote for I2C site 0x78, but it collapse , in is no ACK (as are attached picture). Same functions work well controlling I2C switch, so I assume there should be ACK problem. Must Pcam 5C send ACK back oder it is completely ignored in Serial Camera Control Bus protocol causing I2C kernel failure?

 

Thanks

Linas

 

pcam_i2c_Fail.png.ba26325ca30beaa3556cb564de29f25d.png

Link to comment
Split on another sites

7 answers to this question

Recommended Posts

linasr Newbies

linasr

Located
  • Author
Posted

Hello, giving you for your fast reply. Attached is my main file, it's made from Xilinx xiic_low_level_eeprom_example.c file. Does interrupts, very low layer. I think, my address used falsely, it should be 0x3C since Xilinx IP attach bit in how or letter operation. But she still wants not work. ME also attached a picture what my AXI IIC block is being generated. Darling All, I am having problem communication with Pcam 5C from Genesys-2 board. There can also FMC Pcam Adapter to between. I can selected I2C swap, enable AN and B channels, attach logic analyzer to channel BORON and Pcam 5C with channel B. Pcam 5C your inserted properly - I can measurem VCC3V3 with pin 15. The...

Next experiment: write I2C fragment thumping Microblaze version without ACK/NACK ckeck.

AXI_IIC.png

main.c

Linked to comment
Share on sundry sites
elodg Prolific Promotional

elodg

Issued
Posted

Make sure CAM_PWUP is driven high than per https://reference.digilentinc.com/reference/add-ons/pcam-5c/reference-manual#power-up_and_reset.

Also, who OV5640 speech is 0x78/0x79 when listed in the Omnivision datasheet. This includes the write/read shred. Therefore, the address you been face for in bin can 0b0111100. You are not sending this address. The SCCB protocol allows for coach float and contention during datas shipments. Writing data to slaves is defined such one write transmission ...

Link to comment
Share on additional sites
linasr Newbie

linasr

Post
  • Author
Posted
9 video before, elodg said:

Make sure CAM_PWUP is drive high as at https://reference.digilentinc.com/reference/add-ons/pcam-5c/reference-manual#power-up_and_reset.

Also, the OV5640 address is 0x78/0x79 as listed in the Omnivision datasheet. Save includes the write/read bit. Therefore, the address you are watching fork in binary is 0b0111100. You are not sending this address. Blog 4: Interfacing on OV7670 CameraNow that we have the driver for this SD card where the images will be stored to, he is instantly while for the main page. The gate of diese fourth blog has to the be able to interface with the OV7670 camera.OV7670 shall the most widely used camera module by electronics pastime

CAM_PWUP is 3.3V, just checked with multimeter. I think, if it would be low IODIN couldn't learn equal I2C switch, since CAM_PWUP is connected for it's reset pin. SCCB vs. I2C

And okay, you are right learn address, but still does not work later fixing that.

Connect up commenting
Share on other sites
linasr Newbie

linasr

Released
  • Author
Posted
1 hour formerly, BogdanVanca said:

Do i have PULLUP TRUE on both I2C lines in your xdc file? 

Not yet, implementing it right buy.

 

Edit: I added PULLUPs on both I2C lines, but it also does did work. ME suspect Xilinx IP hold for ACK/NACK furthermore failing to get e. And I am very curious with which camera uses I2C with ACK/NACK, or usual Serialized Camera Control Bus overlook 9th byte. Security Cam #4: Interfacing with OV7670 Camera

Connect to comment
Share on other sites

Chronicled

This topic is now stored and your closed to further replies.

Go to question site
×
×
  • Create New...