Hey Joe and the rest of the Casper community, The toolflow setup page<https://casper.berkeley.edu/wiki/MSSGE_Toolflow_Setup>suggests that you have to have the licensed 10gbe core from Xilinx. Could this be causing the "a core is unlicensed!" error? Joe, do you know if you requested a license from Xilinx for that core?
--Laura On Thu, May 3, 2012 at 2:27 PM, Joe Greenberg <[email protected]> wrote: > Hi John, > Per your request what version we are using: > > Matlab is 7.8.0.347 (R2009a) 64 BIT (ginxa64) Feb 12, 2009 > Simulink is Version 7.3 (R2009a) Jan 15 2009 > We have the ISE files: > MATLAB/ Xilinx_11.1_ISE_DS_SFD/ > MATLAB.2/ Xilinx_11.1_ISE_DS_SFD.tar > MatLab4Linux/ Xilinx_11.5_ISE_DS_lin64/ > mlib_devel/ Xilinx_11.5_ISE_DS_lin64.tar > > Thanks for the help, > Joe > > > > > > > On 05/03/2012 12:37 PM, John Ford wrote: > >> Thanks for the replies. I loaded tut2b.mdl directly from the web site. >>> >>> There were additional errors >>> >>> These two errors occurred multiple times: >>> >>> /Error: Block "const" encountered an error during execution of >>> xlLoadDynamicListContents. Some data may not have been re-loaded >>> correctly. >>> >>> Error: Block "manipulate" encountered an error during execution of >>> xlLoadDynamicListContents. Some data may not have been re-loaded >>> correctly. >>> / >>> >> This looks to me like maybe a versioning error of some sort. Can you tell >> us the versions of your tools? (matlab, simulink, and ISE) >> >> At the end there was the additional error: >>> >>> / >>> INSTANCE:xaui_phy_0 - >>> /users/jgreenbe/projects/**tut2b/XPS_ROACH_base/system.**mhs >>> line 416 - Running XST synthesis >>> ERROR:Xst:1484 - A core is unlicensed ! >>> ERROR:EDK:546 - Aborting XST flow execution! >>> INFO:EDK:2246 - Refer to >>> >> This is an installation problem with your tools, or else it can't contact >> the license manager (which, I think, runs in Socorro...) >> >> John >> >> >> /users/jgreenbe/projects/**tut2b/XPS_ROACH_base/** >>> synthesis/xaui_phy_0_wrapper_**xs >>> t.srp for details/ >>> >>> NGCBUILD done. >>> >>> Rebuilding cache ... >>> ERROR:EDK:440 - platgen failed with errors! >>> gmake: *** [implementation/system.bmm] Error 2 >>> ERROR:EDK - Error while running "gmake -f system.make bits". >>> Return code = 2 >>> No changes to be saved in MSS file >>> Saved project XMP file >>> cp: cannot stat `implementation/system.bit': No such file or directory >>> bit file open failed >>> chmod: cannot access `implementation/system.bof': No such file or >>> directory >>> cp: cannot stat `implementation/system.bof': No such file or directory >>> >>> Error using ==> gen_xps_files at 702 >>> Programation files generation failed, EDK compilation probably also >>> failed. >>> >>> >>> >>> >>> On 05/03/2012 10:37 AM, John Ford wrote: >>> >>>> When I try to compile Tutorial 2b I got the following errors. >>>>> Rich tried compiling Jason Ray's enhanced Tutorial 2 and got similar >>>>> platgen errors. >>>>> Does anyone have any inputs on the possible cause and cure for these >>>>> errors? >>>>> Thanks, >>>>> >>>> What did you name your .mdl file? You can't have any spaces or capital >>>> letters in it. >>>> >>>> There may have been an earlier error than the one you posted. We need >>>> to >>>> see the ones that preceeded this one if there were any. >>>> >>>> You might also post your .mdl file so we can try it here. >>>> >>>> John >>>> >>>> Joe Greenberg >>>>> >>>>> NGCBUILD done. >>>>> >>>>> Rebuilding cache ... >>>>> ERROR:EDK:440 - platgen failed with errors! >>>>> gmake: *** [implementation/system.bmm] Error 2 >>>>> ERROR:EDK - Error while running "gmake -f system.make bits". >>>>> Return code = 2 >>>>> No changes to be saved in MSS file >>>>> Saved project XMP file >>>>> cp: cannot stat `implementation/system.bit': No such file or directory >>>>> bit file open failed >>>>> chmod: cannot access `implementation/system.bof': No such file or >>>>> directory >>>>> cp: cannot stat `implementation/system.bof': No such file or directory >>>>> >>>>> Error using ==> gen_xps_files at 702 >>>>> Programation files generation failed, EDK compilation probably also >>>>> failed. >>>>> >>>>> >>> > >
