Failure at line 5 And.hdl

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Failure at line 5 And.hdl

Elimotley


I can't understand what's wrong, I red an old topic about the same problem, but I can't understand, can you help me please?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Failure at line 5 And.hdl

cadet1620
Administrator
With a=1 and b=1, nand should be 0, but it appears to be 1 in your screen shot.

Is there a Nand.hdl in the directory that contains this And.hdl?  There should not be.

If you select the Nand in the HDL panel, what does it show for Nand's I/O pins?

--Mark
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Failure at line 5 And.hdl

Mgpuentes
I'm getting the same error and I don't have Nand.hdl in the same folder.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Failure at line 5 And.hdl

cadet1620
Administrator
Comparison failure at line 5
This is the first (and only) test line that requires out = 1.

The most common cause of this error is that there is nothing connected to the And chip's out pin. Output pins that are not connected to anything default to 0.

A second common problem is that you have not yet written and tested Not.hdl. The skeleton files have no implementation so they have nothing connected to their out pins. Therefore unimplemented parts always have 0 for their output values.

A less common problem is that you are running the And.tst script from a different directory than where you have your And.hdl. If you have made a working directory for your parts, be sure to copy the .tst and .cmp files into the working directory and run the .tst file from there.

If you have "out=out" in your And.hdl and have a tested Not.hdl in the same directory as your And.hdl, post your And.hdl so we can look at it. The source code can be removed from your post after finding the problem.

--Mark
Loading...