If I build the Vivado project targetting REV D, but keep the SDK usr/user_config.h hardware target REV E, there are no obvious warnings. This will lead to issues where users get unexpected behavior...
Fix this by throwing a build error if Vivado does not match the user config for the C code.
If I build the Vivado project targetting REV D, but keep the SDK
usr/user_config.h
hardware target REV E, there are no obvious warnings. This will lead to issues where users get unexpected behavior...Fix this by throwing a build error if Vivado does not match the user config for the C code.