On 20.03.2018 8:54, Matthias Welwarsky wrote:
currently the DAP support for ARMv7 and v8 targets is undergoing a major
restructuring. As a result many target configurations and possibly board
configurations need to be adjusted.
The big change might be also a good opportunity to improve related stuff.
1) The concept of 'dap apsel n' is mostly debris of pre #3165 code
(3165 = arm_adi_v5: Make the DAP API stateless). If we solve cortex_a
apsel usage in more reasonable way, dap->apsel can be dropped completely.
2) The same name is traditionally used for both tap position and target
name (e.g. stm32f2x.cpu).
Although it is perfectly ok from the machine point of view as there are
different namespaces,
it may confuse user. It is just a change in target config in the same
place where we goint to add
'dap create'...
What do you think?
Tom
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
