UNCLASSIFIED Hi,
I'll have to confess that what I actually got wrong was some mods to the .mk files. I modified the use of ComponentLibraries so that I could include the CDK component library rather than the components library in the full distro. But a bug was messing up the .lso/.ini file generation and thus I was missing stub libs. I'm now at point where I can build FPGAs with VHDL libraries and VHDL workers from a read only install of the CDK (aka opencpi/ocpi) in /opt/ocpi. Next stop will be building devices and platforms using only the CDK. Cheers, Troy Date: Fri, 03 Feb 2012 05:45:09 -0500 From: James Kulp <[email protected]> To: [email protected] Subject: Re: [opencpi_dev] FPGA Build Issues [SEC=UNCLASSIFIED] Hi Troy, How did you use the ComponentLibraries wrong? Perhaps we can add a better error check. Jim ________________________________ From: Ziersch, Troy (Contractor) Sent: Friday, 3 February 2012 5:22 PM To: 'Shepard Siegel' Cc: [email protected] Subject: RE: [opencpi_dev] FPGA Build Issues [SEC=UNCLASSIFIED] UNCLASSIFIED Hi, I''ve also fixed the unknown module issue. That was me using the ComponentLibraries var wrong. The result was the stubs library was being missed in my local components library but not the CDK one. Cheers, Troy IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ________________________________ From: Shepard Siegel [mailto:[email protected]] Sent: Thursday, 2 February 2012 10:13 PM To: Ziersch, Troy (Contractor) Cc: [email protected] Subject: Re: [opencpi_dev] FPGA Build Issues [SEC=UNCLASSIFIED] Hi Troy, I see two possible issues here. 1) There looks to be some error (and a clue) at line 82 of xxx/gen/xxx.v. I've not seen this error; but it's common to have to work backwards to find the issue. 2) The device is overmapped. Guessing you wanted to infer BRAM but got distributed ram instead. Look closely at the other comments in the XST .srp file wrt to the module that is overmapped. Hope that helps. -Shep On Wed, Feb 1, 2012 at 11:06 PM, Ziersch, Troy (Contractor) <[email protected]> wrote: UNCLASSIFIED Hi, I've been attempting to build an FPGA artefact with my own worker using the Test Bias artefact as a template. i.e. SMA->my worker->SMA My worker is mixed language (VHDL wrapped with Verilog). I've made it as for as map but running into two issues. Firstly: "Building application core "xxx" for target "virtex6"" fails with: "ERROR:HDLCompiler:1654 - "xxx/gen/xxx.v" Line 82: Instantiating <xxx> from unknown module <xxx>". I've checked that the XST -sd flag includes the directories that the SMA and my workers NCD files are in. The sma core is found but my worker is not. I've also checked that the worker pinout matches its instantiation in the generated app core verliog file. I'm able to work around this issue by putting a black box def of my worker into the start of the generated app core verilog file. With the above work around the build continues until the map stage where there is an explosion of Dual Port Slice RAMs when compared to the Test Bias case. For comparison I've included the utilisation I get for the Test Bias FPGA, my FPGA and my worker compiled by itself. All builds are for the ml605 platform. Anyone have any ideas where to look next to solve either issue? Test Bias FPGA Design Summary -------------- Slice Logic Utilization: Number of Slice Registers: 16,119 out of 301,440 5% Number of Slice LUTs: 22,609 out of 150,720 15% Number used as logic: 18,208 out of 150,720 12% Number used as Memory: 4,013 out of 58,400 6% Number used as Dual Port RAM: 886 Number used as Single Port RAM: 0 Number used as Shift Register: 3,127 My FPGA Interim Summary --------------- Slice Logic Utilization: Number of Slice Registers: 23,267 out of 301,440 7% Number of Slice LUTs: 140,332 out of 150,720 93% Number used as logic: 46,103 out of 150,720 30% Number used as Memory: 94,063 out of 58,400 161% (OVERMAPPED) Number used as Dual Port RAM: 90,928 Number used as Single Port RAM: 0 Number used as Shift Register: 3,135 My Worker Design Summary -------------- Number of Slice Registers: 6,936 out of 301,440 2% Number of Slice LUTs: 4,445 out of 150,720 2% Number used as logic: 3,870 out of 150,720 2% Number used as Memory: 8 out of 58,400 1% Number used as Dual Port RAM: 0 Number used as Single Port RAM: 0 Number used as Shift Register: 8 IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email. _______________________________________________ opencpi_dev mailing list [email protected] http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email. _______________________________________________ opencpi_dev mailing list [email protected] http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org
