arty Arty bsd project won't run Bitgen in Vivado 2015.4

[dr_b]

When trying to run the Digilent bsd project for Arty, Vivado 2015.4 cannot run Bitgen due to 2 critical warnings. I have been able to run the Digilent Xadc_Demo and GPIO projects successfully with no problems. I'm wondering if there is an error in the .tcl script for the bsd project. I've attached the Vivado critical warning messages. I'm new to both VIvado and Arty so I would appreciate help.

[hamster]

Hi!

The top-level signal spi_ss_io has not been given a because it has already been taken by something else. 

Something to do with "shield_dp0_dp19" at a guess.

Mike

[dr_b]

Thanks for the reply. I was thinking along the same line but since I'm a newbie at Vivado I'm not sure how to proceed with a fix. I thought that the Digilent project would be a slam dunk example like the other two (Xadc_demo and GPIO) which completed fine but apparently there are some bugs in the bsd project that haven't been fixed. I looked at the file "c:/Xilinx/Vivado/2015.4/data/boards/board_files/arty/C.0/part0_pins.xml" and found that <pin index="64" name ="shield_dp0_dp19_tri_i_10" iostandard="LVCMOS33" loc="V17"/> and <pin index="93: name ="spi_ss_i" iostandard="LVCMOS33" loc="V17"/> are both connected to the same location, "V17". Looking at the Digilent Arty schematic, "V17" on the XC7A35T-L1CSG324I FPGA is the "CK_IO10" line corresponding to the "shield_dp0_dp19_tri_i_10" Arduino connector. I can't find "spi_ss_i" anywhere on the Arty schematic. If the design intent is to use "CK_IO10" on V17 as an SPI slave select line ("spi_ss_i") apparently that is the wrong way to implement it as far as Vivado is concerned. I'm tempted to just delete the "spi_ss_i" line and see if Vivado can run Bitgen successfully. Any other thoughts?

[dr_b]

More on this...I just noticed that CK_SS on the Digilent Arty schematic is FPGA location C1 NOT V17 as specified in the file  "c:/Xilinx/Vivado/2015.4/data/boards/board_files/arty/C.0/part0_pins.xml". I'll try making that correction and see if all goes well.

[dr_b]

Still more on this...the Vivado Bitgen completed the Digilent bsd project successfully when I made the above correction to the part0_pins.xml file. I'm wondering if anyone else actually ran this project or if this error has just been out there since the project was generated. I suppose someone could have messed up the file but that seems unlikely. Now I need to figure out if the Check Timing warnings (80 no_input_delay and 76 no_output_delay) with High Severity are of consequence or not. If they are I guess I'll need to find a way to fix that. Any ideas?

[sLowe]

I believe these delays are just for simulation purposes. The warnings are basically saying you haven't specified your input and output delays to the real world so a system that works in theory may not work on the board.

I have successfully ignored them in the past if I am wrong about that.

-Sam