Sign in

username:

password:



Not a member?

Search hc11



Search tips

Subscribe to hc11



Ads

Discussion Groups

Discussion Groups | M68HC11 | Books for the M68HC11

Technical discussions about Freescale Microcontrollers: M68HC11. (Freescale Semiconductor is a Subsidiary of Motorola).

Books for the M68HC11 - Nick Reitter - Nov 30 13:10:00 2004

Here are two texts that good:
"Microcontroller Technology - The 68HC11"; Peter Saspov, Prentice Hall
"Data Acquisition and Process Control with the M68HC11 Microcontroller";
Driscoll etal; Prentice Hall

Nick

-----Original Message-----
From: Israel Brewster [mailto:]
Sent: Tuesday, November 30, 2004 12:16 PM
To:
Subject: [m68HC11] Re: Code Auto Execution problem

yeah, good advice- and absolutely true. The annoying thing about this
situation is that, as
far as I can tell, the need to initialize the OPTION register is completely
undocumented, at
least in the materials I have available. Its existence is not even mentioned
in the book I
have on the subject. So while I am aware of the need to initialize
everything, I don't know
what all needs to be initialized. This, of course, leads to very annoying
problems such as
the one I just experienced. If anyone wants to suggest some good reference
sources for
programing with the HC11/HC12 (thinking of moving up) that mention such
things, I
would appreciate it. Thanks again everyone.

--- In , "Mark Schultz" <n9xmj@y...> wrote:
>
> --- In , Scott Grodevant <scott14468@y...>
> wrote:
> > Hi all and Israel,
> >
> > My memory fails me for specifics about the HC11 (without going to
> > the manual), but I am pretty sure there is a configuration register
> > associated with the ADC that must be initialized before using it.
> > Without BUFFALO running to do it for you, the ADC is probably
> > disabled.
>
> What Scott says here comes close to the advice I will offer.
>
> When you transition from a debug environment (e.g.
> BUFFALO/PCBUG/JBug/etc.) to a 'standalone' runtime environment, you
> must take care to ensure that your program includes ALL necessary
> initialization code. This means things like: Setting the stack
> pointer and status register properly, initializing all your RAM
> variables to known values, setting values in time-protected registers
> such as HPRIO, and initializing ALL subsystems you are using.
>
> You can get away without doing much of the above because a typical
> monitor program will place the MCU in a known, safe-operation state
> as part of its own initialization. This is not true when you start
> up out of reset directly into your own program. You are responsible
> for initializing any subsystem/peripheral you choose to use, and are
> also responsible for initializing the CPU registers and memory
> appropriately.

Yahoo! Groups Links




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