I've just uploaded a new version that gives NO speed penalty (however insiginificant this penalty was...). These are the figures (compared to what I posted yesterday, verified that the figures for "reverted" match):
--- TEST 2B core @ 120MHz, CCLK == 120000, USB 2.0 adapter (JTAG-lock-pick Tiny 2) a. ft2232.c driver, adapter_khz == 6000 - previous fix applied wrote 524288 bytes from file d:/load.hex in 45.307617s (11.301 KiB/s) wrote 524288 bytes from file d:/load.hex in 45.303711s (11.302 KiB/s) - revert applied wrote 524288 bytes from file d:/load.hex in 44.911133s (11.400 KiB/s) wrote 524288 bytes from file d:/load.hex in 44.922852s (11.397 KiB/s) - new fix applied wrote 524288 bytes from file d:/load.hex in 44.935547s (11.394 KiB/s) wrote 524288 bytes from file d:/load.hex in 44.932617s (11.395 KiB/s) b. ftdi.c driver, adapter_khz == 6000 - previous fix applied wrote 524288 bytes from file d:/load.hex in 10.327148s (49.578 KiB/s) wrote 524288 bytes from file d:/load.hex in 10.294922s (49.733 KiB/s) - revert applied wrote 524288 bytes from file d:/load.hex in 10.448242s (49.003 KiB/s) wrote 524288 bytes from file d:/load.hex in 10.274414s (49.833 KiB/s) - new fix applied wrote 524288 bytes from file d:/load.hex in 10.299804s (49.710 KiB/s) wrote 524288 bytes from file d:/load.hex in 10.301757s (49.700 KiB/s) c. ft2232.c driver, adapter_khz == 15000 (fastest for 120MHz core) - previous fix applied wrote 524288 bytes from file d:/load.hex in 44.667969s (11.462 KiB/s) wrote 524288 bytes from file d:/load.hex in 44.678711s (11.460 KiB/s) - revert applied wrote 524288 bytes from file d:/load.hex in 44.429688s (11.524 KiB/s) wrote 524288 bytes from file d:/load.hex in 44.417969s (11.527 KiB/s) - new fix applied wrote 524288 bytes from file d:/load.hex in 44.394531s (11.533 KiB/s) wrote 524288 bytes from file d:/load.hex in 44.347656s (11.545 KiB/s) d. ftdi.c driver, adapter_khz == 15000 (fastest for 120MHz core) - previous fix applied wrote 524288 bytes from file d:/load.hex in 8.908204s (57.475 KiB/s) wrote 524288 bytes from file d:/load.hex in 8.761718s (58.436 KiB/s) - revert applied wrote 524288 bytes from file d:/load.hex in 8.709961s (58.783 KiB/s) wrote 524288 bytes from file d:/load.hex in 8.766602s (58.403 KiB/s) - new fix applied wrote 524288 bytes from file d:/load.hex in 8.712891s (58.764 KiB/s) wrote 524288 bytes from file d:/load.hex in 8.855469s (57.817 KiB/s) e. ft2232.c driver, jtag_rclk - previous fix applied wrote 524288 bytes from file d:/load.hex in 71.053711s (7.206 KiB/s) wrote 524288 bytes from file d:/load.hex in 71.046875s (7.207 KiB/s) - revert applied wrote 524288 bytes from file d:/load.hex in 70.862305s (7.225 KiB/s) wrote 524288 bytes from file d:/load.hex in 70.917969s (7.220 KiB/s) - new fix applied wrote 524288 bytes from file d:/load.hex in 70.812500s (7.230 KiB/s) wrote 524288 bytes from file d:/load.hex in 70.810547s (7.231 KiB/s) f. ftdi.c driver, jtag_rclk - previous fix applied wrote 524288 bytes from file d:/load.hex in 57.305664s (8.935 KiB/s) wrote 524288 bytes from file d:/load.hex in 57.230469s (8.946 KiB/s) - revert applied wrote 524288 bytes from file d:/load.hex in 57.043945s (8.976 KiB/s) wrote 524288 bytes from file d:/load.hex in 57.604492s (8.888 KiB/s) - new fix applied wrote 524288 bytes from file d:/load.hex in 56.940430s (8.992 KiB/s) wrote 524288 bytes from file d:/load.hex in 56.939453s (8.992 KiB/s) --- 4\/3!! ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
