When a new HDF file is exported from Vivado to SDK in the 2017.2 release, the files within the hardware platform project are not updated properly.
This will lead users to unknowingly use a set of stale files; psx_init, mmi, and bit files while configuring.
The HDF information is also used to build the Board Support Package (BSP) and set the relevant compiler options (if using the MicroBlaze).
If this file is not updated in the hardware platform, then some of the previous settings might be lost in the update process.
For example, one common issue could be that the stdin and stdout properties are modified from the default UART values to coresight.
This is a known issue for the SDK 2017.2 release and there are two available work-arounds.
SDK plugin patch:
Note: % here is the timestamp of the plugin.
As a work-around, the HDF container can be manually opened from XSCT.
You will see the container files updated:
This can also be achieved from the Vivado Tcl console:
You will also need to check if your Board Support Package (BSP) settings have been updated as expected.
To view the BSP settings, right click on the BSP in Project explorer and select Board Support Package settings.
|Name||File Size||File Type|