01-27-2015 06:01 PM
In SDK projects in Vivado 2014.x, we see an accumulation of  hw_platforms and  breakpoints. They're really seperate issues but they seem to have one thing in common - they accumulate.
It seems like hw_platforms are automatically created when a hardware change is made (which makes sense) but sometimes when no hardware change is made e.g., when a project is copied from 1 team member's PC to another. Our work-around to elliminate duplicate hw_platforms is to delete all of them and re-open the SDK so that there's just one - hw_platform_0.
Breakpoints also seem to accumulate in the debugger. These appear as duplicates for the same memory location as if old break points are getting replicated and accumulate till I get download errors where the download stalls at, say, 53% and never finishes. The work-around is to simply delete the duplicate breakpoints in the breakpoint window.
01-27-2015 06:11 PM
That is a strange behavior. Would that be possible to share the project for further analysis?
01-27-2015 06:34 PM
01-28-2015 05:24 PM
if this is targeting a development board, then a xml file should be sufficient.
If this can not be shared i will retry the same procedure with a simple example design.
02-03-2015 10:05 AM - edited 02-03-2015 10:06 AM
Here's an example xml file for an Artix project that has accumulated 2 hardware platforms and several copies of break points for line 760 in main.c. As a work-around, I'll manually delete the duplicate breakpoints and I'll delete both hw_platforms and then close&re-open the SDK to re-create hw_platform_0.
I'd guess that the xml file isn't enough and that you'll need more of the project, like the whole 'project.sdk' directory or the whole Vivado project. Just let me know.