Hi, On Wed, Oct 08, 2014 at 02:10:24AM +0000, Kent Brinkley wrote: > I would like to propose a change to create a microchip target that > moves away for the idcode check and just relies on the target being > MicroChip core.
So basically you want to count on user configuration here, I see. Are you sure Microchip didn't provide any means for autodetection? Is similar user intervention needed for the other debug tools or do they just hardcode a list of IDs? And if you want to specify it manually, you can handle it with "-variant" argument of "target create", and that might be handy for testing. But is it really needed? I have a feeling Microchip gave some thought wrt autodetection before implementing EJTAG. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
