Re: Re: HC711 pinout | M68HC11 | EmbeddedRelated.com

----- Original Message -----
From: "Mike McCarty"
To:
Sent: Wednesday, August 16, 2006 2:14 PM
Subject: Re: [m68HC11] Re: HC711 pinout
> 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.
> INIT � RAM and Register Mapping $003D
> Bit 7 6 5 4 3 2 1 Bit 0
> RAM3 RAM2 RAM1 RAM0 REG3 REG2 REG1 REG0
> RESET: 0 0 0 0 0 0 0 0
> 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!

______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!

(You need to be a member of hc11 -- send a blank email to hc11-subscribe@yahoogroups.com )

Sign in

Search hc11

Subscribe to hc11

Ads

Discussion Groups

See Also

Discussion Groups | M68HC11 | Re: Re: HC711 pinout

Re: Re: HC711 pinout - Robert Smith - Aug 16 15:09:50 2006

Re: Re: HC711 pinout - Mike McCarty - Aug 16 16:57:48 2006