Vivado to SDK export randomly produces new hardware platform

[neowt]

Hi,

  Sometimes when I make changes to an existing Vivado project and re-export hardware (with bit file) to SDK, a new hardware platform is generated.  I cannot identify a pattern when a new platform is created or old one is over-written.  Then within SDK, I have 2 hardware platforms, the older one on which my software are still based on, and the new one which I want to use.  I have to manually edit the BSP to map to the new patformform.

  May I know how I can get Vivado/SDK to overwrite the old platform?

  Versions I have seen this behaviour: Vivado 2014.2, Vivado 2014.4.  The changes are merely additional probes signals that does not affect software.

Regards,

Neo

[sampatd]

Check these:
http://www.xilinx.com/support/documentation/sw_manuals/xilinx2014_4/SDK_Doc/tasks/sdk_t_auto_sync.htm

http://www.xilinx.com/support/documentation/sw_manuals/xilinx2014_4/SDK_Doc/tasks/sdk_t_change_hwspec.htm

http://www.xilinx.com/support/documentation/sw_manuals/xilinx2014_4/SDK_Doc/tasks/sdk_t_retarget.htm

[neowt]

Hi,

  According to the links, SDK would update the existing hardware platform when I re-export from Vivado.  SDK would not create a new hardware platform.  Can you explain under what conditions a new hardware platform will be created?

Neo