Sorry to revive an old topic, but I stumbled across this remark:
[quote user="john filo"]My experience so far is that XDS100v2 is so slow as to be completely unusable[/quote]
I think that the XDS100v2 is getting unduely harsh treatment here: the problem appears to be in no small part due to how CCS drives it. For instance, it limits the bitrate to 3 MHz even though the hardware is capable of 30 MHz. I've done some preliminary testing with some custom software driving the XDS100v2 and targeting a DM814x, and even though 30 MHz is far in excess of the max value specified in the datasheet (10 MHz), it appears to work reliably (at least when only ICEPick and one or more DAPs are in the chain).
Of course quite a bit of that will be lost in overhead, mostly due to the (mis)design of DAP and the fact that the FT2232H is not very well suited to JTAG (a small microcontroller would be able to do a much better job), but especially for bulk transfers I still don't see any fundamental obstacles to getting at least to within an order of magnitude of the theoretical max speed.
Which leaves the question, even acceping the 3 MHz limit, why on earth does it take CCS more than 20 seconds to upload and a whopping 40 seconds to download 50 KB of raw data, which means an average transfer rate of little over 10 kilobit/s, 0.34% of the JTAG bitrate?!