On Sun, Jul 5, 2009 at 3:31 AM, Gary Carlson<[email protected]> wrote: > Here is the short story of this patch left out of the first email: > > I have a SAM-ICE device running V8 firmware that I am using on an Atmel > AT91SAM9G20-EK evaluation board.
So the V8 firmware is finally out in the market. I had a V7 mIDAS-Link which is V7 (ADI's version of Segger J-Link). >From the Chinese website http://blog.ednchina.com/taoist/199214/message.aspx V8 is using AT91SAM7S256. V6/V7 is using AT91SAM7S64. Improved SWD using interface chip (V6/V7 from GPIO). Better SWD support. 3 LED indicators instead of one. One for USB Communication; one for target CPU reset status, one for 5V output. Is this in line with your SAM-ICE? There there is the new J-Link Pro which adds Ethernet interface in addition to the USB interface. It is said that it is using AT91SAM7X256. http://www.segger.com/jlink.html > When I execute openocd, approximately > every third attempt causes a complete communication failure, the green light > on the SAM-ICE extinguishes for about three seconds (internal watchdog > timeout in the dongle?), flickers a few times, and then resumes a solid > illumination. The console displays the following messages during the event > and the debugger is left unusable afterwards: > > Jupiter:Embedded garycarlson$ openocd-jlink -f > /usr/local/openocd-config/interface/jlink.cfg -f > /usr/local/openocd-config/target/at91sam9260.cfg > . > . > . > Error: J-Link command EMU_CMD_VERSION failed (-60) > Error: J-Link command EMU_CMD_VERSION failed (-1) > Error: J-Link command EMU_CMD_VERSION failed (-32) This "EMU_CMD_VERSION failed" happens very often with V3/V6/V7. > Info : J-Link initial read failed, don't worry > Info : J-Link JTAG Interface ready > Error: usb_bulk_read failed (requested=1, result=-32) > Error: jlink_tap_execute, wrong result -107 (expected 1) > Error: usb_bulk_read failed (requested=1, result=-32) > . This happens from time to time. > Based on the j-link code written by the original author, I suspect he may > have experienced the same or a similar problem. The code has a while loop > and three retries in the jlink_init function to get communication to work > with the dongle. The first version patch I submitted yesterday has > decreased the statistical startup failure rate in my case from 43% to 2%, > but has not completely eliminated the problem. It does not help me for the V3 and V7 I tried. Strangely the Linux distros play a part as well. It seems to be more stable under Ubuntu 9.04 than Arch Linux. > Unfortunately I only have one j-link device with one particular board. What > I am hoping to find is some other people who use the j-link device with > other CPUs that have also experienced the problem and are willing to test > this patch and a possible revised patch prior to making a final commitment > decision. What I don't want to do is break it for someone else through > unintended consequences. It does not help. It does not make things worse either. > The second version of this patch that I am working on will hopefully reduce > the failure rate from 2% to zero. I will try to get that out either today > or tomorrow if my own testing proves fruitful. > I can test that. -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
