Re: [Usbpicprog-technical] Weird transient failures on some programs

[Matthijs K. <mat...@st...>]

Hi,

> when creating a few initial testing programs, I've been suffering from the
> "Hardware should say OK" error message. After some investigation, it seemed as
> if some hex files would consistently trigger this message, while others would
> consistently work. Some more investigation shows that is the case that the
> working programs work _most_ of the time, but not always.

I've mucked around in the PC application sources a bit, and it seems the error
is caused by an USB timeout in readString (which I gathered from adding a
cout line, since the wxLogError call that is in readString didn't show up
anywhere for me).

As a hack I tried increasing the USB timeout (USB_OPERATION_TIMEOUT) from
1000ms to 3000ms, which magically solved all my problems, including the
erasure problems (though I've only tested a handful times on the Linux PC, not
the Windows one).

Could it be that the USB controller is causing this? Both machines I've tested
on are laptops with very similar hardware.

Gr.

Matthijs