On May 3, 2014, at 11:15 PM, Paul Fertser <[email protected]> wrote:
>> >> The platform may have 8 cpus. I do not want to connect and attach, >> and probe every single CPU. Perhaps I only want to connect and >> attach to the (NTH) cpu. >> >> With auto discovery, how do I tell the system to *SKIP* a specific >> CPU, there is no means to do that. > > I think they should have provided some robust DAP-level solution to > auto-enumeration, topology discovery etc. > > Since that's not happened, well, we should provide some means for > manual configuration indeed. It has nothing to do with a “more robust DAP level solution” - the problem is auto discovery, that is an openocd problem. Openocd does not have a command to specify target(X) on the Coresight DAP and to skip target(Y) In contrast for JTAG based targets it does. Example: FPGA(1) + arm7tdmi + arm926 + FPGA(2) To debug I can create 3 different config files, (1) the arm7 only, (2) the arm926 only, and (3) with both all three config files describe the tap chain … the difference is creating or not creating targets. Since I wrote the configuration file … I can control what is ‘discovered’ In contrast, OpenOCD could scan the JTAG chain (auto-discover) and automatically build the TARGET LIST based on the JTAG ids. If that happened would a need for a command to tell Openocd *ONLY* use tap position (X) and to skip position(Y) -Duane. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
