You can use markpoints simply to mark the interesting locations (data , code.) in your application and then use it as a bookmark. This allows you easy switch between different locations which might be usefull especially in a complex application.
So just to clarify: Based on the last reply that markpoints are merely "bookmarks", then Markpoints would not need to use any of the on-chip debug resources. Debug resources would not be necessary if markpoints are merely bookmarks.
However, I'm not sure that this is correct, because the markpoint setup tab in "Controlpoints Configuration" dialog has fields for type of access and size, and proposes a name of "Trigger A".
So this leads me to assume that somehow markpoints are used in conjunction with the on-chip debug triggers.
Could someone explain markpoints more clearly, please? Thanks!!