Other Parts Discussed in Thread: DM385
Hi,
We are trying to integrate ISS functionality from IPNC 3.5 into EZSDK 5.05 for DM385 platform. The communication with the ISS driver is already working and we are enabling MIPI CSI2 capture.
We are following the instructions from the ISS_TMS (SPRUH30B), specifically the CSI2 PHY and Link Initialization Sequence to start the Complex I/O module, so we set the line positions as follows:
CSI2_COMPLEXIO_CFG[2:0]CLOCK_POSITION = 0x1
CSI2_COMPLEXIO_CFG[3]CLOCK_POL = 0x0
CSI2_COMPLEXIO_CFG[6:4]DATA1_POSITION = 0x2
CSI2_COMPLEXIO_CFG[7]DATA1_POL = 0x0
CSI2_COMPLEXIO_CFG[10:8]DATA2_POSITION = 0x3
CSI2_COMPLEXIO_CFG[11]DATA2_POL = 0x0
Rest of the lines are unused. We are trying to get frames from an OV5640 sensor.
According to TMS, the flow is:
1. Configure Complex I/O lines.
2. Deassert the Complex I/O reset
3. Force RX Mode Signal using the CSI2_TIMING[15] register
4. Power up the Complex I/O setting CSI2_COMPLEXIO_CFG[27] = 1
5. Check whether the state status reaches the ON state ( CSI2_COMPLEXIO_CFG[25] = 1 )
But for some reason, the status bit [25] never reaches 1. We have also tried to enable the module using the sequence found on the ISS driver source code, in issdrv_captureApi.c, using the following calls:
1. issCsi2rxInit()
2. issCsi2rxConfig()
3. issCsi2rxStart()
but that seems to fail powering up the complex I/O as well.
We have the pinmux configuration equal to an IPNC example where the capture works just fine, and the CSI2 clock set to: ISS_CLKCTRL[3]CSI_A = 0x1
Are we missing some configuration for the Complex I/O or ISS module? Some kind of missing PLL config, a clock gate or some power voltage that need to be muxed to the complex I/O?
Also, we found that the working IPNC example is running the ISS clock at 400Mhz, our EZSDK is running the ISS clock at 200MHz, could that be an impediment for the complex I/O module to enable?
Thanks in advance!
DiegoSolano
