From: Andreas F. <and...@gm...> - 2013-10-31 08:54:33
|
On Thu, Oct 31, 2013 at 1:53 AM, Jens Bauer <jen...@gp...> 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 |