I did some more searching and I found this github issue with a workaround:
https://github.com/EttusResearch/uhd/issues/103

(begin quote):

I hit the same ddr3_32bit build error on Windows:

[IP_Flow 19-3475] Tcl error in ::ipgui_ddr3_32bit::updateAllModelParams
procedure for IP 'ddr3_32bit'. Loading device for application Rf_Device
from file '7k410t.nph' in environment
C:/Xilinx/Vivado/2015.4/ids_lite/ISE.
child killed: floating-point exception

Workaround I found is the following:

$ cd build-ip/xc7k410tffg900-2/ddr3_32bit/
$ rm mig_a.prj
$ cp mig_xc7k410tffg900-2.prj mig_a.prj

It looks like tcl does not like mig_a.prj being a link on Windows.

(end quote)




The build seems to successfully get past the mig however it fails on the
"pga" block (much later in the build process):

synth_ip: Time (s): cpu = 00:47:50 ; elapsed = 00:55:13 . Memory (MB): peak
= 1815.309 ; gain = 1479.445
BUILDER: Adding file from Block Design list: C:
                                               pga
                                                  pga-maintusrp3        op
ERROR: [Vivado 12-172] File or Directory 'pga' does not exist
INFO: [Common 17-206] Exiting Vivado at Mon Jan 29 15:12:30 2018...
make[1]: *** [Makefile.x300.inc:111: bin] Error 1
make[1]: Leaving directory '/cygdrive/c/fpga/fpga-maint/usrp3/top/x300'
make: *** [Makefile:61: X310_HG] Error 2



I will switch over to the master branch if you think my time will be more
productive there? I saw that you are working toward a new release very soon.



On Mon, Jan 29, 2018 at 2:52 PM, Martin Braun via USRP-users <
usrp-users@lists.ettus.com> wrote:

> On 01/26/2018 03:49 PM, Martin K via USRP-users wrote:
> > I have Cygwin64 setup in Windows 10
> > Vivado 15.4.2 installed and licensed.
> >
> > [...]
> > Some web searching shows that other people have had trouble with the mig
> > failing - on both Windows and Linux, but obviously it works for you
> > guys.  I appreciate any advice.
>
> We've had issues like this (not sure if exactly this issue), and
> recently saw them again when we updated Vivado (I think). Maybe this is
> a Cygwin issue, but maybe not. Which branch are you running? If it's
> master, can you update to the latest and try 2017.4?
>
> -- M
>
> _______________________________________________
> USRP-users mailing list
> USRP-users@lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>



-- 
Martin K.
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Reply via email to