On Tue, Mar 8, 2011 at 2:01 PM, Jean-Claude Repetto <jcr...@mxm.eu> wrote: > Thanks for your answer. Unfortunately, the EFM32 has only a SWD debug port, > no JTAG. So, unless Openocd supports SWD very soon, I'll have to use an > external adapter.
Hey hey! SWD transport is now functional for FT2232H chip (KT-LINK has separate buffers as descibed on [1]) in a few days it will show up in UrJTAG branch and I will move to OpenOCD integration. I wanted to have clear situation before moving forward and bring potentialy more mess than good into OpenOCD (also to have clear situation on my university took some time). It will support ADIv5 for now (point-to-poin SWD), when its frozen and stable, we will move to ADIv5.1 support (multidrop SWD). All mechanisms I have provided with libswd can be reused for totaly different serial transport mehcanisms (such as I2C, SPI, ...). Stay tuned and be prepared for support - meanwhile you can browse libswd project website [2] (doxygen web documentation is up to date) and my works on stm32primer devices [3] (need some updates) :-) Also I am thinking of reusing existing JTAG adapters to perform SWD because i have done urjtag-driver reuse this way. For people that want to have safe solutions dedicated interface (such as kt-link) is necessary, but i have some ideas on how to make jtag adapter swd aware (using libswd and openocd/urjtag) :-) Please note that Cortex CPU has both JTAG and SWD support (howewer not both must be used - if jtag port is available swd can be used as well). Best regards! :-) Tomek [1] http://www.shop.kristech.eu/product_info.php?cPath=57&products_id=257&language=EN [2] http://libswd.sf.net/ [3] http://stm32primer2swd.sf.net/ -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
