On Mon, 2010-10-11 at 03:23 +0200, Tomek CEDRO wrote: > Hello David, nice to hear from you! :-)
> > I am working on it - preferably FT2232 (KT-LINK) first, then RLink > (Stm32Primer2).. but RLink can be more accessible on the STM32Primer2 > boards.. and also needs some reverse engineering on the protocol. > Which one of them do you think should be made working first to help > SWD development and make it more accessible at the moment? No opinion. Pick one, see what users you pick up. Then the other... :) > > > > The debug adapter drivers can provide a simple SWD driver > > struct with methods that kick in as needed (instead of JTAG). > > So far just one adapter driver has been updated (not yet > > ready to use or circulate). > > Do you mean to initialize the adapter or to perform all SWD operations? I plan to circulate that driver code when both of those work. > > > > The biggest issues are probably > > - fault handling, where the ARM Debug Interface V5 pipelining > > needs work in both JTAG and SWD modes and > > JTAG and SWD have their own ways of detecting/quering errors, but the > sticky-bits part seems to be in fact similar, so maybe one error > handling system could cover both JTAG and SWD..? That'd be best, and is mostly the model I followed when coming up with the ADI-v5 DAP interface. Whether it can really work is another issue. - Dave _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
