Hi! On Tue, Oct 13, 2009 at 1:28 PM, Magnus Lundin <lun...@mlu.mine.nu> wrote: > Without looking deeply (lot of other work the coming weeks) I think this > is good, but I would like it in a separate file(module). Called > adiv5_component, adiv5_debug or coresight_component ?? > > So the adiv5 code talks to the MEMAP registers but does not handle the > memory mapped components that are accessed through the the MEMAP. This > includes the content of the ROMTABLE.
Hmm, I do not think so. 1) access to components is a part of the same ADIv5 specification IHI 0031A (shouldn't it be called then swjdp.c like it was?) 2) if you want to have the layer independent of ap and components layers, then there should be no links in that direction, only from components towards DP. As a result the cpu layer, which uses both components and AP accesses should be aware of scanning, handling (storing/freeing...) scanning results and so on. Or I misunderstood your point? > > Best regards, > Magnus > >> Hi! >> >> What about implementing more generic access to ADIv5 and APB-AP? >> I see it like this but what gurus have in mind? _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
