> On 25 Jan 2017, at 11:10, Paul Fertser <[email protected]> wrote: > > ... all of the probes that > were supported by the old ft2232 interface driver should be supported > by the current "ftdi" driver, ... "interface/ftdi/olimex-arm-usb-ocd.cfg"
oops! sorry, my mistake, I had an old debug configuration which failed due to the missing file and I did not investigate further. I confirm that the old Olimex probe works with the new ftdi interface. I also fixed the blog post, please check it and let me know if you have further suggestions. > 3. I suggest to refrain from using MD5 hashes for anything, as they're > considered to be insecure since long; right. do you have a specific suggestion? I wouldn't go for very complicated cryptographic tools only to check the integrity of some files, job that some time ago was successfully performed by a simple checksum. > 4. An interesting new option provided by current libusb release on > Windows is the usbdk backend which allows one to use vendor jlink > drivers (or vendor ftdi drivers etc) with any libusb application, > including OpenOCD. You might want to consider giving it a go. thank you, I personally do not use windows at all, but, if you want, we can add a paragraph to the blog post announcing this new feature, and possibly other features. feel free to send a pull request, the page is publicly available at: https://github.com/gnuarmeclipse/gnuarmeclipse.github.io-source/blob/master/_posts/openocd/releases/2017-01-24-openocd-v0-10-0-20170124-released.md best regards, Liviu ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
