jonzzzsat wrote
I downloaded the file again and it solved the problem. I have completed the test successfully, I am still a computer learner I must have altered something.
Glad that solved the problem. It's easy to accidentally change a file, so I keep a virgin download in a different directory that I can always pull clean copies from.
But in respect to the most efficient implementation the ideas I generated in my folly got me thinking about it nonetheless. Now I recall the most efficient chip is the one with the fewest parts.
Not necessarily. Also, it depends on what metric is being used to judge efficiency.
So in respect to the not chip - one Nand must be the most efficient?
Actually, no. In terms of the building blocks you have to work with, it's the best you can do. But in the real world you would prefer to use an actual Not gate. In CMOS, a Not gate consists of two transistors while a Nand gate consists of four.
If I found another way that passed the test does the Simulator install the most efficient? How does it decide?
The simulator simply uses whichever one you provide to it. If you don't have an implementation in the directory at all, then it uses its internal model which is nothing more than a Java function that implements the desired logic and has no concept of digital gates being connected.
But like you said, to connect all pins nonetheless. Is the compare file that is generated on testing - the interface chip truth table? It says unconnected output pins will default to 0 in the HDL survival guide under unconnected pins.
The HDL survival guide is not definitive and was not written by the authors. I've found a couple of errors in it. I don't know if Cadet1620 (who wrote it) looked at the source code to determine how unconnected pins are handled. I do know that the simulator behaves somewhat erratically with signals that are generated by not used.
Now this might be a silly question but I feel like playing around with the Hardware Simulator, but once I have implemented a chip it stores it in memory and I move on to the next at will?
It doesn't store implemented chips in memory. Every time you run the simulator it looks for the chip implementations in the working directory and, if it finds them, it uses them. Otherwise it uses the internal Java model.