On Mon, 2009-04-20 at 18:56 +0200, Michael Fischer wrote: > Hello Zach, > > >* J-Link driver (w/ yellow hardware): > > - cure buggy madness (this is my own poorly qualified TODO item) > Does it works on your side? Here I have a jlink too and want to get > it working under Mac OS X. And old version, I think 717 was working > with e.g. STR710, but the new SVN not anymore. I could start openocd > and reset the target, but the GDB do not want to download the program > to the CPU.
It has worked better in the past, but it has never worked 100% for me. I used something in that epoch to get a working configuration running, but I now have time to focus on fixing the current SVN trunk. Still, this puts me with hardware that has been verified to work in other scenarios, and I have been using the telnet interface to eliminate GDB as a factor. Recently, I evaluated IAR's ARM tools for a client, so I know what remains to be achieved for us to reach full functionality. In the end, the problem can only be OpenOCD; further, your reply to Magnus (with your FTDI test results) indicates that the problem almost certainly exists within the J-Link driver and not at other layers. > Your yellow one, which version it is? Here I have a v6.0. Same. Once I know the source files are clear of pending patches, I will start pushing changes to get the driver cleaned up and fixed. I will do a thorough audit of the driver against the documentation that I have and try to find out exactly what is going wrong. Cheers, Zach _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
