Now that AVaRICE 2.12 is done: About a week ago (after the release candidate was out), I started a branch to finally implement a better error recovery / cleanup method than the old "sometimes return codes, sometimes punt without cleaning up the ICE, sometimes do nothing" one.
I restructured the code quite a lot, to make use of C++ exceptions wherever an exceptional situation needs reporting/handling. The biggest advantage of that is that it not necessarily means the next higher layer has to handle an exception by itself; if it doesn't, the exception is automatically passed up. As a result, this should drastically reduce the amount of situations where AVaRICE just bails out, leaving the JTAG ICE "in limbo", where only a powercycle would help. As a side-effect, it resolves things like the feature request to decode the ICE error codes in a textual form. So if anyone wants to give it a try, I merged the branch back to the SVN trunk now that release 2.12 is out. I've been testing it a bit during the past days, and could resolve all the remaining issues I found. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ avarice-user mailing list avarice-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/avarice-user
