Hello
On Wed, Aug 14, 2013 at 12:17 PM, Jason Ray <[email protected]> wrote:
> All,
>
> Occasionally I've noticed (maybe a handful of times over the past few
> months) that progdev will fail with our roach2 boards. After working fine
> for long periods, it will fail to program out of nowhere and the only fix is
> to reboot the roach2.
> --> 115 raise KatcpClientError("Client not connected")
So one of the reasons why you are disconnected may be that
tcpborphserver3 is no longer running. This can be caused by a software
error internal to tcpborhpserver (the kernel will report a sigsegv, 11 typically
and somtimes sigabort, 6 in cases where I detect major internal
consistency failures)
or by a bus timeout when doing io to the fpga, when the gateware isn't
quite doing
the right thing - the latter generally shows up as a sigbus signal, 7.
To distinguish between the two options, get a shell prompt on the roach2
and type dmesg
Also: If you check the mailing list archive you should see some
activity relating to bus timeouts in April
regards
marc
