> -----Original Message----- > From: openocd-development-boun...@lists.berlios.de [mailto:openocd- > development-boun...@lists.berlios.de] On Behalf Of Freddie Chopin > Sent: woensdag 24 juni 2009 18:28 > To: openocd-development > Subject: [Openocd-development] Creative summary of options for > OpenOCDdistros > > OK - be creative. End the flames, throw some ideas. Here goes another > summary of REALISTIC and ACCEPTABLE options, if ftd2xx.dll will still be > "censored" in the distributions. > > 1. Any kind of network protocol that would talk to "driver". > > PRO - Possibilities to use JTAGs over internet to debug remotely, > possibility to use closed-source drivers (for me that's a pro [; ) > > CONS - latency of the medium, need to run another program on one's PC, > someone has to create the program and that has to be more complicated > than the one from option 2.
Freddy, Talking over de network may not be an option for Windows. A couple of years aho I worked on a portable (Linux / Windows) client - server application that used tcp/ip. On Linux this worked fine but on Windows XP we quickly learned that many short packets takes a lot of CPU power (even when send & received on localhost). We ended up using a shared memory & signals solution on Windows. A bit more cumbersome to write, but it performed very well. Nico Coesel _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
