# XVC Remote debug

**URL:** <https://discuss.pynq.io/t/xvc-remote-debug/737>\
**Category:** Support\
**Created:** [December 11, 2019, 2:30pm UTC](https://discuss.pynq.io/t/xvc-remote-debug/737 "2019-12-11T14:30:09Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![PeterOgden](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/peterogden/32/55_2.png) [@PeterOgden](https://discuss.pynq.io/u/PeterOgden)\
**Post date:** [December 16, 2019, 6:46pm UTC](https://discuss.pynq.io/t/xvc-remote-debug/737/6 "2019-12-16T18:46:08Z")

</div>

You shouldn’t need to change the port from 0.0.0.0 - that will bind to all network interfaces. In theory - yes changing the port and assigning the correct IP to the `debug_bridge` variable all that should be be required. If you are on a Zynq Ultrascale+ board you may also need to do the `cpuidle` [fix](https://discuss.pynq.io/t/pynq-on-zcu104-hangs-when-jtag-is-used/735/2) to prevent the processor from locking when the JTAG chain is accessed. Note that it may not be particularly quick. This was put together as a proof of concept rather than something production ready.

Peter

---

_[View the full topic](https://discuss.pynq.io/t/xvc-remote-debug/737)._