@Laurent:
>For now, if you want to speed up your OpenOCD , build OpenOCD with d2xx driver 
>:-) !

Tried that on windows ... Makes no difference, either driver gives the same 
speed, the bottleneck is OpenOCD, on Linux I can't even get openocd to see the 
adapter with the d2xx driver, I have to use libftdi ...

@Øyvind:
>Somebody just has to step up and do the work to profile the Cortex-M3 flash 
>programming case and rewrite the higher level codes and performance should >be 
>dramatically improved.

I agree totally, it shouldn't be too hard to get >200KB/s with some 
modifications for this micro, after all sending 256bytes per 1ms USB frame is a 
no-brainer ... USB can support 1500bytes per 1ms frame in theory, 1200 bytes in 
practice, and you can easily get around the latency issues. I have done this 
with USB->CAN at these sorts of speeds no problem.

@Peter:
>Any real solution just has to give up trying to run this from the PC.
>It's stupid. I think some dongles do more or less of it already.
>FT2232 obviously does not do it at all, whether full or high speed.
>The USB-Blaster CPLD seems to be slightly more clever, but is not quite fully 
>utilized.
>A PC is USELESS for any kind of bitbanging or the like (MPSSE in crap FTDI 
>chips counts just the same!) - there are *at least* THREE bus masters >between 
>CPU and IO pin, and you want it to be fast? Come on..

Rubbish! The bottleneck is OpenOCD,  A PC is more than capable to do all the 
work necessary to support "dumb (read simple)" interface chips like the FT2232, 
I like OpenOCD's concept of putting all the brains in the software and support 
simple/cheap hardware ... After all who wants another BDI2000, like Øyvind 
says, it just needs a little work.

Not that I have much of a say, but I fully support improving OpenOCD on cheap 
adapters rather than "relying" on the purchase or building of an intelligent 
adapter .. I think that is the wrong direction to go ..... My 2c

Cheers,
Bernie





_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to