Hallo MIPSers, i was reviewing my own patch about avoiding mips32_configure_break_unit for ejtag 2.0 devices. But now i see, it's not so trivial. This version has break capability, but it is not reflected on DCR, like it is done on 2.5 and alter. And most Memory-Mapped Registers have different addresses. Before i'll write a patch, i would like to have some comments and suggestions. Should we have names like EJTAG_DBA1_V25 and EJTAG_DBA1_V15 or, do some init time assignments so other part of openocd do not do recheck each time thay use this addresses?
Other comments about ejtag 1.5-2.0? -- Regards, Oleksij ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
