Skip to content

No driver and Memory corruption problem #378

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
qaarah opened this issue Aug 1, 2018 · 7 comments
Closed

No driver and Memory corruption problem #378

qaarah opened this issue Aug 1, 2018 · 7 comments

Comments

@qaarah
Copy link

qaarah commented Aug 1, 2018

Hi,
While working with an example, Reading the blif file generated by yosys using VPR, I get the memory corruption error "Net #1 (zro_zro) has no driver and will cause memory corruption." How to solve this problem?
VPR Version: VPR 7.0 Full Release, May 18, 2013
On Linux
Thanks

@kmurray
Copy link
Contributor

kmurray commented Aug 1, 2018

I'd suggest trying the latest version of VTR from the trunk.

We've substantially upgrade the robustness of the blif handling since the VTR 7.0 release, and I suspect the trunk would handle this with no issues.

@qaarah
Copy link
Author

qaarah commented Aug 1, 2018

Thanks @kmurray. I get the following error while installing VTR. though I am following the instructions from "https://github.com/verilog-to-routing/vtr-verilog-to-routing/blob/master/BUILDING.md"
$make
cd ./build && /usr/bin/cmake -DCMAKE_BUILD_TYPE=release -G 'Unix Makefiles' ..
-- CMAKE_BUILD_TYPE: release
CMake Error at CMakeLists.txt:63 (message):
Could not determine C++14 support for compiler /usr/bin/c++. C++14 support
is required.

-- Configuring incomplete, errors occurred!
See also "/home/qazi/Desktop/Qazi/tools/vtr-verilog-to-routing/build/CMakeFiles/CMakeOutput.log".
See also "/home/qazi/Desktop/Qazi/tools/vtr-verilog-to-routing/build/CMakeFiles/CMakeError.log".
Makefile:60: recipe for target 'build/Makefile' failed
make: *** [build/Makefile] Error 1

Thanks

@kmurray
Copy link
Contributor

kmurray commented Aug 1, 2018

That means your compiler doesn't have C++ 14 support which is required to build the latest VTR.

Compilers that should work are:

  • GCC >= 4.9
  • Clang >= 3.6

You should be able to install one of these with your Linux distribution's package manager.

@qaarah
Copy link
Author

qaarah commented Aug 2, 2018

Thanks, I am working on it to install. (One of them). I tried all the questions that are posted on different forums but after installation of GCC , my compiler could not be updated.

@kmurray
Copy link
Contributor

kmurray commented Aug 2, 2018

That sounds like a computer setup related issue, which is unrelated to VTR. I'd suggest checking your Linux Distro's documentation.

I'm going to close this issue for now. If you get things sorted out and still run into the no driver/memory corruption message with the latest VTR feel free to re-open it.

@kmurray kmurray closed this as completed Aug 2, 2018
@qaarah
Copy link
Author

qaarah commented Aug 3, 2018

Hi @kmurray .
I am tryinig to synthesize using new VTR. I am using the sample_arch.xml file and also tried the xml file of previous version but I get the following error.
"Found 1 'timing' child node(s) of 'device' (expected 0). has been replaced with the <switch_block> tag. Please upgrade your architecture file."
I have gone through the timing and <switch_block> but could not solve the problem.
Is there any special xml. for new versions?
Thanks for help.

@kmurray
Copy link
Contributor

kmurray commented Aug 7, 2018

It looks like you are using an out-of-date architecture file (perhaps a VTR7 architecture file with the latest trunk code?).

The architecture files which are included the the trunk code should all be up-to-date.

If you have your own architecture file which you need to upgrade then you can use the vtr_flow/scripts/upgrade_arch.py script. However I'd suggest starting out with one of the architecture files from the trunk first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants