The 68HC08 (HC08 in short) is a broad family of 8-bit microcontrollers from Freescale Semiconductor (formerly Motorola Semiconductor). HC08’s are fully. NXP 68HC08 are available at Mouser Electronics. Mouser offers inventory, pricing, & datasheets for NXP 68HC 68HC08 Datasheet, 68HC08 PDF, 68HC08 Data sheet, 68HC08 manual, 68HC08 pdf, 68HC08, datenblatt, Electronics 68HC08, alldatasheet, free, datasheet.

Author: Goltirisar Zulkibei
Country: Monaco
Language: English (Spanish)
Genre: Science
Published (Last): 5 December 2005
Pages: 382
PDF File Size: 12.77 Mb
ePub File Size: 10.33 Mb
ISBN: 744-1-25548-500-6
Downloads: 86378
Price: Free* [*Free Regsitration Required]
Uploader: Zulugul

Spare Time Labs 2. This page has gone through several rewrites, mainly to get rid of my ‘rant mode’ writing, but it seems I just need to write it out of myself.

Feel free to skip the first part. For references purposes and convenience I’ve put all the useful links here at the top of the page: Having said that I realize that a table contents is handy, especially if later on you want to come back and look for something. Besides it allows you to skip the rant part and get down to the brass task, starting at ‘Building the Hardware’.

68HC08 Datasheet, PDF – Alldatasheet

This page is aimed at beginners in microcontrollers. While a microcontroller project may not be suitable as a first project in electronics I hope to show that it is not that difficult either. The controller here can be put together and the development environment set up in a few evenings and for less than 15 USD, if you have the basic infrastructure, a personal computer and tools, in place.

Lots of people are interested in microcontrollers, as witnessed by the countless number of hobby pages in the net.

If you are new to this hobby it might make sense to pause for a moment and think about why you want to get involved. Motivation always concerns me a lot, in more than one sense of the word. While I’m 688hc08 always forthcoming with my own motivations, at least I try 688hc08 be honest with myself. A lot of people datashert cite that they want to learn to ‘do datassheet or ‘learn a new programming language’. These are as good reasons as any, but I suspect that behind these statements there are dreams or ambitions that aim further.

Search within yourself and find out what makes you tick. So before I get to the actual technical substance, let me do some soul datxsheet here with you, maybe it will provoke some thoughts that will help you to make up your mind. Why microcontrollers I spend about two hours every day commuting and no sooner than I’ve started the car my thoughts start to wonder and I get these ideas.

Hey, it would be cool to monitor the electric consumption of the house, just measure the pulse train on the meter, or how about creating that CNC rooter I’ve always dreamed of and I could build an induction furnace or how about a levitation device What is common to these pipe dreams is that most of these would be best implemented with a microcontroller. A microcontroller is a sort mini computer 668hc08 a central processing unit or CPU, some memory and some peripherals or input output devices.

Let’s face it, analog circuits and logic chips are just not the way to go today. A microcontroller can vatasheet pulses and frequencies, measure signals, do math, do logic and control them in a wonderfully precise and repeatable way. No tolerances to worry about, no trimming to do, no need for special measuring devices.

Everything is going digital and that is the way it should be. It just makes sense. Taking the long term view I’m a datsaheet programmer involved in designing embedded systems on a daily basis for the past quarter of a century, almost as long as they’ve existed. I also enjoy tinkering with these things in my spare time. Now how twisted is that! With this schizophrenic mind set I cannot dattasheet bringing some of my professional baggage to my spare time activities although the motivations, goals, requirements and resources of professionals 68nc08 hobbyist differ considerably.

Having fun with HC08

Learning new stuff, like microcontrollers, is fun, but it’s also an investment. An investment in yourself and your future. Like any investment it requires spending one thing to gain another. Money is a secondary consideration; anyone can be rich, 68hc088 no-one lives forever so we all must carefully consider what we do with our time. As with any investment, it is natural to expect from it something in return, datasueet it in the form of skills, opportunities, gratification or just sheer fun.


So what has all this got to do with microcontrollers? Learning to ‘do’ microcontrollers is a big investment in terms of spending precious spare time. Nobody wants to see their investement go bust so it pays to invest carefully. Concerns include, “what if the chip I’m using gets discontinued,” “what if the tools I’m using get discontinued,” “am I going to be left in a niche where other users are few and far between.

I’ll bet you anything that the guys writing Unix code more than fourty years ago had no idea that a lot of this code would still be running and tooted as the most advanced operating system available today: I’ve found playing with microcontrollers both rewarding and fun, and it has even paid my mortage, but surely it also has swallowed a big chunk of my life. Ok, so let’s see where this sort of thinking has lead me and why.

I’m not putting this forward as the only right way of going about it, I’m just sharing my point of view. 68h08 and revisions of my opinions are encouraged. If you’re still reading, remember, that it sometimes pays off to listen to others who’ve ‘been-there-done-that’, but you should also study yourself and find out what it is that you really want to do. It is your project and your life. Looking for a microcontroller For years I’ve been looking for a suitable microcontroller that would fulfil my self-imposed constraints.

In the past, me and my friends have had great fun building things from the 68HC11 family of devices, but, although a very nice device, it leaves something to be desired when compared to more modern offerings with internal Flash and whatnot.

Here is my list requirements for a microcontroller: C-programmable DIL package USB Single chip Minimal in-circuit programming adapter Minimal external parts Free dxtasheet Simple, Elegant Interestingly, this list is always almost the same regardless of what I am contemplating to do with it, pretty much like my cooking datashete first I take a pound of butter, bowl of sugar, a pint of creamhalf a dozen xatasheet and then I start to think what to cook and eat!

In the following, I’ll discuss these to give a beginner one point of view on the matter. Please note that there are many views on datasheett, none, including mine, of which are necessarily absolutely correct. In the following I’ll discuss my views on each of the above-listed requirements to some length.

C-programmable Programming is at the very heart of microcontrollers – it is what makes them tick, and it is what makes them so universally applicable to various task.

Those people at the silicon foundry who crank out these chips for us don’t know or care what we do with them. And they don’t have to, that is the beauty of it, because we as programmers put in the soul, the program, that dictates what it does. So the parts can be manufactured in millions, datashdet the cost down. But those darn chips only understand and obey voltage levels in their memory 68ch08 and while it sometimes is necessary and strangely satisfying specifying those voltages with ones and zeros, it surely is not the way to go on a larger scale.

So we need something higher level that allows us to think in more abstract terms than boolean logic and flip flops which are the building blocks of microcontrollers. We need a programming language. Now there is something about programming languages that makes people foam in the mouth. Don’t know what it is, but there surely is something fascinating about them and everyone seems to have very definite opinions about them. Lots of the argumentation and discussion on programming languages seems to center around technical characteristics or philosophical issues about why one programming language is better than another.

While there certainly are differences and one can put forward well-founded arguments for various aspects of different languages, I find that this sort discussion is centered around the wrong questions. The question is not about which programming language is the best, but rather which one you should use and thus learn. All the programming languages are pretty much the same.


How could they be different, seeing that the computing architecture is always pretty much the same old Von Neumann and the problems are always the same, control flow, data representation, computation and storage management.

Make a decision on those, throw in a syntax darasheet, hey presto, we have a programming language! Of course, there are some differences and some languages are better than others, but the essential difficulties of programming are not likely to be solved with one programming language, any programming language, anytime soon! So how do you go about choosing a programming 68hc80 To me it the choice is obvious: I know datasueet old joke about flies and cow pat, but when something is popular there has got to be something good about it.

And there is safety in numbers, bringing me to my pet long term view theme. When there is a large user base you get: As often in life, it pays to take the middle road.

Yes, it is a vicious circle 68hc008 ties us to design decisions done decades ago but datsaheet is no escaping the past if you have the future in mind. Now isn’t that ironic! And the lucky winner is C C has never been datasbeet favorite programming language yet both professionally and hobby-wise it is the only choice I can think of when talking about small microcontrollers.

The tools and the language are mature and standardized, even the C99 standard is ten years old next year. Datasheer hey, lots of people use BASIC 68hc008 some improved C-like language to program microcontrollers, 68uc08 that makes sense? BASIC has a special place in my heart, it was the first datashret I learned and it still has certain appeal in its simplicity and ease of learning.

However, I would never consider using it for anything real. Well, that is not quite true; only some weeks ago I was well on my way to write a BASIC compiler for HC08, I had the linker and assembler ready, and the compiler ticking, but fortunately I came to my senses before I wasted any more time on it.

The original Dartmouth BASIC born in like me was a very simple language that contained all the basic building blocks that you need in a programming language, but lacked the basic higher level abstraction features that I think are essential, like named subroutines, local variables and parameter datassheet, and structural datashwet statements, without which programming is rather similar to assembler programming, making it difficult to manage anything complex successfully.

Of course, later variants of BASIC added these features, only so many of them went their own way, so they are all the same, only different!

With C the people who can? And this need to tweak is not an ‘if’, it’s a ‘when’! Talking about proprietary products versus standard languages: Companies come and go, they are bought, sold and merged, datsaheet discontinued and killed off. So, personally, I would never invest programming in a language that does not have an exceptionally high likelihood of survival.

About Spare Time Labs

The same happened to a friend on the PC version. I go as far as making the language and tools affect the choice of the chip. If a chip is not supported by Gnu C it is a definite minus point. If it can’t be programmed in C it is a non starter. No chip is so great that it makes sense to invest on re-learning a new programming language when the competition is bound to offer something that can be programmed with C.

Before I close up this rather long and most likely boring section on programming languages, I can’t help mentioning the project Arduino. Everyone interested in getting into microcontrollers should check it out. Although I think the idea of having yet another IDE and adding some sort of automatic preprocessor on top C does not really make sense to me, the project has a lot to offer.

DIL package In professional circles, surface mount devices are not only a fact of life but a desirable characteristic.