Changed Behavior - 2023.2 English

The Vitis Unified IDE is now the default GUI when launching with the vitis command. To launch the classic Vitis IDE, run vitis --classic.

To refer to information about the classic Vitis IDE, visit the 2023.1 or earlier version of the documentation.

xparameters.h no longer contains DEVICE_ID definitions. Instead the BASEADDR definition is used. AMD drivers and libraries handle this change. However, if you have legacy code, you need to be aware of this change. You need to change the way your software application addresses the hardware module through X<DUT>_Initialize and X<DUT>_LookupConfig driver functions.

The initialization behavior of ap_int/ap_uint/ap_fixed/ap_ufixed is changed to be more compatible with the C builtin type (int, float...).

ap_int<N> A[N]; // uninitialized, both 23.2 and previous releases

ap_int<N> B[N] = {0}; // With 23.2, the whole array is initialized \
to zero. With previous releases, only the first element is initialized to \
zero, other elements are uninitialized. 

ap_int<N> B[N] = { }; // With 23.2, the whole array is initialized \
to zero. With previous releases, it is uninitialized.

The original qdma_axis<w, 0, 0, 0> has been removed from clib and is replaced with:

template <std::size_t WData, std::size_t WUser, std::size_t
                        WId, std::size_t WDest>
using qdma_axis = hls::axis<ap_uint<WData>, WUser, WId,
                        WDest, AXIS_ENABLE_ALL ^ AXIS_ENABLE_STRB, false>;

In the 2023.2 release the timing model used by the scheduler was changed so that the HLS compiler timing predictions more closely match the Vivado Design Suite. This causes the delay model to be more pessimistic. Major changes include the delay of an AXIS stream interface, and the use of complex enabling conditions for pipeline control. As a result of these changes it is expected that both latency and II can change for designs that were passing before this release.

If a design was meeting timing in HLS and Vivado before, you can restore the original II and latency by adding such constraints via pragmas or directives. You can also reduce clock uncertaintly using the add_clock or set_clock command. With a better HLS timing model, uncertaintly can be reduced. But II constraints (and latency constraints if needed) are a more deterministic mechanism to achieve the same goal.

MLD/MDD MSS filesets are removed and replaced by YAML and CMake filesets.

While xparameters.h is still generated by Lopper Framework, it does not contain DEVICE_ID definitions. Instead, the BASEADDR definition is used. AMD drivers and libraries handle this change. However, users with legacy code need to be aware of this change.