Re: [AVaRICE-user] First release candiate for AVaRICE 2.12
As Joerg Wunsch wrote: Given that the changes are a little more intrusive than they used to be in previous releases, I'd ask everyone to give the release candidate a try. According to Sourceforge's download statistics, a number of people downloaded both, the source tarball as well as the Win32 zip file. In the hope that at least some of those who picked up the files had a chance to test it, and given that no bug report came in, I'd like to release AVaRICE 2.12 tonight. -- cheers, Jorg .-.-. --... ...-- -.. . 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
[AVaRICE-user] First release candiate for AVaRICE 2.12
Thanks to Detlev Kraft's reverse engineering of the way AVR Studio 5 talks with the JTAGICEmkII/AVRDRAGON, and thanks to his detailed analysis of that communication, I could add support for ICE firmware versions 7.x to AVaRICE. (With Detlev's permission, I added his document to the doc/ folder in SVN. Sorry, it's in German only.) In particular, this improves the situation for Xmega devices a lot. For the first time, I'd claim that AVaRICE now supports Xmega devices (but only if you had a chance to upgrade your ICE firmware to 7.x). Sorry, data breakpoints (watchpoints in GDB terminology) are not supported on Xmega devices. This appears to be a limitation of the ICE firmware right now, AVR Studio 5 does not support data breakpoints at all (not even for MegaAVR devices, where we continue supporting it). I also added some minor performance improvements, in particular PC caching, so AVaRICE finally makes use of the BREAK event the ICE sends whenever it stops the target CPU, thus eliminating the need to send another CMND_READ_PC again. In some areas, I think we might now even be faster than AVR Studio 5 (e.g. AVR Studio issues 32 separate ICE commands to read the CPU registers, while we read all 32 registers in one request). Given that the changes are a little more intrusive than they used to be in previous releases, I'd ask everyone to give the release candidate a try. Obviously, people who'd like to test the new features with version 7.x firmware are very welcome, but likewise, I'd like to know whether everything else still works the way it used to previously (i.e., all Tiny/Mega devices should continue to work as before, for any supported ICE firmware version). For the convenience of Windows users, I could find a Windows machine to compile it under Cygwin, and provide a Windows .exe file (in the .zip archive). You propably need an installed Cygwin to resolve the various cyg*.dll dependencies, sorry, but that's unavoidable the way AVaRICE is written (which is fairly Posix-centric, using fork(), unnamed pipes, IO multiplexing and all this). If you encounter any bugs, please do not hesitate to fill in a bug tracker item on sourceforge.net. -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ avarice-user mailing list avarice-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/avarice-user
Re: [AVaRICE-user] First release candiate for AVaRICE 2.12
As always I'm very impressed by the work you do to support AVR under Linux. Unfortunately it's of no use to me at the moment since I use ARM now. Keep up the good work! /Janne On Fri, 2 Dec 2011 21:56:37 +0100 Joerg Wunsch j...@uriah.heep.sax.de wrote: Thanks to Detlev Kraft's reverse engineering of the way AVR Studio 5 talks with the JTAGICEmkII/AVRDRAGON, and thanks to his detailed analysis of that communication, I could add support for ICE firmware versions 7.x to AVaRICE. (With Detlev's permission, I added his document to the doc/ folder in SVN. Sorry, it's in German only.) In particular, this improves the situation for Xmega devices a lot. For the first time, I'd claim that AVaRICE now supports Xmega devices (but only if you had a chance to upgrade your ICE firmware to 7.x). Sorry, data breakpoints (watchpoints in GDB terminology) are not supported on Xmega devices. This appears to be a limitation of the ICE firmware right now, AVR Studio 5 does not support data breakpoints at all (not even for MegaAVR devices, where we continue supporting it). I also added some minor performance improvements, in particular PC caching, so AVaRICE finally makes use of the BREAK event the ICE sends whenever it stops the target CPU, thus eliminating the need to send another CMND_READ_PC again. In some areas, I think we might now even be faster than AVR Studio 5 (e.g. AVR Studio issues 32 separate ICE commands to read the CPU registers, while we read all 32 registers in one request). Given that the changes are a little more intrusive than they used to be in previous releases, I'd ask everyone to give the release candidate a try. Obviously, people who'd like to test the new features with version 7.x firmware are very welcome, but likewise, I'd like to know whether everything else still works the way it used to previously (i.e., all Tiny/Mega devices should continue to work as before, for any supported ICE firmware version). For the convenience of Windows users, I could find a Windows machine to compile it under Cygwin, and provide a Windows .exe file (in the .zip archive). You propably need an installed Cygwin to resolve the various cyg*.dll dependencies, sorry, but that's unavoidable the way AVaRICE is written (which is fairly Posix-centric, using fork(), unnamed pipes, IO multiplexing and all this). If you encounter any bugs, please do not hesitate to fill in a bug tracker item on sourceforge.net. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ avarice-user mailing list avarice-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/avarice-user
