# AXI BRAM breaks overlay design

**URL:** <https://discuss.pynq.io/t/axi-bram-breaks-overlay-design/775>\
**Category:** Support\
**Created:** [December 19, 2019, 3:37pm UTC](https://discuss.pynq.io/t/axi-bram-breaks-overlay-design/775 "2019-12-19T15:37:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![frank](https://avatars.discourse-cdn.com/v4/letter/f/3d9bf3/32.png) [@frank](https://discuss.pynq.io/u/frank)\
**Post date:** [December 19, 2019, 3:37pm UTC](https://discuss.pynq.io/t/axi-bram-breaks-overlay-design/775/1 "2019-12-19T15:37:08Z")

</div>

Hello,

I’m trying to get a rather simple block design to work on Vivado 2019.1 (Linux). I’m using the PYNQ-Z2 with the v2.5 boot image.

It’s just a Zynq7 PS, three GPIOs, an AXI BRAM controller, and what gets added by the connection automation (reset, AXI SmartConnect, memory generator).

Without the BRAM, the project works fine. But with the BRAM, it fails in the synthesis step.

The generated error is:  
“design1\_axi\_bram\_ctrl\_0\_bram\_0\_synth\_1 (1 error)  
[Common 17-55] ‘set\_property’ expects at least one object.  
Resolution: If [get\_(value)] was used to populate the object, check to make sure this command returns at least one valid object.”

There is also one critical warning, in case it is important:  
“design1\_axi\_smc\_0\_synth\_1 (1 critical warning)  
[Common 17-161] Invalid option value ‘10,000’ specified for ‘period’. [”~/Xilinx/Vivado/2019.1/ram2/ram2.srcs/sources\_1/bd/ram\_desu/ip/ram\_desu\_axi\_smc\_0/ooc.xdc":3]"

Do you have an idea what might be the cause of this problem?

Regards,

Frank

p.s.  
For more details, I’ve been following this tutorial:

> [@Tutorial: Creating a hardware design for PYNQ](https://discuss.pynq.io/t/tutorial-creating-a-hardware-design-for-pynq/145):
>
> Creating a new hardware design for PYNQ The previous tutorial showed how to rebuild the reference base design for the PYNQ-Z1/PYNQ-Z2 boards. This tutorial will show you how to create a new Vivado hardware design for PYNQ. This tutorial is based on the v2.4 PYNQ image and will use Vivado 2018.2. The PYNQ-Z2 board was used to test this design. If you are using the PYNQ-Z1 or PYNQ-Z2, first make sure the board files have been installed. Download the [PYNQ-Z1 board files](https://github.com/cathalmccabe/pynq-z1_board_files/raw/master/pynq-z1.zip) or the [PYNQ-Z2 board files](https://dpoauwgwqsy2x.cloudfront.net/Download/pynq-z2.zip),…

---

<div class="post-metadata">

**Author:** ![gnatale](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/gnatale/32/11_2.png) [@gnatale](https://discuss.pynq.io/u/gnatale)\
**Post date:** [December 20, 2019, 11:06am UTC](https://discuss.pynq.io/t/axi-bram-breaks-overlay-design/775/2 "2019-12-20T11:06:24Z")

</div>

Please share your .tcl file. This is a Vivado issue, not PYNQ-related.  
There’s probably an error in your tcl

---

<div class="post-metadata">

**Author:** ![gnatale](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/gnatale/32/11_2.png) [@gnatale](https://discuss.pynq.io/u/gnatale)\
**Post date:** [December 20, 2019, 11:08am UTC](https://discuss.pynq.io/t/axi-bram-breaks-overlay-design/775/3 "2019-12-20T11:08:22Z")

</div>

I also recommend you redirect this question to the Xilinx forum (or search for it there) because again, this is a Vivado issue (or likely a mistake in your project)

For instance, take a look here: [https://forums.xilinx.com/t5/Synthesis/set-property-expects-at-least-one-object/td-p/818063](https://forums.xilinx.com/t5/Synthesis/set-property-expects-at-least-one-object/td-p/818063)

---

<div class="post-metadata">

**Author:** ![frank](https://avatars.discourse-cdn.com/v4/letter/f/3d9bf3/32.png) [@frank](https://discuss.pynq.io/u/frank)\
**Post date:** [December 20, 2019, 8:27pm UTC](https://discuss.pynq.io/t/axi-bram-breaks-overlay-design/775/4 "2019-12-20T20:27:15Z")

</div>

Thank you, I have tracked the problem down!

It was a problem with my localisation settings. Some parts of Vivado honour the decimal separator setting, some parts don’t and expect a decimal “.” dot. That results in Vivado confusing itself. I fixed those settings, and now it works.

Regards, Frank
