Dear Baurzhan,<br><br><div class="gmail_quote">On Fri, Oct 1, 2010 at 4:49 PM, Baurzhan Ismagulov <span dir="ltr"><<a href="mailto:ibr@radix50.net">ibr@radix50.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Fri, Oct 01, 2010 at 04:00:35PM +0800, Morgan Howe wrote:<br>
> Has anyone experienced anything like this or have some idea where to<br>
> look?<br>
<br>
</div>I had a somewhat similar problem which turned out to be floating DMA<br>
control lines of the USB controller, which resulted in incorrect reads<br>
from and writes to the flash on the CPU bus.<br>
<br>
In your case, I'd disable all drivers that are not used in the test case<br>
and repeat the test.<br>
<br>
The next step could be tracing the lowest-level writing routine in the<br>
kernel in order to see whether it is called at all, gets the right data<br>
(e.g., you could generate a file that has the same checksum for every<br>
block written, etc.) and correctly handles status information from the<br>
hardware.<br></blockquote><div><br>I appreciate you taking the time to provide such a helpful response. It definitely gave us some direction to start debugging this problem. As it turns out, we seem to have been able to resolve the problem with some hardware rework.<br>
<br>Thanks and regards,<br>Morgan <br></div></div>