In the 2016.3 release of SDK, While debugging on Zynq/Zynq MPSoC, triggering a processor core reset from outside of the debugger causes the core to halt at the reset vector.
How can I resolve this?
The Debugger enables the vector catch to halt the processor core at the reset vector when a core reset is triggered.
If it is not desirable to halt the core at the reset vector, you can disable debugger access to that core, so that the vector catch is not turned on and the core does not stop at the reset vector. Access can be disabled from XSDB, as follows:
configparams disable-access 1
xsct% configparams disable-access 1