# KV260 read mipi frame stuck on dma, help

**URL:** <https://discuss.pynq.io/t/kv260-read-mipi-frame-stuck-on-dma-help/5347>\
**Category:** Support\
**Created:** [March 14, 2023, 11:11am UTC](https://discuss.pynq.io/t/kv260-read-mipi-frame-stuck-on-dma-help/5347 "2023-03-14T11:11:47Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![cking](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/cking/32/5476_2.png) [@cking](https://discuss.pynq.io/u/cking)\
**Post date:** [October 30, 2023, 2:16pm UTC](https://discuss.pynq.io/t/kv260-read-mipi-frame-stuck-on-dma-help/5347/7 "2023-10-30T14:16:17Z")

</div>

Hi Mario,

Unfortunately I don’t have the expertise to poke any further into the driver design of PCam5C for KV260 PYNQ. I do sense there is something inherently wrong under the surface I’m just unsure where.

After reading: [Pcam not generating frames · Issue #27 · Xilinx/Kria-PYNQ · GitHub](https://github.com/Xilinx/Kria-PYNQ/issues/27) I have realised I am in the same boat. The camera can be seen at address _3c_ only after `mipi.start()` is entered from the top level in python.

But writing to this address at all using axi.iic.send/recieve from the axi iic class defined under pynq/lib ([https://github.com/Xilinx/PYNQ/blob/master/pynq/lib/iic.py](https://github.com/Xilinx/PYNQ/blob/master/pynq/lib/iic.py)), works (doesn’t prompt an error) but reading the output from the command reads nothing. The only output is whatever integer is entered in either the send/receive function, should this be the case?

It would be great to have someone look into the problem as it has clearly troubled some people, particularly I would say because the Xilinx KV260 board is advertised as the go to board for all things vision related - including its “plug and play” rpi camera connector.

Thanks,  
Cameron

---

_[View the full topic](https://discuss.pynq.io/t/kv260-read-mipi-frame-stuck-on-dma-help/5347)._