Aargh. (was Re: Now what?)

[Bartz, Jamison]

I think that I am on the other end of the spectrum.  I have a good 
knowledge of Microcontroller and Assembly, but I don't have the
knowledge of how to make it all useful.  I would like to help anyone
with programming stuff, but I don't know where to get the good data
from.  I am just now figuring out to decode and read the 160 baud ALDL
stream.  It isn't the electrical side of the problem that I am having, it
is the application of it.
In the same example as what Shannen wrote about, I am the one that knows
the technical manuals inside and out.  I could design and build a computer
to
accomplish anything you wanted it to.  I could have probably written the
manual.  The problem is, I don't know enough about the application and how
things are supposed to work together to accomplish something useful.
I know the basic overview of the system, but don't know the specifics
needed to apply what I know.
I took the 5-6 years to learn all about what you can put in those microns
of silicon.  I even know how to build one.  I now am working as a BIOS
Engineer for Compaq but have a very strong hardware background.  I would
like
to help anyone that wants to pick my brain.  Sorry to anyone that thinks I
am rambling on about nothing.  Shannen, if you would like me to try and
explain
something for you, let me know.  I just want to help where I can.

Jamison (Jamie) Bartz
BIOS Development Engineer
Compaq Computer Corporation 


-----Original Message-----
From: Shannen Durphey [mailto:shannen at grolen.com]
Sent: Wednesday, May 26, 1999 11:33 AM
To: gmecm at efi332.eng.ohio-state.edu
Subject: Aargh. (was Re: Now what?)


Mike Pitts wrote:

> You should read any Motorola MCU manual you can get your hands
> on.  The HC11 is my favorite.
> 
> -Mike

Read Motorola manual.... I've tried many times to do that.  Puts me to
sleep faster than a bad movie.  Can read, and only guess.  Where to go
to "do" after the "read" ?  
I'll explain this differently.  Let's say I've got a book that
provides technical details about pistons.  Trying to understand engine
operation from that book would be, at best, a chore.  So I run out and
buy something like Vizard's books, that talk about different types of
pistons, and rod ratios, and crankshaft materials, and ring types. 
I've got some pretty hefty notions, but still no idea of what to do to
overhaul my stocker, or even how to tell what's worn when I
dissasemble it.  But I see pictures of torque wrenches, and
micrometers, and other tools in the book.  Thinking I'm going to need
them, I run out and buy bunches of tools, maybe end up with an
inch-pound torque wrench, or a set of inside mics that only go to 2",
not really knowing what's going to work.  I still have made no
progress on getting the engine work done, but I've sure started a
collection of stuff.
I had to give myself a pat on the back the other day.  Someone asked
about using multiple proms, and I accurately predicted the answer
would involve the "chip enable".  I've seen that a few times.  After
that, I was lost.  Like many other times, I saved the posted answer
for a later day.

Someone, please, volunteer some clues for the guys that are doggedly
hanging in, watching for useful stuff.  Books, beginner's lists,
something.  I'm going to end up so durn frustrated that I go back to
school for 4 more years, just to learn to understand a small aspect of
what's inside a .5625 square inch piece of silicon.  
I've helped some guys on the list with some mechanical stuff that's
pretty basic.  It's not a problem for me.  I know that everyone has to
start somewhere.  Many mechanics feel that they've worked hard to
learn the tricks and tips they use, and they're not going to give them
out to anyone.  I see no reason to make everyone re-invent the wheel. 
I've chosen to learn much of what I know, and don't mind sharing,
especially with someone who wants to learn.  It's not going to cut my
throat to help a list member understand how to diagnose their own
driveability problems, or to tell the difference between an exhaust
rattle and a gear noise.

Some guys seem to treat this programming info like it's reserved for a
chosen few.  Generally, the people on this list are willing to help, I
think they just forget where some of us stand in the puddle of
knowledge.
Shannen
*doing the clue mating dance*