openocd connection causes FIQ #27
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When the OpenOCD connection is establishing, the CPU is reset and briefly booting. This is very apparent if the board is set up to boot from SD card with a firmware that prints to the UART; but the issue also occurs with other boot modes including JTAG (in which case it is running whatever old code was in OCM). That SD card firmware will be (re)started a few times when OpenOCD connects.
This is a rather minor problem but it leads to confusing behavior.
Fixed in
c9b48c80a0
Still happens sometimes.
Seems it's not a reset but a FIQ.
should this be closed?
It's still a problem I think (though a very minor one).
I don't see reboots?
IIRC it would just print FIQ now, since we have a dedicated FIQ handler which just prints and halts.
Indeed, it just prints FIQ now. But why is there a FIQ?
It seems to me that this is due to gateware in artiq-zynq.
In experiments, no FIQ is triggered when the device is halted.
In SZL, FIQ is still triggered even if the artiq-zynq firmware is not run. And it did not trigger after cancelling the gateware loading.
openocd connection reboots the CPUto openocd connection causes FIQ