D
David Brown
Guest
On 03/12/14 13:05, Rick C. Hodgin wrote:
Don't be so surprised - a basic understanding of digital logic is not
actually very difficult. I was about 12 or 13 when I learned about
boolean logic, registers, ALUs and processor design. If you are
comfortable with binary, logic operations, and assembly code (on any
cpu), then digital logic design is mostly pretty simple.
There is an "ah-ha!" moment for software programmers when they first
look at Verilog, VHDL, or other HDL's, when they realise you are mostly
describing a lot of things that happen in parallel, rather than mostly
describing a lot of things that happen serially, but you seem to have
passed that.
What is not simple, of course, is actually making something useful and
working - figuring out what you need, how to make appropriate
structures, how to manage everything, how to make the design efficient
in size and space, how to avoid races, how to fit together existing
pieces, etc. And even when you know what you are doing here, there is
massive amounts of work involved.
I am not trying to discourage you here - I am just saying that you
shouldn't think you have some "natural aptitude" here (nor am I saying
that you /don't/ have a natural aptitude - but if you do, it is not yet
apparent). You are a reasonably intelligent person, with good enough
mathematical skills and plenty of experience at assembly programming,
and lots of determination and motivation - I would have been very
surprised if you had /not/ got the hang of Verilog fairly quickly.
I have had long-term goals:
(1) Visual FreePro and its compiler framework
(2) Exodus 32-bit x86-based operating system
(3) Armodus 32-bit ARM-based OS.
(4) Exodus 64-bit.
(5) Armodus 64-bit
And various other related system and user apps.
I have only discovered in the last month that I
have some natural understanding of hardware.
Until this Oppie-1 project, I had always viewed
hardware as some distant and nebulous thing.
But now that I see I have this knowledge and
ability, much to my surprise I might add, I am
moving in this way.
It's absolutely floored me to be honest. When I
began to learn Verilog, and write things, and it
all made sense, I literally walked around my
house in disbelief saying out loud, "No way!"
Don't be so surprised - a basic understanding of digital logic is not
actually very difficult. I was about 12 or 13 when I learned about
boolean logic, registers, ALUs and processor design. If you are
comfortable with binary, logic operations, and assembly code (on any
cpu), then digital logic design is mostly pretty simple.
There is an "ah-ha!" moment for software programmers when they first
look at Verilog, VHDL, or other HDL's, when they realise you are mostly
describing a lot of things that happen in parallel, rather than mostly
describing a lot of things that happen serially, but you seem to have
passed that.
What is not simple, of course, is actually making something useful and
working - figuring out what you need, how to make appropriate
structures, how to manage everything, how to make the design efficient
in size and space, how to avoid races, how to fit together existing
pieces, etc. And even when you know what you are doing here, there is
massive amounts of work involved.
I am not trying to discourage you here - I am just saying that you
shouldn't think you have some "natural aptitude" here (nor am I saying
that you /don't/ have a natural aptitude - but if you do, it is not yet
apparent). You are a reasonably intelligent person, with good enough
mathematical skills and plenty of experience at assembly programming,
and lots of determination and motivation - I would have been very
surprised if you had /not/ got the hang of Verilog fairly quickly.
And in the weeks since I've looled at how the
various hardware interconnects, and it's like this
veil has been lifted and I can see the hardware
ends.
The path before me is now a combined path:
(1) LibSF 386-x40 comprised of
(2) Exodus OS,
(3) Visual FreePro, and its general IDE supporting a C-like compiler, and
(4) Other user apps
Best regards,
Ricl C. Hodgin