RE: Recent dialog and old initiatives
- To: "Simon, Mike HS-SNS" <mike.simon@xxxxxxxxxx>
- Subject: RE: Recent dialog and old initiatives
- From: "M. Simon" <msimon@xxxxxxx>
- Date: Sat, 04 Nov 2000 04:50:24 +0000
- Cc: "'Ben Franchuk <bfranchuk@xxxxxxxxxxxx>'" <IMCEAGWISE-SNDSGW+2EGWIA55+2E+22bfranchuk+40jetnet+2Eab+2Eca+22@xxxxxxxxxxxxxxxxxxxx>, "SMTP:MISC@xxxxxxxxxxxxxxxxxxxx" <MISC>
- In-Reply-To: <B9AC92FDD225D4119B4200508B6608F80105361F@HSMX52NT.rkd.snds.com>
I wanted:
a: to understand How the alu worked
b: understand how to simplify or change it.
So I did it in schematic form.
Of course being a hardware engineer I love schematics.
I'm doing all my designs in schematic and schematic macro form except
for the instruction decoder which I'm doing as a PLD type equation.
It forces me to keep things simple and really think through a problem and
the paths
and data flows. Important in the smaller FPGAs.
But I'm bound to try VHDL some day if they ever get a version that isn't C
ugly.
Or I get a paying customer.
Simon
>At the moment using a 74382 alu macro is a simpler than figuring out the
>VHDL code for a ALU.Once I get a working schematic version then I will
>rewrite for a high level language.
>
>========================================
>
>You might want to check out the ALU schematics found in old
>TTL books if you need ALU implimentation details.
>
>M. Simon