On Thu, Oct 31, 2013 at 12:06 PM, Jens Bauer <[email protected]> wrote:
> I've also been thinking that it could be a problem with my platform, but
> no, libusb works on my platform, so it *has* to be a software problem, and
> thus it will be possible to fix it.
> It's still possible that it's a value read frm an uninitialized buffer.
>
Could you post a -d3 debug log up to the point of failure (IR capture
error) in case there's something suspicious there. You could also configure
OpenOCD with verbose I/O enabled (don't remember the exact flag) for extra
information.
I looked at the G4 Mac, but it's a bit too bulky to have lying around for
the occasional test. A Mac Mini would be nice, but I don't feel like
spending the money. I'll first give another shot at my qemu mips-be machine
on a second host.
/Andreas
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
