On Sun, May 27, 2012 at 4:42 AM, Tomek CEDRO <tomek.ce...@gmail.com> wrote: > Please see how OpenOCD is organized, take a look at TARGET first, then > DEBUG. TRANSPORT AND INTERFACE is below target. Transport is already > implemented somehow in openocd master. Interface is implemented only in my > fork, openocd master still use cable that is part of jtag queue. I will make > structural reorganization after swd is finished. > On Sun, May 27, 2012 at 4:50 AM, Tomek CEDRO <tomek.ce...@gmail.com> wrote: > I think this is TRANSPORT layer that should be responsible for TARGET > commands processing. And TARGET can decide on how to process the commands - > if INTERFACE is intelligent TRANSPORT will simply pass commands to > INTERFACE, if INTERFACE is dump then transport will generate bitstream for > INTERFACE. With this approach the code is already there, just need some > better organization :-) > > Isnt that clean simple and elegant?
Nice summary. You answer clears some of my doubts to your libswd. I need to read more about your work. -- Xiaofan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
