I agree and I think the trouble reports so far also agree - -
The timing is set to be marginal at best, and fail randomly at worse.
What you have found is a common problem with the Linux USB stack -
It has strange ideas of when a packet (and/or command) should be buffered at times.
I am about to post a plan to get more information out of the machine about how it is set before we try to load and start the RAM kernel.
Will have to wait for Hawhill's comments on that next post -
since he would have to make changes to his K3Flasher.
|