Hello Luca! On Sat, Feb 12, 2011 at 12:54 PM, Luca Ellero <lro...@gmail.com> wrote: > dap_ap_select was used in the code at various points, but that can lead to > confusion, without any knowledge of what AP is really selected at some > points. (...)
This is also somehow related with the TRANSPORT and DP system that interconnects the interface/cable and the DAP (Debug Access Port). Transport is related with DAP in case of ARM because ARM DAP has SW-DP and JTAG-DP that both provide access to the AHB-AP... however in different manner - JTAG has its own registers while SWD use different "addressing" [1]. New Cortex from TI have even something that delects the DAP that makes things more complicated. I think it could be nice to clearly separate those structures (INTERFACE, TRANSPORT, PICK, DP, DAP, AP (bus), FLASH, ...) and work through their instance on the real hardware by using functions to change instance value/state. I am working on such model with (not yet functional) libswd [2] - what is more there is even a context that keeps all those instances separated, so maybe it would be possible to use many interfaces-targets at once.. work in progress... :-) Best regards, Tomek [1] http://stm32primer2swd.sf.net/ [2] http://libswd.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
