cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
3,836 Views
Registered: ‎01-19-2009

Vivado crash when compiling mor1kx processor

Jump to solution

#
# An unexpected error has occurred (11)
#
Stack:
/lib/x86_64-linux-gnu/libc.so.6(+0x33250) [0x7f5db0591250]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libverific.so(Verific::veri_file::IncludeFileName(char const*, Verific::ColLineFile*)+0x6b) [0x7f5d879ba0cb]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libverific.so(Verific::veri_file::IncludeFile(char const*)+0x70) [0x7f5d879c1620]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libverific.so(verilex()+0x91e) [0x7f5d879c36be]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libverific.so(veriparse()+0xbc5) [0x7f5d879f3f85]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libverific.so(Verific::veri_file::AnalyzeInternal(char const*, unsigned int, char const*)+0xc2) [0x7f5d879bb282]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libverific.so(Verific::veri_file::Analyze(char const*, unsigned int, char const*, unsigned int)+0xc8) [0x7f5d879bb478]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_filemgmt.so(HADGParserVerilogVerific::analyze(HADGParserConfigHolder*, bool, bool, HDGUIStatus&)+0xbb) [0x7f5d91bffc0b]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_filemgmt.so(HADGParserConfigHolder::analyzeFile(bool, HSTVector<HDDASrcFile*, std::allocator<HDDASrcFile*> >&, HDGUIStatus&, std::string const&)+0x184) [0x7f5d91bf9f64]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_filemgmt.so(HADGDesignGraph::analyzeFiles_HSV1(bool, HDGUIStatus&)+0x431) [0x7f5d91b953b1]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_filemgmt.so(HADGDesignGraph::updateGraphDetail(bool, HDGUIStatus*, void (HADGDesignGraph::*)(bool, HDGUIStatus&))+0x5c7) [0x7f5d91b96e57]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_filemgmt.so(HADGDesignGraph::updateGraph(bool, HDGUIStatus*)+0x37) [0x7f5d91b975b7]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_filemgmt.so(HADGUtils::getAndUpdateDefaultGUIDesignGraph(HADAFileSet*, HDGUIStatus*)+0x23) [0x7f5d91c080d3]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_runs.so(HAXFPartitionUtils::populateCellInfo_(HPPartitionMgr*, std::vector<HPPartitionCellInfo, std::allocator<HPPartitionCellInfo> >&, HADAFileSet*)+0xfe) [0x7f5d8a3bbace]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_runs.so(HAXFPartitionUtils::getPartitionCellInfoForElab(HADAFileSet*, std::vector<HPPartitionCellInfo, std::allocator<HPPartitionCellInfo> >&)+0x29) [0x7f5d8a3bc249]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_runs.so(HAXFDataSpec::addSrcFiles()+0x23f) [0x7f5d8a39db9f]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_runs.so(HAXFDataSpec::init()+0x298) [0x7f5d8a39fea8]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_project.so(HAPRRealtimeInvoker::launch(HDGUIStatus&)+0x14) [0x7f5d8c777b14]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_project.so(HAPRProjUtils::openRodinElabNetlist(HAPRProject*, HAPRDesignSpec const&, HDARPart const*, HDGUIStatus&)+0x4d3) [0x7f5d8c747393]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_project.so(HAPRDesign::openNetlist_(HDGUIStatus&)+0x26d) [0x7f5d8c6dfe4d]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_project.so(HAPRDesign::openAndProcessNetlist_(HDGUIStatus&, bool, bool&)+0x177) [0x7f5d8c6e35b7]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_project.so(HAPRDesign::refreshDesign(HDGUIStatus&, bool)+0x240) [0x7f5d8c6e44f0]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_project.so(HAPRProject::openDesign_(HAPRDesignSpec const&, HDGUIStatus&, bool)+0x75) [0x7f5d8c772a95]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_project.so(HAPRProject::elaborate(HDARPart const*, HADAFileSet*, HADAFileSet*, std::string const&, bool, std::string const&, bool, bool, int, bool, bool, bool, bool, HDGUIStatus&)+0x14a) [0x7f5d8c77306a]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_vivadotasks.so(+0x3c60dd) [0x7f5d7e02a0dd]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_vivadotasks.so(+0x3cda2f) [0x7f5d7e031a2f]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_common.so(+0x5f8f37) [0x7f5db161af37]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x331f5) [0x7f5dac5461f5]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x34d6b) [0x7f5dac547d6b]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(Tcl_EvalEx+0x16) [0x7f5dac548276]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(Tcl_FSEvalFileEx+0x1d2) [0x7f5dac5acd02]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_commontasks.so(+0x2edfb2) [0x7f5da882bfb2]

/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_common.so(+0x5f8f37) [0x7f5db161af37]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x331f5) [0x7f5dac5461f5]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(Tcl_EvalObjv+0x32) [0x7f5dac5467e2]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(TclEvalObjEx+0x322) [0x7f5dac5485d2]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_commontasks.so(+0x30bef9) [0x7f5da8849ef9]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_commontasks.so(+0x304d43) [0x7f5da8842d43]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_common.so(+0x5f8f37) [0x7f5db161af37]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x331f5) [0x7f5dac5461f5]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(Tcl_EvalObjv+0x32) [0x7f5dac5467e2]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(TclEvalObjEx+0x322) [0x7f5dac5485d2]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_commonmain.so(+0x6430) [0x7f5db0e1d430]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(Tcl_Main+0x1d5) [0x7f5dac5b3175]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_common.so(+0x631d09) [0x7f5db1653d09]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7464) [0x7f5db0043464]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f5db064530d]

 

How to reproduce: run the build_top.sh in the attached archive (this is stock MiSoC). The mor1kx sources can be found at https://github.com/openrisc/mor1kx

 

Building MiSoC with the LM32 processor works fine.

 

The problem affects Vivado 2016.4 and does not affect Vivado 2016.2.

 

Also, please fix this forum's file attachment mechanism. Sending a .tar.bz2 results in "The attachment's vivado_crash.tar.bz2 content type (application/x-bzip) does not match its file extension and has been removed."

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Xilinx Employee
Xilinx Employee
6,868 Views
Registered: ‎01-24-2017

Re: Vivado crash when compiling mor1kx processor

Jump to solution

Hi, 

 

The crash is due to synth_design -top top -part xc7k325t-ffg900-2 -include_dirs {}. Remove -include_dirs {} its working fine.

There were few errors

  1. Missing  file mor1kx_bus_if_avalon.v, I commented it in top.tcl

  2.Missing  mor1kx_branch_pedictor_simple.v in top.tcl, which I have added in top.tcl

 

Correcting these Vivado didn't crash

 

 

 

 

View solution in original post

2 Replies
Highlighted
Xilinx Employee
Xilinx Employee
6,869 Views
Registered: ‎01-24-2017

Re: Vivado crash when compiling mor1kx processor

Jump to solution

Hi, 

 

The crash is due to synth_design -top top -part xc7k325t-ffg900-2 -include_dirs {}. Remove -include_dirs {} its working fine.

There were few errors

  1. Missing  file mor1kx_bus_if_avalon.v, I commented it in top.tcl

  2.Missing  mor1kx_branch_pedictor_simple.v in top.tcl, which I have added in top.tcl

 

Correcting these Vivado didn't crash

 

 

 

 

View solution in original post

Highlighted
3,636 Views
Registered: ‎01-19-2009

Re: Vivado crash when compiling mor1kx processor

Jump to solution

This works. Thanks!

0 Kudos