Bugs item #3587834, was opened at 2012-11-16 01:57 Message generated for change (Comment added) made by svenq You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=425407&aid=3587834&group_id=39505
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: svenq (svenq) Assigned to: Nobody/Anonymous (nobody) Summary: Avarice dies with timeout upon memory read Initial Comment: Avarice dies with a receive timeout when reading memory from an ATMega32u4 via JTAG, after apparently correct initialization. MCU: ATMEGA32U4 Tools: AVR JTAG ICE mkII, FW 7.28 or FW 6.x Avarice 2.10, 2.12 or 2.13 on Gentoo Linux or Debian Linux avr-gdb 7.2 or 7.6 Same setup works with AVR Studio 6 ---------------------------------------------------------------------- Comment By: svenq (svenq) Date: 2012-11-19 12:12 Message: When starting debugging with Atmel Studio, i noticed a quite long delay. Thus i tried to increase the JTAG_RESPONSE_TIMEOUT in jtag.h to 5 seconds. This makes some basic things possible. The following steps have been done in GDB. The corresponding avarice log is attached as "avarice-debugging-02.txt". in GDB: - connect to target. This takes approx 5 seconds. - set Breakpoint at main - continue. Execution will be halted at the breakpoint. (another 5 seconds) - Reading registers and Memory works (no delay) - single step (takes up to one minute) - set breakpoint in main loop and continue - Breakpoint in main loop gets hit only once. - interrupting the program (ctrl-c) takes long (up to one minute) - alternatively avarice quits with a timeout. I'm not sure if this information is useful, it's just for completenes. ---------------------------------------------------------------------- Comment By: Joerg Wunsch (joerg_wunsch) Date: 2012-11-16 09:18 Message: The main difference between both appears to be the use of the undocumented command 0x36, rather than the old CMND_SET_DEVICE_DESCRIPTOR. So far, I assumed command 0x36 is only used for Xmega device, but perhaps it is to be used in general now. In addition to the already known usage (with a 0x0002 as the initial value of the configuration record), it seems the IO register bitmaps are also configured through command 0x36, but with initial values 0x0080, 0x0081, 0x0088, 0x0089. This configuration method looks very similar to what the JTAGICE3 uses (see the respective feature request and attached USB trace). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=425407&aid=3587834&group_id=39505 ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ avarice-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/avarice-user
