Mike Phillips wrote: > Mike,
>
> We just aren't communicating, but we are on the same page. I have
> always known that we probably had to program off of the main board. So
> no, it's not rejected at all.
>
> I don't know how to program a 27C256. So I'll try and find the
diagram
> you mentioned and see what I see. I was thinking I need to make a board
> with a plcc84 socket and a db9 connector for the laptop for just this
> part.
>
Something occurs to me. You need to program the EEPROM on that
chip, as well, do you not? Well, the pins you have available to
you on the connector do not include the SCI. You have, IIRC,
So, you are going to have to come up with a minimal circuit
to boot that guy and talk to it in order to burn EEPROM.
That means that trying to use the EPROM Emulation Mode
for programming the EPROM would be extra effort.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
Reply by BobG...@aol.com●August 16, 20062006-08-16
Mike McCarty wrote: > The K series processor has special purpose PWM
hardware, which is
> presumably used to control fuel injectors in this application. Does the Err, sorry, not "fuel injectors", but the speed of the motor(s)
driving
the wheels.
Sheesh! I can't believe I wrote that!
========================================================Well, in an EV the PWM
controller sort of 'injects' pulses of DC into the motor, so I'll
go with it....
but you are right... the tech arts boards have hc11 d0 and e0 cpus.... no K
models that I recall...
________________________________________________________________________
Check out AOL.com today. Breaking news, video search, pictures, email and IM.
All on demand. Always Free.
Reply by Mike McCarty●August 16, 20062006-08-16
Mike McCarty wrote: > The K series processor has special purpose PWM
hardware, which is
> presumably used to control fuel injectors in this application. Does the
Err, sorry, not "fuel injectors", but the speed of the motor(s) driving
the wheels.
Sheesh! I can't believe I wrote that!
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
Reply by David Kelly●August 16, 20062006-08-16
On Wed, Aug 16, 2006 at 12:04:14PM -0700, Mike Phillips wrote: >
> I have the S19 file. Not sure if that's rom or source code.
[Deleted 118 lines below top-post]
A .s19 file is an image ready to be loaded in MPU, memory, or whatever.
S19 is the "binary" format which is traditional for Motorola/Freescale.
Is not really binary but hex ascii with additional address information
so that the loader knows where to put things.
--
David Kelly N4HHE, d...@HiWAAY.net
=======================================================================Whom
computers would destroy, they must first drive mad.
Reply by Mike McCarty●August 16, 20062006-08-16
B...@aol.com wrote: > Maybe a good plan B is just give up on the OTP HC711s
and make a
> little adapter board to go from the PLCC socket to a tech arts
> microstamp 20 pin header. Those have flash rom on them and can be
> programmed from a serial port. You only have the rom image, not the
> source code, correct?
It's not necessary for everyone to keep quoting the entire thread
every time he replies.
The K series processor has special purpose PWM hardware, which is
presumably used to control fuel injectors in this application. Does the
microstamp have a version with the K series proc on it? If not, then
I trow this is not a real solution.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
Reply by Mike McCarty●August 16, 20062006-08-16
Mike Phillips wrote: > I have the S19 file. Not sure if that's rom or
source code.
S19 is an object file format, so it's unlikely to contain
the source code. One *could* do that, but it's unlikely.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
Reply by Mike Phillips●August 16, 20062006-08-16
I have the S19 file. Not sure if that's rom or source code.
Mike
--- B...@aol.com wrote:
> Maybe a good plan B is just give up on the OTP HC711s
and make a
> little adapter board to go from the PLCC socket to a tech arts
> microstamp 20 pin header. Those have flash rom on them and can be
> programmed from a serial port. You only have the rom image, not the
> source code, correct?
>
>
>
> -----Original Message-----
> From: m...@yahoo.com
> To: m...
> Sent: Wed, 16 Aug 2006 11:54 AM
> Subject: [m68HC11] Re: HC711 pinout
>
> Holy Cow Mike!
>
> Some of these HC11 pdf files are hundreds of pages of Greek!!!!
>
> I came to this group looking for help. Clearly, I'm not a processor
> guy. Never claimed to be. What I'm telling you is what little info I
> was given. You are too close to this skill to see what I see. I don't
> understand much of it. So I have to rely on you and others to take
> what I say and translate it into your own lingo. If it's that
> annoying
> just tell me. I'll bug out of here. But this is a real need by a
> whole
> group of people who have spent thousands buying these vehicles not
> knowing about the poor R & D testing that the manufacturer did. So
> here I am, an R & D guy, busting my butt every free hour I have to
> keep more of these boards from dying and resurrecting the ones that
> have died.
>
> 1) There is an app note with a schematic in it for allowing the
> processor to be accessed in at least 2 ways. I may have even seen it.
> I can fab my own board from this schematic.
>
> 2) There is some brand of software out there that will allow me to
> burn code into my processor and fix the constants when they get
> screwed up. Constant is what the mfr calls it. I need this groups
> input on which software app to buy.
>
> These are the 2 things I need. If I'm stil welcome here, then I want
> help finding these 2 items.
>
> Mike
>
> >
> > May I make a suggestion? I suggest that you read the section on
> > programming the EPROM in that PDF file at the URL I gave you.
> > After you read that, then you can ask intelligent questions, and
> > won't be relying on a fuzzy memory of a vague statement which
> > you may have heard from someone who saw someone else use the
> > chip.
> >
> > At the very least, you should be able to know what it is that
> > you don't know, and have some vocabulary to talk about it.
> >
> > Mike
> > --
> > p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
> > This message made from 100% recycled bits.
> > You have found the bank of Larn.
> > I can explain it for you, but I can't understand it for you.
> > I speak only for myself, and I am unanimous in that!
> >
>
>
Reply by BobG...@aol.com●August 16, 20062006-08-16
Maybe a good plan B is just give up on the OTP HC711s and make a little adapter
board to go from the PLCC socket to a tech arts microstamp 20 pin header. Those
have flash rom on them and can be programmed from a serial port. You only have
the rom image, not the source code, correct?
-----Original Message-----
From: m...@yahoo.com
To: m...
Sent: Wed, 16 Aug 2006 11:54 AM
Subject: [m68HC11] Re: HC711 pinout
Holy Cow Mike!
Some of these HC11 pdf files are hundreds of pages of Greek!!!!
I came to this group looking for help. Clearly, I'm not a processor
guy. Never claimed to be. What I'm telling you is what little info I
was given. You are too close to this skill to see what I see. I don't
understand much of it. So I have to rely on you and others to take
what I say and translate it into your own lingo. If it's that annoying
just tell me. I'll bug out of here. But this is a real need by a whole
group of people who have spent thousands buying these vehicles not
knowing about the poor R & D testing that the manufacturer did. So
here I am, an R & D guy, busting my butt every free hour I have to
keep more of these boards from dying and resurrecting the ones that
have died.
1) There is an app note with a schematic in it for allowing the
processor to be accessed in at least 2 ways. I may have even seen it.
I can fab my own board from this schematic.
2) There is some brand of software out there that will allow me to
burn code into my processor and fix the constants when they get
screwed up. Constant is what the mfr calls it. I need this groups
input on which software app to buy.
These are the 2 things I need. If I'm stil welcome here, then I want
help finding these 2 items.
Mike
>
> May I make a suggestion? I suggest that you read the section on
> programming the EPROM in that PDF file at the URL I gave you.
> After you read that, then you can ask intelligent questions, and
> won't be relying on a fuzzy memory of a vague statement which
> you may have heard from someone who saw someone else use the
> chip.
>
> At the very least, you should be able to know what it is that
> you don't know, and have some vocabulary to talk about it.
>
> Mike
> --
> p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
> This message made from 100% recycled bits.
> You have found the bank of Larn.
> I can explain it for you, but I can't understand it for you.
> I speak only for myself, and I am unanimous in that!
>
Reply by Mike McCarty●August 16, 20062006-08-16
Mike Phillips wrote: > Holy Cow Mike!
>
> Some of these HC11 pdf files are hundreds of pages of Greek!!!!
Well, perhaps hundreds of pages of Geek :-)
I suggested that you read (3) three (3) pages. Three.
> I came to this group looking for help. Clearly,
I'm not a processor
> guy. Never claimed to be. What I'm telling you is what little info I
Fine, you're not uController proficient. But you are not using all
the info you've been given.
> was given. You are too close to this skill to see
what I see. I don't
> understand much of it. So I have to rely on you and others to take
> what I say and translate it into your own lingo. If it's that annoying
> just tell me. I'll bug out of here. But this is a real need by a whole
No, that's not annoying. What's annoying is having suggestions
rejected,
then hearing complaints about not getting help. I'm very familiar with
the MC68HC11 processors. I'm not expert with the K family specific
features. I've never programmed an OTP part like this, either.
> group of people who have spent thousands buying these
vehicles not
> knowing about the poor R & D testing that the manufacturer did. So
> here I am, an R & D guy, busting my butt every free hour I have to
> keep more of these boards from dying and resurrecting the ones that
> have died.
Ok, fair enough. You are a nice guy.
But itt's *your* problem, and not mine. I'm willing
to help. But you have to pull your own weight. Otherwise, why not
just ask someone else to do all the work for you as a charity effort?
I'm sympathetic, and willing to help those who are expending their
maximum effort. But when I do projects for somebody else for no pay
I do them on my terms. This isn't my project. If you want me to do
the research for you, then I will. But I get *paid* for doing
other people's work for them. I've expended some effort on your
behalf, and requested in turn that you read three pages of a document,
spend some time thinking and trying to understand, then come back
with questions or requests for explanations or clarification.
I think that this is a reasonable request.
> 1) There is an app note with a schematic in it for
allowing the
> processor to be accessed in at least 2 ways. I may have even seen it.
> I can fab my own board from this schematic.
Ok, this is something you know that I do not.
> 2) There is some brand of software out there that
will allow me to
> burn code into my processor and fix the constants when they get
> screwed up. Constant is what the mfr calls it. I need this groups
> input on which software app to buy.
Yes, there is. Two versions are described on the pages I mentioned
in the PDF document you have a copy of. How about reading that
description, which is better written than one I could write,
and then ask questions about what you don't understand.
> These are the 2 things I need. If I'm stil
welcome here, then I want
> help finding these 2 items.
Of course you're still welcome. AFAIK, nobody is angry at anybody.
Google is your friend.
If you can't find it, then why do you suppose that I can?
The document describes three basic approaches to programming that
part. Here's the part of the document I asked you to read and
try to understand. Now, step one: let's read that text (not too hard)
and try to understand what it means to you in this context, and pick
one of the methods to try. Only when that is done can we
begin to design circuitry.
Method 1: Normal Programming.
You write a program which you load into the uController using any
means available to you. This program follows these steps:
[QUOTE MODE ON]
1. Set the ELAT bit in EPROG register. EELAT bit in PPROG must be
cleared as it$function of the ELAT bit.
2. Write data to the desired address.
3. Turn on programming voltage to the EPROM array by setting the EPGM
bit in EPROG register.
4. Delay for 2 ms or more, as appropriate.
5. Clear the EPGM bit in EPROG to turn off the programming voltage.
6. Clear the EPROG register to reconfigure the EPROM address and data
buses for normal operation.
Method 2: EPROM Emulation Mode
In EPROM emulation mode (PROG mode), the EPROM/OTPROM is programmed as a
stand-alone EPROM by adapting the MCU footprint to the 27C256-type EPROM
and using an appropriate EPROM programmer. To put the MCU in PROG mode,
pull the following pins low: MODA/LIR, MODB/VSTBY, RESET, PA[2:0]. Refer
to Figure 6.
Method 3:
In the third method, the EPROM is programmed by software while in the
special test or bootstrap modes. User-developed software can be uploaded
through the SCI, or a ROM resident EPROM programming utility can be
used. To use the resident utility, bootload a three-byte program
consisting of a single jump instruction to $BF00. $BF00 is the starting
address of a resident EPROM programming utility. The utility program
[QUOTE MODE OFF]
The utility program presumably uses the steps detailed above in
Method 1 Normal Programming to do the work for you. The EPROM
emulation looks to me to be the simplest, supposing it works.
The circuit diagram for that is shown in Figure 6, if you would
just go look at it. (You requested that such a circuit be found,
a few times now, and I've told you now three times at least
that I have already found you one, but you won't go look.)
Anyway, read that text, and try to understand what it means
for you. Methods 1 and 3 require that you learn how to write
a program and upload it, and design a minimal circuit which
can cause the uController to boot and talk via its serial
interface. Method 3 requires a simpler circuit (schematic in
Figure 6), and an EPROM programmer which can program 27C256 EPROMS.
Which method looks best for you?
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
Reply by Mike Phillips●August 16, 20062006-08-16
Holy Cow Mike!
Some of these HC11 pdf files are hundreds of pages of Greek!!!!
I came to this group looking for help. Clearly, I'm not a processor
guy. Never claimed to be. What I'm telling you is what little info I
was given. You are too close to this skill to see what I see. I don't
understand much of it. So I have to rely on you and others to take
what I say and translate it into your own lingo. If it's that annoying
just tell me. I'll bug out of here. But this is a real need by a whole
group of people who have spent thousands buying these vehicles not
knowing about the poor R & D testing that the manufacturer did. So
here I am, an R & D guy, busting my butt every free hour I have to
keep more of these boards from dying and resurrecting the ones that
have died.
1) There is an app note with a schematic in it for allowing the
processor to be accessed in at least 2 ways. I may have even seen it.
I can fab my own board from this schematic.
2) There is some brand of software out there that will allow me to
burn code into my processor and fix the constants when they get
screwed up. Constant is what the mfr calls it. I need this groups
input on which software app to buy.
These are the 2 things I need. If I'm stil welcome here, then I want
help finding these 2 items.
Mike
>
> May I make a suggestion? I suggest that you read the section on
> programming the EPROM in that PDF file at the URL I gave you.
> After you read that, then you can ask intelligent questions, and
> won't be relying on a fuzzy memory of a vague statement which
> you may have heard from someone who saw someone else use the
> chip.
>
> At the very least, you should be able to know what it is that
> you don't know, and have some vocabulary to talk about it.
>
> Mike
> --
> p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
> This message made from 100% recycled bits.
> You have found the bank of Larn.
> I can explain it for you, but I can't understand it for you.
> I speak only for myself, and I am unanimous in that!
>