Jump to content

Nik

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by Nik

  1. Hi ! I switched back to Digilent MIPI IPs, but does not seem to work. I used same configuration code provided in the reference design. Is there any way to debug MIPI IP. I used ILA and found no streaming of data. I am using vivado 2019.1. Thanks,
  2. Hi ! Thank you for the response. I solved the issue by using the interrupt handler. This time PCam is fully configured. However, I am not getting the data from MIPI IP. The TVALID signal is always LOW. Note that I am using Xilinx's MIPI CSI-2 RX Subsystem. What can be the issue here? Thanks !
  3. Thank you. It helped me a lot. But I am having little problem in IIC data writing. The program control stuck infinitely in the following code. while ((!TransmitComplete && !slave_nack_flag_)|| (XIic_IsIicBusy(IicInstance) == TRUE)); Thanks,
  4. Is anybody there? I want to know how four Pcams addresses are set in ZedBoard 4Pcam FMC Adapter Demo project. How channel_masking is working and what is the value of a_pin? I am trying to write a custom code for accessing and configuring the the four pcams but unable to do so. I need your help. Thanks,
  5. Hello, Does ZedBoard 4PCam FMC Adapter Demo Design support Petalinux? Regards,
  6. Hello, I am following digilent's ZedBoard 4Pcam FMC Adapter Demo project. But I need your help to understand some of the code line. Could someone help me to figure out in the following code lines? This following code has been taken from main.cc. /* main.cc */ ..... //Constructing OV5640 objects in dynamic storage vs. automatic makes //ignoring cameras with init exceptions possible //Since the power enable signals is shared between all FMC Pcam Adapter ports, //cam_a will be the only one controlling it through the gpio_driver. try { muxch_a_ptr = std::make_unique<TCA9546>(iic_driver, 0, 1 << 0); cam_a_ptr = std::make_unique<OV5640>(*muxch_a_ptr, nopgpio); } catch (std::runtime_error const& e) { VERBOSE("Camera on port A did not initialize correctly: %s", e.what()); } ..... When I open TCA9546.h. I have noticed following lines of code /** * * @param iic is the underlying I2C_Client driver to-be-wrapped * @param a_pin specifies the mux hardware address pins A2-A0 on its 3 LSB * @param channel_mask should have the bit(s) corresponding to the * addressed channel(s) set to 1. */ TCA9546(I2C_Client& iic, uint8_t a_pin, uint8_t channel_mask) : iic_(iic), channel_mask_(channel_mask) { dev_address_ &= ~0x07; dev_address_ |=(a_pin & 0x07); reset(); } From above codes, I need your help to understand that how these codes are working to access PCam A in ZedBoard 4PCam FMC Adapter. What is happening here? Thanks ! Kind Regards,
×
×
  • Create New...