simonqian.openocd wrote: > >> No, all this is necessary. Again, no care how it is implemented, > >> but it must be implemented in some way for SWD. > >Then it can be another function in dap_ops, a smarter replacement > >for current ABORT..? > Yes, I prefer this. But OpenOCD maintainer should look into this > and do the decision.
If you and Tomek are in agreement then I will immediately work on any patches you propose. Send me code any way you can. The best would be via gerrit, but other methods are also good. If a patch is already in gerrit then please let me know and I will look at it. > >> But if JTAG memap_read is transport independent, maybe there > >> will be a performance problem. I'm not sure how to process this > >> patch. I think the first priority is to make it work, performance is only the second objective. > >This can be true as the impelementation of this part can take > >retry and error flags handling into account whereas other > >functions dont anf this could produce a slowdown. Will take a look > >at this when swd is finished, right now it it working and noone > >complains so I would not touch this part:-) > > No, you mis-understanding, I mean that remove adi_jtag_dp_scan in > mem_ap_read_buf_u32, so that this function can be transport independent. > And again, OpenOCD maintainer should look into this and do the decision. I am very sorry for not having a better understand of this already - what exactly is the needed decision? Kind regards //Peter ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
