From: Jens B. <jen...@gp...> - 2013-10-31 12:22:46
|
Hi Andreas. I attached a -d3 log called "errorLog.txt" on the original post. Will that do, or do you need a different one ? I'll try and see if I can figure out about configuring OpenOCD with verbose I/O, but I'm most likely too sleepy right now to do anything useful. ;) (Yes, I burned the midnight oil again) Love Jens On Thu, 31 Oct 2013 13:12:16 +0100, Andreas Fritiofson wrote: > > On Thu, Oct 31, 2013 at 12:06 PM, Jens Bauer <jen...@gp...> 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 |