Closed yonnorc42 closed 4 days ago
That is a good question! I'm not exactly sure why they are not present in Vivado/EDIF, but they are listed in the Unisim and libraries guide. It could be that they are populated automatically through other properties being set, but I'm not sure. They don't hurt for them to be there and potentially it could make file sizes smaller when they specify the default settings to simply omit them. However, they aren't listed when querying the properties of a cell in the Vivado GUI. Sorry I couldn't be of more help. If you find behavior that changes due to their presence or absence, let us know.
I was running some tests with DSP48E1's using RapidWright, and there's something I don't understand. I have a test design which only contains 1 DSP48E1, and the properties that are listed are here:
It contains IS_x_INVERTED properties for the CLK, CARRYIN, ALUMODE, INMODE, and OPMODE. However, in another design I have, those properties aren't there:
It's worth nothing that the DSP48E1 that does contain those properties was directly instantiated by me (although I didn't specify the IS_x_INVERTED properties), and the one without those properties was just inferred because the design used multiplication in some spots, and it's also worth noting that these properties are listed in the unisim library for DSP48E1's
https://github.com/Xilinx/XilinxUnisimLibrary/blob/1c8e05fd1e9a79ceb8b996a0996674122eed086f/verilog/src/unisims/DSP48E1.v#L57-L61
My question is why those properties only show in RapidWright for some DSP48E1's. As far as I knew, all instances of the same cell type will have the same properties each time, even though the values are different. In neither case are those specific properties directly set so they should all just be the default values. If you want to check it out yourself, I attached the files, and this is the python script I used to check the properties using RapidWright.
dsp_and_edf.zip
@reillymck