Hi Andreas. Yes, my guesses was round the USBLib, but still OpenOCD already uses USBLib indirectly through the FTDI-driver, so that would be unlikely too. It doesn't *have* to be a BE problem, but I think it's more likely than the problem is something else.
Can I assume you're located in Sweden ? :) Today I just looked, and there are a few PowerMac G4 for sale. One is 1.25GHz single core and USB 1.1, price=DKK 500. All PowerPC based Mac Mini have USB 2.0, which is much more interesting (speed=1.25GHz..1.5GHz), unfortunately those cost from DKK 1000 and up. But you're working for free, so DKK 500 might not be cheap; it's simply not fair to ask you to pay for working on something that's free (!) I have a YellowDog Linux in the drawer (it works on a PowerMac G4/PowerBook G4/Mac Mini G4, but I never installed it). I'll be happy to send you a copy in case you get your hands on a G4. ;) But usually, Mac OS X will behave much like Linux does. After updating autotools, the difference is hardly noticable. (After a fresh Mac OS X install, you need to install "Developer Tools", they're free, and you can start building on the command line immediately). An alternative is that I could give you an account on a PowerMac G5 (my primary computer), and you could make some tests. Not as fun as having a local computer, but if it's a help, let me know. Love Jens On Thu, 31 Oct 2013 09:54:26 +0100, Andreas Fritiofson wrote: > > > > On Thu, Oct 31, 2013 at 1:53 AM, Jens Bauer <[email protected]> wrote: >> Hi all. >> >> I've wanted to use the FTDI driver since I first heard of it. >> But due to the other problems I've been though, I thought they were >> the cause that the FDTI driver did not work for me. >> I'm now using the JTAG-lock-pick Tiny 2 (but I hve the exact same >> problems when using Olimex ARM-USB-TINY-H) >> >> So far, I'm past the worst big-endian problems, and also the >> problems with the LPC43xx acting up (thanks for the fix, Nemuisan) >> >> The following line works: >> $ openocd -f interface/jtag-lock-pick_tiny_2.cfg -f >> Flashing/Board/Board.cfg -c "flashNow TestFile.elf" >> >> But this line does not: >> $ openocd -f interface/ftdi/jtag-lock-pick_tiny_2.cfg -f >> Flashing/Board/Board.cfg -c "flashNow TestFile.elf" >> >> (There seem to be no difference when I add 'sudo ' in front of openocd) >> Now, it appears that noone else are seing this problem, so it might >> be a Big Endian issue, but I haven't spotted anything in the sources >> yet. >> >> What would most likely cause this to go wrong (eg. approximately >> where should I look) ? > > Interesting. I would be surprised if there were endianness problems > in the ftdi driver but not in the ft2232 driver. The driver mostly > handles byte streams. I've tried setting up a BE virtual machine to > test but I currently haven't succeeded due to problems with the host > USB controlller driver acting up. If anybody could tell me an easy > way to test or know a *cheap* and commonly available BE machine with > USB that runs a modern linux with little or no setup, please do. > > I would suspect that the interface definition in > interface/ftdi/jtag-lock-pick_tiny_2.cfg doesn't match hardware, but > since you have the same problem with the Olimex hardware, that's > unlikely the problem. > > /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
