Sounds good to me. Regards Luca
On 12/04/2011 18.56, Michel JAOUEN wrote:
Hello, Following your advice, here is a set of 3 patches impacting only cortex_a functions: 0001-cortex_a-use-dap-ref-from-armv4_5common.patch : No change in cortex_a behaviour, dap is always selected from armv4_5common 0002-cortex_a-multiple-target-on-the-same-dap.patch : Cortex_a behavior is changing ,on the same tap, the 1st initialization build the dap instance, The other instance relies on the 1st instance. 0003-cortex_a-apb-mem-read-write-working-with-mmu_on.patch : Support memory read even from apb mem access even if mmu is on : (This support is needed for ste u8500, DDR is not accessible from ap mem) Best regards -----Original Message----- From: Øyvind Harboe [mailto:[email protected]] Sent: Monday, April 11, 2011 8:26 PM To: Michel JAOUEN Cc: luca ellero; [email protected] Subject: Re: cortex_a : dap_ap_select issue when multiple target on the same dap I haven't been following cortex work closely enough to comment in detail, but a couple of things come to mind: try to split the commits into the "harmless" first and then later on those that enable new features and have a bigger chance of breaking things. Having small commits will make it easier to review the changes. That said, it sounds to me like you're heading in the right direction. Perhaps we can come up with more clever ways of separating jtag tap and dap later on, but I don't have any clever suggestions as of writing.
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
