On 21/06/2011, at 1:07 AM, Laurent Gauch wrote:
>>/
/>>/ >/ On Mon, Jun 20, 2011 at 1:00 PM, Steve Bennett <steveb at workware.net.au <https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote:
/>>/ />>/ On 20/06/2011, at 8:54 PM, Øyvind Harboe wrote:
/>>/ />>/ />>>/ On Mon, Jun 20, 2011 at 12:50 PM, Steve Bennett <steveb at
workware.net.au <https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote:
/>>/ />>>>/ Instead, just produce a warning
/>>/ />>>/ />>>/ Why?
/>>/ />>>/ />>>/ It merits a comment at least?
/>>/ />>/ />>/ Seems self-evident to me.
/>>/ />>/ Why should it be fatal just because a value couldn't be read?
/>>/ />>/ Doesn't stop anything from working.
/>>/ />/ />/ Why should we support broken hardware or drivers?
/>>/ />/ />/ Better the user is told to toss his busted dongle / hardware than
to tangle
/>>/ />/ with subtle followon errors?
/>>/ /
/>>/ Nothing to do with hardware. It's a problem with the driver.
/>>/ See
http://www.mail-archive.com/openocd-development@lists.berlios.de/msg15945.html
/>>/
/>>/ >/ /
/>/ Objection !
/>/
/>/ If we cannot read this value back, this means we reach trouble with driver or device somewhere.
/>/ Also, this trouble could affect following access ...
/>/ This is why we stop with fatal error.
/
OK. So what alternative solution would you suggest to make this driver work?
What version of the driver do you use. If it really come from the driver and if
this is the last official driver, then ask the writer of the driver to correct.
If no correction are done quickly by the writer of the driver, then yes, you
may just produce a warning.
Regards,
Laurent
http://www.amontec.com/jtagkey.shtml
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
