I created Mux4Way.hdl and Mux8Way.hdl, was that not the right way?

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

I created Mux4Way.hdl and Mux8Way.hdl, was that not the right way?

Ludovic
When I came across the Mux4Way16, I felt it would be great to already have a Mux4Way boolean to begin with, so I went ahead and did that.

Was that supposed to happen at all ? the course doesn't seem to indicate anything in that regard.
Reply | Threaded
Open this post in threaded view
|

Re: I created Mux4Way.hdl and Mux8Way.hdl, was that not the right way?

cadet1620
Administrator
For this course there isn't really a right or wrong way to build your chips. What's important is to develop something that works. The book only directs you to build chips that you will need later on in the course. There is no reason that you can't build "helper" chips along the way.

One of the goals of the course is to learn abstraction. From that point of view, using 3 Mux16s to make Mux4Way16 instead of 16 Mux4Ways is better and will also lead the way to using Mux16 and Mux4Way16 to build Mux8Way16.

If you have time, after you complete the hardware section you might want to revisit what you've done and use your experience to clean things up a bit.

--Mark
Reply | Threaded
Open this post in threaded view
|

Re: I created Mux4Way.hdl and Mux8Way.hdl, was that not the right way?

Ludovic
Actually I'm going to go clean that up right now, although I'm in the next section now.
Reply | Threaded
Open this post in threaded view
|

Re: I created Mux4Way.hdl and Mux8Way.hdl, was that not the right way?

Ludovic
As expected, it was much easier.
It would be nice if there was at least one mention of how well each chip can be optimized, like some can be done in 4 primitives, or with as little as 2 abstractions, etc.