Jens, On Thu, Jan 15, 2015 at 07:07:55PM +0100, Jens Bauer wrote: > Error: Failed to read memory and, additionally, failed to find out where
It would be meaningful to put this in context. You're right that the actions are queued, but if something failed, then an attempt to read the current contents of the hardware TAR register is performed, and if the target can respond at all, it will. But if the communication with the target is lost, it's impossible to investigate where read failed. So basically, it's already working the way you describe, with error-checker (TAR readout) queued and run after something fails. At least that's how I see it. Thank you for the suggestion nevertheless, I think getting user feedback is very important in improving the software, so please keep it flowing. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
