Industrial application for HC11

Can you suggest me some real application of MC68HC11 microcontroller?
I need to know notorius industrial products that have this microcontroller
(for example fuel injection, motor application,...)

Thanks

Frankie,

We did a pressure controller for a gas chromatograph.

This system held a pressure of .01 PSI over a range of 0 - 120PSI.

Motor control systems use HC11 for PID control.

I personally did my solar controller, controlling pumps where the 
temperature was set.

Many real world application exist.

If you got to the Motorola web site I am sure you will find applications
in the automotive field.


Also other small processors are used in the automotive area.

Google is your friend.


Frankie wrote:
> Can you suggest me some real application of MC68HC11 microcontroller?
> I need to know notorius industrial products that have this microcontroller
> (for example fuel injection, motor application,...)
> 
> Thanks
> 
> 

On 2 Nov 2004 18:35:07 +0100, "Frankie" <goes@to.holliwood> wrote:
>Can you suggest me some real application of MC68HC11 microcontroller?
>I need to know notorius industrial products that have this microcontroller
>(for example fuel injection, motor application,...)

I have used them in networking/telecom products (ethernet & token ring
adapters, etc.) and as auxiliary processors in robotics equipment
(controlling stepper motors, lights, pneumatic valves, etc.)


Roberto Waltman

[Please reply to the group. The
 reply-to address is invalid]

Built remote energy control systems for midsized plants( 10-125,000 sq.ft.)

Also solar heating control systems for pools

Jay Miller
Temtronic Designs Inc.

"Frankie" <goes@to.holliwood> wrote in message
news:4187c54b$2@x-privat.org...
> Can you suggest me some real application of MC68HC11 microcontroller?
> I need to know notorius industrial products that have this microcontroller
> (for example fuel injection, motor application,...)
>
> Thanks
>
I recently opened up the ECU box in my car, I didn't intially recognise the
cpu as it has an 'SC' part number. When I removed
the eprom and read it I recognised 68HC11 code.

The ECU ia made by Nippon-Denso for my 1992 Mazda MS-6 car,
the cpu has some extra hardware, hence the SC designation, meaning
'semi-custom'. The rom is jam-packed with highly optimised code written in
assembly language, it has a lot of work to do yet only runs with 2MHz
internal clock. Extra support is provided by a 6821 PIA and a 6840 Timer
chip.

I have tried to get info on the whole unit but its now to old, Motorola
does not release info on SC parts, and Denso does not release any
technical info on its products, but hey - life wasn't meant to be easy!!

"Frankie" <goes@to.holliwood> wrote in message
news:4187c54b$2@x-privat.org...
> Can you suggest me some real application of MC68HC11 microcontroller?
> I need to know notorius industrial products that have this microcontroller
> (for example fuel injection, motor application,...)
>
> Thanks
>
>

I put about 2 dozen of them in a balloon and filled it with clear epoxy..
shaped a "flat" for the base and used it as a paper weight.. !

John Dyer wrote:

> "Frankie" <goes@to.holliwood> wrote in message
> news:4187c54b$2@x-privat.org...
>> Can you suggest me some real application of MC68HC11 microcontroller?
>> I need to know notorius industrial products that have this
>> microcontroller (for example fuel injection, motor application,...)
>>
>> Thanks
>>
> I recently opened up the ECU box in my car, I didn't intially recognise
> the cpu as it has an 'SC' part number. When I removed
> the eprom and read it I recognised 68HC11 code.
> 
> The ECU ia made by Nippon-Denso for my 1992 Mazda MS-6 car,
> the cpu has some extra hardware, hence the SC designation, meaning
> 'semi-custom'. The rom is jam-packed with highly optimised code written in
> assembly language, it has a lot of work to do yet only runs with 2MHz
> internal clock. Extra support is provided by a 6821 PIA and a 6840 Timer
> chip.
> 
> I have tried to get info on the whole unit but its now to old, Motorola
> does not release info on SC parts, and Denso does not release any
> technical info on its products, but hey - life wasn't meant to be easy!!

The fact that you have already opened the box (and probably due to its age) 
will definitely have invalidated any warrantry you had on that unit. So, if 
you are so inclined to find out more, start reverse engineering the unit. 
You may get to figure out what they added.

As to the level of work the processor does, it may not need to be that 
great a load especially if the added hardware bits do most of the grunt 
work with the parameters being updated once in a while.

You probably won't put this unit back on your car (might be too much of a 
death wish).

-- 
********************************************************************
Paul E. Bennett ....................<email://peb@a...>
Forth based HIDECS Consultancy .....<http://www.amleth.demon.co.uk/>
Mob: +44 (0)7811-639972 .........NOW AVAILABLE:- HIDECS COURSE......
Tel: +44 (0)1235-811095 .... see http://www.feabhas.com for details.
Going Forth Safely ..... EBA. www.electric-boat-association.org.uk..
********************************************************************

"Paul E. Bennett" <peb@amleth.demon.co.uk> wrote in message
news:cmbb8j$j58$1$8300dec7@news.demon.co.uk...
> John Dyer wrote:
>
> > "Frankie" <goes@to.holliwood> wrote in message
> > news:4187c54b$2@x-privat.org...
> >> Can you suggest me some real application of MC68HC11 microcontroller?
> >> I need to know notorius industrial products that have this
> >> microcontroller (for example fuel injection, motor application,...)
> >>
> >> Thanks
> >>
> > I recently opened up the ECU box in my car, I didn't intially recognise
> > the cpu as it has an 'SC' part number. When I removed
> > the eprom and read it I recognised 68HC11 code.
> >
> > The ECU ia made by Nippon-Denso for my 1992 Mazda MS-6 car,
> > the cpu has some extra hardware, hence the SC designation, meaning
> > 'semi-custom'. The rom is jam-packed with highly optimised code written
in
> > assembly language, it has a lot of work to do yet only runs with 2MHz
> > internal clock. Extra support is provided by a 6821 PIA and a 6840 Timer
> > chip.
> >
> > I have tried to get info on the whole unit but its now to old, Motorola
> > does not release info on SC parts, and Denso does not release any
> > technical info on its products, but hey - life wasn't meant to be easy!!
>
> The fact that you have already opened the box (and probably due to its
age)
> will definitely have invalidated any warrantry you had on that unit. So,
if
> you are so inclined to find out more, start reverse engineering the unit.
> You may get to figure out what they added.
>
> As to the level of work the processor does, it may not need to be that
> great a load especially if the added hardware bits do most of the grunt
> work with the parameters being updated once in a while.
>
> You probably won't put this unit back on your car (might be too much of a
> death wish).
>

Actually, I went to the local wreckers yard and got another ECU of the same
type to pull apart, I sure don't want be without my car if anything should
happen!!!!

I have disassembled the rom to give me an assembly language file that I can
re-assemble correctly with a 6811 assembler, but if you know anything about
disassembly, you will know that this is a long way short of getting an
understanding
of whats going on.

The next step is to work out the schematic diagram so I can see what is
connected
to what, buts its difficult as there are so many custom chips, I believe
these chips
are only surge supressors, but as they have custom Denso numbers, I can't
get any
info on them.
The cpu has extra addresses above the normal end of the 68hc11 internal port
space so there are obviously additional hardware features in the chip, and
since
I can't get a pin-out or info on the SC part, it all looks a tad to
difficult.

If you have any suggestions that might help I would be pretty pleased!!!

Thanks,
John

John Dyer wrote:

> Actually, I went to the local wreckers yard and got another ECU of the
> same type to pull apart, I sure don't want be without my car if anything
> should happen!!!!

That was sensible of you. :>
 
> I have disassembled the rom to give me an assembly language file that I
> can re-assemble correctly with a 6811 assembler, but if you know anything
> about disassembly, you will know that this is a long way short of getting
> an understanding
> of whats going on.

At least that is the simpler part of the work done.

> The next step is to work out the schematic diagram so I can see what is
> connected
> to what, buts its difficult as there are so many custom chips, I believe
> these chips
> are only surge supressors, but as they have custom Denso numbers, I can't
> get any
> info on them.
> The cpu has extra addresses above the normal end of the 68hc11 internal
> port space so there are obviously additional hardware features in the
> chip, and since
> I can't get a pin-out or info on the SC part, it all looks a tad to
> difficult.
> 
> If you have any suggestions that might help I would be pretty pleased!!!

A couple of useful devices are a signal injector and a current trace probe. 
Using these two together will allow you to clearly identify any tracks on 
the PCB and their connectivity to other devices, no matter what they are.
A logic probe will also be quite usefule, especially if it is able to work 
with any of the logic families. The very hard part is trying to work out 
what all those black shiny impenatrable boxes are doing. I might suggest 
that you should perhaps pick up yet another spare one that you can 
dismantle to check out the individual hardware items for response 
characteristics once you gain some idea of how they are connected 
(identifying power supplies etc).

As for the assembly code, begin by trying to identify the blocking 
structure of the code. ie:- use a highlighter pen to show where bits of 
sub-routines begin and end. Be prepared to have several goes at this bit as 
you will not necessarily get it right tghe first time through. This can 
probably bnest be accomplished from following the reset vector jumps and 
walking through the code bit by bit. 

You could also Highlight the JMP, JSR and RTS codes (I hope that is 
correctly remembered for the family). Then make sure each one is really 
what it purports to be and not data fields.

-- 
********************************************************************
Paul E. Bennett ....................<email://peb@a...>
Forth based HIDECS Consultancy .....<http://www.amleth.demon.co.uk/>
Mob: +44 (0)7811-639972 .........NOW AVAILABLE:- HIDECS COURSE......
Tel: +44 (0)1235-811095 .... see http://www.feabhas.com for details.
Going Forth Safely ..... EBA. www.electric-boat-association.org.uk..
********************************************************************

"Paul E. Bennett" <peb@amleth.demon.co.uk> writes:

> As for the assembly code, begin by trying to identify the blocking 
> structure of the code. ie:- use a highlighter pen to show where bits of 
> sub-routines begin and end. Be prepared to have several goes at this bit as 
> you will not necessarily get it right tghe first time through. This can 
> probably bnest be accomplished from following the reset vector jumps and 
> walking through the code bit by bit. 

You can automate this to a very high degree by building
a symbol table and noting which addresses are referenced
by JSR/BSR (procedures) and which are referenced by the
other instructions (data).  Data areas greater than two
bytes on the 68XX family tend to be character string
constants and can be tested for content to distinguish
between that and address constants with a high degree of
success.  [There won't be much character string data in
an ECU.]