search

rasmusto / vtr-verilog-to-routing

Automatically exported from code.google.com/p/vtr-verilog-to-routing
0 stars 0 forks source link

VPR fails with "Error: in check_node: node XX has no edges." #56

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. I used the architecture arch/timing/soft_fpu_arch_timing.xml, that comes 
with the package. Benchmark is my own test circuit, which is a 4bit counter 
using only soft logic.

2. Since the run_vtr_flow script seems to fail with architectures that do not 
have any memory blocks, I added the memory definition from 
arch/timing/k6_N10_memDepth16384_memData64_40nm.xml (copy&paste)

3. Flow scripts were not changed.

What is the expected output? What do you see instead?
Flow fails. vpr prints this message:
"Error: in check_node: node 87 has no edges."
Please find attached the task folder including the run.

What version of the product are you using? On what operating system?
VTR release 1.0 (compiled for graphic output)
Ubuntu 12.04 32-bit

Please provide any additional information below.
I'm currently evaluating vtr for possible use within my company's research 
division. It would be great, if you could look into this issue, because the 
framework is actually pretty cool. However, error messages should be more 
verbose to enable users to fix problems in their architecture.

Regards,
Daniel Drescher

Original issue reported on code.google.com by daniel.d...@de.bosch.com on 24 Jan 2013 at 8:01

Attachments:

GoogleCodeExporter commented 9 years ago 
Hello Daniel,

Thank you for your interest in our tool.  We agree that good error messages are 
important and so we have been doing active development improving that in VTR.  
If you use the latest trunk code for VTR, you'll find much more informative 
error reporting.  Alternatively, you can wait for our next release which we 
hope will be out mid-February.

The problem that you've encountered, "Error: in check_node: node 87 has no 
edges.", is resolved in the trunk.  More details below:

VPR had strict internal checks.  If there is a bug and the internal check 
detects it, then VPR will throw an error instead of producing an invalid 
answer.  For your case, that particular internal check was unnecessarily 
strict.  We have since relaxed it.

Original comment by JasonKai...@gmail.com on 24 Jan 2013 at 9:22