Sign in

username:

password:



Not a member?

Search 68hc12



Search tips

Subscribe to 68hc12



68hc12 by Keywords

68HC1 | 812A4 | 9S12DP256 | Bootloader | CodeWarrior | D60A | Debugger | DP256 | ECT | EEPROM | EVB | Flash | HC1 | HCS12 | I2C | IAR | ICC1 | Interrupts | LCD | M68KIT912DP256 | MC9S12DP256 | MC9S12DP256B | Metrowerks | Motor | MSCAN | Multilink | PLL | Quadrature | SDI | SPI | Transceiver | XFC

Ads

Discussion Groups

Discussion Groups | 68HC12 | Writing to EEPROM

Join our technical discussions about Freescale Microcontrollers: M68HC12. (Freescale Semiconductor is a Subsidiary of Motorola).

Re: dbe definition - Author Unknown - May 16 16:11:00 2003

In a message dated 5/16/03 5:10:29 PM Eastern Daylight Time,
writes:

> holy bat chips batman! does it ever take a lot of hardware to build a pru
> for this thing

Why not just hang a couple of ls165s on the spi or something simple... what
do you need? 16 input? 16 outputs? [Non-text portions of this message have been removed]



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


dbe definition - Ed Taylor - May 16 16:18:00 2003

hi:

holy bat chips batman! does it ever take a lot of hardware to build a pru for this thing. i can't seem to find a clear definition of the dbe (pe7) pin for the 912b32. i'm assuming that any internal cpu register operations will leave it in a high state in the expanded mode. is this correct?

thanks in advance!!

regards,

ed

[Non-text portions of this message have been removed]




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

Re: dbe definition - Ed Taylor - May 16 16:34:00 2003

hi bob:

i'm building a universal board to use as a simulator for the 912b32 in
single chip mode. i want it to be exactly the same programming model as the
single chip hence the requirement for replicating ports a&b. the use for
such a beast is so that i can connect it (hard wired) to target boards (that
are hardware intensive) and develop the software in the 30k ram space
available in the lower half of memory. there are simulator/emulators
available for a hefty price but this is the way i want to go. i've got
red/green lamps on all i/o to monitor the status .. sort of looking like a
madame la-rue pinball machine. regards,

ed

----- Original Message -----
From: <>
To: <>
Sent: Friday, May 16, 2003 3:11 PM
Subject: Re: [68HC12] dbe definition > In a message dated 5/16/03 5:10:29 PM Eastern Daylight Time,
> writes:
>
> > holy bat chips batman! does it ever take a lot of hardware to build a
pru
> > for this thing
>
> Why not just hang a couple of ls165s on the spi or something simple...
what
> do you need? 16 input? 16 outputs? > [Non-text portions of this message have been removed] >
> --------------------------------------------------------
> To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit
> http://www.motorola.com/mcu






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

microcontroller using DVS - venu - May 16 16:59:00 2003

people,

i am looking for a microcontroller preferable cheap,
which has the feature of dynamic voltage scaling in
it.
please help if you can

venu

=====
venu venkata subramanya surampudi
700 woodland ave b 108
lexington kentucky
40508
usa ph# 859 323 7607

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
visit http://in.tv.yahoo.com


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

Re: dbe definition - Robert Smith - May 17 5:21:00 2003

I think this is already done by the WaferScale (now STM) PSD parts;.

Start here http://www.st.com/stonline/prodpres/memory/psd/html/psd_idx.htm

Bob Smith

--- Avoid computer viruses, Practice safe hex ---

-- Specializing in small, cost effective
embedded control systems --

http://www.smithmachineworks.com/embedprod.html Robert L. (Bob) Smith
Smith Machine Works, Inc.
9900 Lumlay Road
Richmond, VA 23236 804/745-1065
----- Original Message -----
From: "Ed Taylor" <>
To: <>
Sent: Friday, May 16, 2003 5:34 PM
Subject: Re: [68HC12] dbe definition > hi bob:
>
> i'm building a universal board to use as a simulator for the 912b32 in
> single chip mode. i want it to be exactly the same programming model as
the
> single chip hence the requirement for replicating ports a&b. the use for
> such a beast is so that i can connect it (hard wired) to target boards
(that
> are hardware intensive) and develop the software in the 30k ram space
> available in the lower half of memory. there are simulator/emulators
> available for a hefty price but this is the way i want to go. i've got
> red/green lamps on all i/o to monitor the status .. sort of looking like a
> madame la-rue pinball machine. > regards,
>
> ed
>
> ----- Original Message -----
> From: <>
> To: <>
> Sent: Friday, May 16, 2003 3:11 PM
> Subject: Re: [68HC12] dbe definition > > In a message dated 5/16/03 5:10:29 PM Eastern Daylight Time,
> > writes:
> >
> > > holy bat chips batman! does it ever take a lot of hardware to build a
> pru
> > > for this thing
> >
> > Why not just hang a couple of ls165s on the spi or something simple...
> what
> > do you need? 16 input? 16 outputs?
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > --------------------------------------------------------
> > To unsubscribe from this group, send an email to:
> >
> >
> > To learn more about Motorola Microcontrollers, please visit
> > http://www.motorola.com/mcu
> >
> >
> >
> >
> >
> > --------------------------------------------------------
> To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit
> http://www.motorola.com/mcu



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

Re: microcontroller using DVS - Andrei Chichak - May 28 16:37:00 2003

Alright, I'll ask...what is "dynamic voltage scaling"?

You wouldn't happen to want a Digital to Analog Converter (ADC) would you?

Andrei

At 10:59 PM 5/16/2003 +0100, you wrote:
>people,
>
>i am looking for a microcontroller preferable cheap,
>which has the feature of dynamic voltage scaling in
>it.
>please help if you can
>
>venu
>
>=====
>venu venkata subramanya surampudi
>700 woodland ave b 108
>lexington kentucky
>40508
>usa ph# 859 323 7607
>
>________________________________________________________________________
>Missed your favourite TV serial last night? Try the new, Yahoo! TV.
> visit http://in.tv.yahoo.com >--------------------------------------------------------
>To unsubscribe from this group, send an email to: >To learn more about Motorola Microcontrollers, please visit
>http://www.motorola.com/mcu




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

Re: microcontroller using DVS - venu - May 28 17:54:00 2003

andrei,

Thanks for your response, i am talking about a
microcontroller whose clock and supply voltage(Vdd)
can both be reduced to reduce the power. Doing this
the tasks will be executed with a delay but will be
executed. Usually the microcontrollers use the reduced
clock to accomodate the various power save modes but
doing both together is not that common. I have found
the same in motorola's dragon ball imx1 processor but
the documentation fell short of telling weather the
user can reduce both of them to see the phenomenon
working.I was just curious if you guys have come
across such a thing. I also know the intels speed step
technolgy means the same so is transmeta's crusoe
processor.

thanks

venu

=====
venu venkata subramanya surampudi
700 woodland ave b 108
lexington kentucky
40508
usa ph# 859 323 7607

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
visit http://in.tv.yahoo.com


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

Re: microcontroller using DVS - Michael Pont - May 29 0:49:00 2003

Venu,

> i am talking about a
> microcontroller whose clock and supply voltage
> can both be reduced to reduce the power.

I know that DVS is supported by some processors with an ARM core (e.g. Intel
StrongARM SA-1100). I'm not sure if this is within your price range?

As far as I am aware, no members of the HC12 family (the focus of this list)
have such support. You may be better to ask the question on some more
general microcontroller / microprocessors lists.

Michael.

+==================================+

Michael J. Pont, PhD
Embedded Systems Laboratory
University of Leicester

http://www.le.ac.uk/eg/embedded

+==================================+




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

Re: microcontroller using DVS - Andrei Chichak - May 29 10:25:00 2003

The Motorola 68332 normally runs off of a 32768Hz. crystal that is PLL'd up
to the typical 16-25MHz. running frequency. The processor boots at 8MHz,
then your code sets the SYNC register to a value that sets the PLL down to,
at most, 128KHz. and up to full specified speed with a varying granularity
of about 128KHz. to 1MHz.

The '332 <<CAN>> run down to 3.3V (same core as the 68LK332), but no
guarantees.

You should be able to do this with pretty much any static processor, a PIC
will happily run on a 32768Hz. watch crystal and will run off of 3 AA cells
(as is the one on my desk). Switching, on the fly, to 5V is not a problem.
You would have to come up with some external circuitry to alter the clock
frequency without consuming more power than you are trying to save.

Andrei

At 11:54 PM 5/28/2003 +0100, you wrote:
>andrei,
>
>Thanks for your response, i am talking about a
>microcontroller whose clock and supply voltage(Vdd)
>can both be reduced to reduce the power. Doing this
>the tasks will be executed with a delay but will be
>executed. Usually the microcontrollers use the reduced
>clock to accomodate the various power save modes but
>doing both together is not that common. I have found
>the same in motorola's dragon ball imx1 processor but
>the documentation fell short of telling weather the
>user can reduce both of them to see the phenomenon
>working.I was just curious if you guys have come
>across such a thing. I also know the intels speed step
>technolgy means the same so is transmeta's crusoe
>processor.
>
>thanks
>
>venu
>
>=====
>venu venkata subramanya surampudi
>700 woodland ave b 108
>lexington kentucky
>40508
>usa ph# 859 323 7607
>
>________________________________________________________________________
>Missed your favourite TV serial last night? Try the new, Yahoo! TV.
> visit http://in.tv.yahoo.com >--------------------------------------------------------
>To unsubscribe from this group, send an email to: >To learn more about Motorola Microcontrollers, please visit
>http://www.motorola.com/mcu



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

Re: Re: microcontroller using DVS - Michael Pont - May 29 11:38:00 2003


My understanding:

One of the features of the ARM-based processors is that there are two supply-voltage pins on the processor, in order to allow you to change the CPU voltage without varying the I/O pin voltage.

If you don't have this facility, you may have difficulty with your I/O when you lower the chip voltage?

Michael. > From: Andrei Chichak <>
> Date: 2003/05/29 Thu PM 03:25:40 GMT
> To:
> Subject: Re: [68HC12] microcontroller using DVS
>
> The Motorola 68332 normally runs off of a 32768Hz. crystal that is PLL'd up
> to the typical 16-25MHz. running frequency. The processor boots at 8MHz,
> then your code sets the SYNC register to a value that sets the PLL down to,
> at most, 128KHz. and up to full specified speed with a varying granularity
> of about 128KHz. to 1MHz.
>
> The '332 <<CAN>> run down to 3.3V (same core as the 68LK332), but no
> guarantees.
>
> You should be able to do this with pretty much any static processor, a PIC
> will happily run on a 32768Hz. watch crystal and will run off of 3 AA cells
> (as is the one on my desk). Switching, on the fly, to 5V is not a problem.
> You would have to come up with some external circuitry to alter the clock
> frequency without consuming more power than you are trying to save.
>
> Andrei
>
> At 11:54 PM 5/28/2003 +0100, you wrote:
> >andrei,
> >
> >Thanks for your response, i am talking about a
> >microcontroller whose clock and supply voltage(Vdd)
> >can both be reduced to reduce the power. Doing this
> >the tasks will be executed with a delay but will be
> >executed. Usually the microcontrollers use the reduced
> >clock to accomodate the various power save modes but
> >doing both together is not that common. I have found
> >the same in motorola's dragon ball imx1 processor but
> >the documentation fell short of telling weather the
> >user can reduce both of them to see the phenomenon
> >working.I was just curious if you guys have come
> >across such a thing. I also know the intels speed step
> >technolgy means the same so is transmeta's crusoe
> >processor.
> >
> >thanks
> >
> >venu
> >
> >=====
> >venu venkata subramanya surampudi
> >700 woodland ave b 108
> >lexington kentucky
> >40508
> >usa ph# 859 323 7607
> >
> >________________________________________________________________________
> >Missed your favourite TV serial last night? Try the new, Yahoo! TV.
> > visit http://in.tv.yahoo.com
> >
> >
> >--------------------------------------------------------
> >To unsubscribe from this group, send an email to:
> >
> >
> >To learn more about Motorola Microcontrollers, please visit
> >http://www.motorola.com/mcu
> >
> >
> >
> --------------------------------------------------------
> To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit
> http://www.motorola.com/mcu > >

+======================================+

Michael J. Pont, PhD
Embedded Systems Laboratory,
University of Leicester

http://www.le.ac.uk/eg/embedded

+======================================+




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

Re: Re: microcontroller using DVS - venu - May 29 13:17:00 2003

exactly micahael,

There should also be a DC-DC converter to reduce the
processor speed.
=====
venu venkata subramanya surampudi
700 woodland ave b 108
lexington kentucky
40508
usa ph# 859 323 7607

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
visit http://in.tv.yahoo.com


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

Writing to EEPROM - John Theofanopoulos - May 29 15:39:00 2003

Hi all,

This relates more to the Start12 (HCS12) architecture, but hopefully
someone can shed some light on this.

I have code written for the S12DP256 that writes to EEPROM and it does
so everytime, without any problems. If I take that same code and put it
into an S12DG128, the EEPROM writing functions 'seem' to work, but in
actuality they're not really writing anything to EEPROM. I'm sort of at
a loss here. When working with a DG128 I do set the INITEE variable to
0x09 which should move it to the 0x800->0xFFF range, which should make
the code for EEPROM storage transparent across the micros (I start
writing at 0x800).

Does anybody have any suggestions (constructive and relating to this
particular problem :) ) John





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

Re: Writing to EEPROM - Author Unknown - May 29 16:36:00 2003

John

I assume that in the first case, you are running your code out of RAM and in the latter case out of FLASH. Did you actually step through your code in flash to make sure you do not have any paging problems, etc?

Are you running in specialsingle chip mode in the first case and regular single chip mode in the latter case?

Regards
Dave Perreault > From: "John Theofanopoulos" <>
> Date: 2003/05/29 Thu PM 04:39:16 EDT
> To: <>
> Subject: [68HC12] Writing to EEPROM
>
> Hi all,
>
> This relates more to the Start12 (HCS12) architecture, but hopefully
> someone can shed some light on this.
>
> I have code written for the S12DP256 that writes to EEPROM and it does
> so everytime, without any problems. If I take that same code and put it
> into an S12DG128, the EEPROM writing functions 'seem' to work, but in
> actuality they're not really writing anything to EEPROM. I'm sort of at
> a loss here. When working with a DG128 I do set the INITEE variable to
> 0x09 which should move it to the 0x800->0xFFF range, which should make
> the code for EEPROM storage transparent across the micros (I start
> writing at 0x800).
>
> Does anybody have any suggestions (constructive and relating to this
> particular problem :) ) > John >
>
> --------------------------------------------------------
> To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit
> http://www.motorola.com/mcu >




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

RE: Writing to EEPROM - John Theofanopoulos - May 30 7:25:00 2003

Dave,

Actually, in both cases I'm running out of Flash (trying to keep things
as consistent as possible). I have stepped through the code and it
seems to be putting the data in the right memory location and the flash
routine seems to be doing its thing. I'm really puzzled by this, but
will do a little bit more digging/comparing to see if I can come up with
more info

John Theofanopoulos

-----Original Message-----
From: [mailto:]
Sent: Thursday, May 29, 2003 5:36 PM
To:
Subject: Re: [68HC12] Writing to EEPROM John

I assume that in the first case, you are running your code out of RAM
and in the latter case out of FLASH. Did you actually step through your
code in flash to make sure you do not have any paging problems, etc?

Are you running in specialsingle chip mode in the first case and regular
single chip mode in the latter case?

Regards
Dave Perreault > From: "John Theofanopoulos" <>
> Date: 2003/05/29 Thu PM 04:39:16 EDT
> To: <>
> Subject: [68HC12] Writing to EEPROM
>
> Hi all,
>
> This relates more to the Start12 (HCS12) architecture, but hopefully
> someone can shed some light on this.
>
> I have code written for the S12DP256 that writes to EEPROM and it does

> so everytime, without any problems. If I take that same code and put
> it into an S12DG128, the EEPROM writing functions 'seem' to work, but
> in actuality they're not really writing anything to EEPROM. I'm sort
of at
> a loss here. When working with a DG128 I do set the INITEE variable
to
> 0x09 which should move it to the 0x800->0xFFF range, which should make

> the code for EEPROM storage transparent across the micros (I start
> writing at 0x800).
>
> Does anybody have any suggestions (constructive and relating to this
> particular problem :) ) > John >
>
> --------------------------------------------------------
> To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit
> http://www.motorola.com/mcu
--------------------------------------------------------
To unsubscribe from this group, send an email to: To learn more about Motorola Microcontrollers, please visit
http://www.motorola.com/mcu





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

RE: Writing to EEPROM - mohan kumar - May 31 5:14:00 2003

John,

Are you running both the micros at the same system clock frequency? If not you may
need to adjust the timer register of EEPROM to get the EEPROM (erase/prg.)module to work between 150KHz to 200KHz.

Regards,
Mohan

John Theofanopoulos <> wrote:
Dave,

Actually, in both cases I'm running out of Flash (trying to keep things
as consistent as possible). I have stepped through the code and it
seems to be putting the data in the right memory location and the flash
routine seems to be doing its thing. I'm really puzzled by this, but
will do a little bit more digging/comparing to see if I can come up with
more info

John Theofanopoulos

-----Original Message-----
From: [mailto:]
Sent: Thursday, May 29, 2003 5:36 PM
To:
Subject: Re: [68HC12] Writing to EEPROM John

I assume that in the first case, you are running your code out of RAM
and in the latter case out of FLASH. Did you actually step through your
code in flash to make sure you do not have any paging problems, etc?

Are you running in specialsingle chip mode in the first case and regular
single chip mode in the latter case?

Regards
Dave Perreault > From: "John Theofanopoulos" <>
> Date: 2003/05/29 Thu PM 04:39:16 EDT
> To: <>
> Subject: [68HC12] Writing to EEPROM
>
> Hi all,
>
> This relates more to the Start12 (HCS12) architecture, but hopefully
> someone can shed some light on this.
>
> I have code written for the S12DP256 that writes to EEPROM and it does

> so everytime, without any problems. If I take that same code and put
> it into an S12DG128, the EEPROM writing functions 'seem' to work, but
> in actuality they're not really writing anything to EEPROM. I'm sort
of at
> a loss here. When working with a DG128 I do set the INITEE variable
to
> 0x09 which should move it to the 0x800->0xFFF range, which should make

> the code for EEPROM storage transparent across the micros (I start
> writing at 0x800).
>
> Does anybody have any suggestions (constructive and relating to this
> particular problem :) ) > John >
>
> --------------------------------------------------------
> To unsubscribe from this group, send an email to: > To learn more about Motorola Microcontrollers, please visit
> http://www.motorola.com/mcu
--------------------------------------------------------
To unsubscribe from this group, send an email to: To learn more about Motorola Microcontrollers, please visit
http://www.motorola.com/mcu
Yahoo! Groups Sponsor
--------------------------------------------------------
To unsubscribe from this group, send an email to: To learn more about Motorola Microcontrollers, please visit
http://www.motorola.com/mcu Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
,

---------------------------------





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

RE: Writing to EEPROM - Steve Russell - May 31 20:40:00 2003

John,

I have seen similar symptoms when the flash security bits (bits 0 and 1) in
flash at banked address 0x3FFF0F were not set to "unsecure". (Bit 1 1 and
bit 0 0).

This requires programming banked address 0x3FFF0F after erasing flash and
before the next reset. You will see special code to do this in may HCS-12
flash programming examples.

It appears that some mask sets for HCS-12 parts do not behave as one would
expect when "secured".

The unsecuring procedure in AN2400/D has made this "partially secured"
symptom go away for me.

Steve At 03:14 AM 5/31/2003, you wrote:
>John,
>
>Are you running both the micros at the same system clock frequency? If
>not you may
>need to adjust the timer register of EEPROM to get the EEPROM
>(erase/prg.)module to work between 150KHz to 200KHz.
>
>Regards,
>Mohan >
>
>John Theofanopoulos <> wrote:
>Dave,
>
>Actually, in both cases I'm running out of Flash (trying to keep things
>as consistent as possible). I have stepped through the code and it
>seems to be putting the data in the right memory location and the flash
>routine seems to be doing its thing. I'm really puzzled by this, but
>will do a little bit more digging/comparing to see if I can come up with
>more info
>
>John Theofanopoulos
>
>-----Original Message-----
>From: [mailto:]
>Sent: Thursday, May 29, 2003 5:36 PM
>To:
>Subject: Re: [68HC12] Writing to EEPROM >John
>
>I assume that in the first case, you are running your code out of RAM
>and in the latter case out of FLASH. Did you actually step through your
>code in flash to make sure you do not have any paging problems, etc?
>
>Are you running in specialsingle chip mode in the first case and regular
>single chip mode in the latter case?
>
>Regards
>Dave Perreault
>
> >
> > From: "John Theofanopoulos" <>
> > Date: 2003/05/29 Thu PM 04:39:16 EDT
> > To: <>
> > Subject: [68HC12] Writing to EEPROM
> >
> > Hi all,
> >
> > This relates more to the Start12 (HCS12) architecture, but hopefully
> > someone can shed some light on this.
> >
> > I have code written for the S12DP256 that writes to EEPROM and it does
>
> > so everytime, without any problems. If I take that same code and put
> > it into an S12DG128, the EEPROM writing functions 'seem' to work, but
> > in actuality they're not really writing anything to EEPROM. I'm sort
>of at
> > a loss here. When working with a DG128 I do set the INITEE variable
>to
> > 0x09 which should move it to the 0x800->0xFFF range, which should make
>
> > the code for EEPROM storage transparent across the micros (I start
> > writing at 0x800).
> >
> > Does anybody have any suggestions (constructive and relating to this
> > particular problem :) )
> >
> >
> > John
> >
> >
> >
> >
> > --------------------------------------------------------
> > To unsubscribe from this group, send an email to:
> >
> >
> > To learn more about Motorola Microcontrollers, please visit
> > <http://www.motorola.com/mcu>http://www.motorola.com/mcu
> >
> >
> > >http://docs.yahoo.com/info/terms/
> >
> >
> >
>--------------------------------------------------------
>To unsubscribe from this group, send an email to: >To learn more about Motorola Microcontrollers, please visit
><http://www.motorola.com/mcu>http://www.motorola.com/mcu >>http://docs.yahoo.com/info/terms/ >
>Yahoo! Groups Sponsor
>--------------------------------------------------------
>To unsubscribe from this group, send an email to: >To learn more about Motorola Microcontrollers, please visit
><http://www.motorola.com/mcu>http://www.motorola.com/mcu >>Yahoo! Terms of Service. *************************************************************************
Steve Russell mailto:
Senior Software Design Engineer http://www.nohau.com
Nohau Corporation phone: (408)866-1820
51 East Campbell Avenue fax: (408)378-7869
Campbell, CA 95008
*************************************************************************

[Non-text portions of this message have been removed]




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

RE: Writing to EEPROM - Steve Russell - Jun 1 18:09:00 2003

John,

I was sloppy about describing where to look for the security bits in
flash. They can be seen at many places, but the key to seeing them is that
they are in page 0x3F. To see them, the ROMON bit in the MISC register
(bit 0 of register block location 0x13, must be set.

The security bits will be at the 16-bit address of 0xFF0F, because page
0x3F is mapped to the 16-bit addressees of 0xC000 through 0xFFFF.

If PPAGE is set to 0x3F, then the security will also be visible at 16-bit
address 0xBF0F in the "program window".

If you are using "linear" or "physical" addressing (as for an S19 file for
some flash programming utilities), the address would be 14 bits of location
in the "program window" 0x3F0F plus 6 bits of PPAGE value shifted left 14
bits 0xFC000, giving 0xFFF0F.

If you are using "banked" or "logical" addressing,the address is the 16 bit
address of the location in the program window 0xBF0F plus the 6 bits of
PPAGE shifted left 16 bits 0x3F0000, giving 0x3FBF0F.

The logical addressing schemes that I am familiar with will display the 16
bit processor address if the 16 bit address is outside the "program window"
of 0x8000 through 0xBFFF, so "banked" address 0x3FFF0F will display the
same as 0xFF0F and also show you the security bits.

Every time I try to explain it, I'm sorry its so complicated. However, its
one of the simplest of such schemes around. (Ask someone to explain the
addressing in a modern 8051 derivative.) It does save bits in the CPU
hardware.

Steve

At 06:40 PM 5/31/2003, Steve Russell wrote:
>John,
>
>I have seen similar symptoms when the flash security bits (bits 0 and 1) in
>flash at banked address 0x3FFF0F were not set to "unsecure". (Bit 1 1 and
>bit 0 0).
>
>This requires programming banked address 0x3FFF0F after erasing flash and
>before the next reset. You will see special code to do this in may HCS-12
>flash programming examples.
>
>It appears that some mask sets for HCS-12 parts do not behave as one would
>expect when "secured".
>
>The unsecuring procedure in AN2400/D has made this "partially secured"
>symptom go away for me.
>
> Steve >At 03:14 AM 5/31/2003, Mohan wrote:
> >John,
> >
> >Are you running both the micros at the same system clock frequency? If
> >not you may
> >need to adjust the timer register of EEPROM to get the EEPROM
> >(erase/prg.)module to work between 150KHz to 200KHz.
> >
> >Regards,
> >Mohan
> >
> >
> >
> >
> >John Theofanopoulos <> wrote:
> >Dave,
> >
> >Actually, in both cases I'm running out of Flash (trying to keep things
> >as consistent as possible). I have stepped through the code and it
> >seems to be putting the data in the right memory location and the flash
> >routine seems to be doing its thing. I'm really puzzled by this, but
> >will do a little bit more digging/comparing to see if I can come up with
> >more info
> >
> >John Theofanopoulos
> >
> >-----Original Message-----
> >From: [mailto:]
> >Sent: Thursday, May 29, 2003 5:36 PM
> >To:
> >Subject: Re: [68HC12] Writing to EEPROM
> >
> >
> >John
> >
> >I assume that in the first case, you are running your code out of RAM
> >and in the latter case out of FLASH. Did you actually step through your
> >code in flash to make sure you do not have any paging problems, etc?
> >
> >Are you running in specialsingle chip mode in the first case and regular
> >single chip mode in the latter case?
> >
> >Regards
> >Dave Perreault
> >
> > >
> > > From: "John Theofanopoulos" <>
> > > Date: 2003/05/29 Thu PM 04:39:16 EDT
> > > To: <>
> > > Subject: [68HC12] Writing to EEPROM
> > >
> > > Hi all,
> > >
> > > This relates more to the Start12 (HCS12) architecture, but hopefully
> > > someone can shed some light on this.
> > >
> > > I have code written for the S12DP256 that writes to EEPROM and it does
> >
> > > so everytime, without any problems. If I take that same code and put
> > > it into an S12DG128, the EEPROM writing functions 'seem' to work, but
> > > in actuality they're not really writing anything to EEPROM. I'm sort
> >of at
> > > a loss here. When working with a DG128 I do set the INITEE variable
> >to
> > > 0x09 which should move it to the 0x800->0xFFF range, which should make
> >
> > > the code for EEPROM storage transparent across the micros (I start
> > > writing at 0x800).
> > >
> > > Does anybody have any suggestions (constructive and relating to this
> > > particular problem :) )
> > >
> > >
> > > John
> > >
> > >
> > >
> > >
> > > --------------------------------------------------------
> > > To unsubscribe from this group, send an email to:
> > >
> > >
> > > To learn more about Motorola Microcontrollers, please visit
> > >
> <<http://www.motorola.com/mcu>http://www.motorola.com/mcu>http://www.motorola.com/mcu
> > >
> > >
> > > >http://docs.yahoo.com/info/terms/>http://docs.yahoo.com/info/terms/
> > >
> > >
> > >
> >
> >
> >
> >--------------------------------------------------------
> >To unsubscribe from this group, send an email to:
> >
> >
> >To learn more about Motorola Microcontrollers, please visit
> ><<http://www.motorola.com/mcu>http://www.motorola.com/mcu>http://www.moto
> rola.com/mcu
> >
> >
> >>http://docs.yahoo.com/info/terms/>htt
> p://docs.yahoo.com/info/terms/
> >
> >
> >
> >Yahoo! Groups Sponsor
> >--------------------------------------------------------
> >To unsubscribe from this group, send an email to:
> >
> >
> >To learn more about Motorola Microcontrollers, please visit
> ><<http://www.motorola.com/mcu>http://www.motorola.com/mcu>http://www.moto
> rola.com/mcu
> >
> >
> >>http://docs.yahoo.com/info/terms/>Yah
> oo! Terms of Service. >*************************************************************************
>Steve Russell mailto:
>Senior Software Design
>Engineer <http://www.nohau.com>http://www.nohau.com
>Nohau Corporation phone: (408)866-1820
>51 East Campbell Avenue fax: (408)378-7869
>Campbell, CA 95008
>*************************************************************************
>
>[Non-text portions of this message have been removed] >Yahoo! Groups Sponsor
>ADVERTISEMENT
><http://rd.yahoo.com/M=244522.3313099.4604523.1261774/D=egroupweb/S=1706554205:HM/A=1595056/R=0/SIG=124fv1soh/*http://ashnin.com/clk/muryutaitakenattogyo?YH=3313099&yhad=1595056>565f7b.jpg
>565fe9.jpg
>
>--------------------------------------------------------
>To unsubscribe from this group, send an email to: >To learn more about Motorola Microcontrollers, please visit
><http://www.motorola.com/mcu>http://www.motorola.com/mcu >>Yahoo! Terms of Service. [Non-text portions of this message have been removed]




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

RE: Writing to EEPROM - John Theofanopoulos - Jun 2 7:26:00 2003

I'ld like to thank all of you for the suggestions on the EEPROM. I
finally did find the problem, and I'll describe the issue here, in case
somebody else runs into something similar.

As I mentionned a lot of our code is written on a Dx256 part, but we
sometimes use a Dx128 part in our release part (we have more of those
parts in house, so if we fry a Dx256 on the eval board, we simply
replace it with a Dx128). So basically we have a mix of Dx256 and
Dx128's and the software should work across all of them without a
recompile/relink. We basically set our limits to the lowest common
denominator (2K EEPROM, 8K RAM, etc).

Here's the problem.

The Dx256 part has its RAM at 0x1000->0x3FFF and its EEPROM at 0x000 ->
0xFFF. For our purpses we pretty much ignored the lower section of
EEPROM and started writing at 0x800.
The Dx128 part has its RAM at 0x0000->0x1FFF and its EEPROM at 0x000 ->
0x7FF.

Mapping the EEPROM alone to 0x800 did not do the trick since it was
still overlapped by RAM and RAM has priority of EEPROM. In order for
this to work, I had to remap the RAM to 0x2000->0x3FFF (by using
INTRM=0x39) I was able to map the RAM in such a way to keep the code
consistent for the Dx128 and Dx256 parts.

There's a document for this: EB386/D, Rev. 3, 07/2002.

Again, thanks to all for your suggestions.

John Theofanopoulos -----Original Message-----
From: Steve Russell [mailto:]
Sent: Sunday, June 01, 2003 7:10 PM
To:
Subject: RE: [68HC12] Writing to EEPROM John,

I was sloppy about describing where to look for the security bits in
flash. They can be seen at many places, but the key to seeing them is
that
they are in page 0x3F. To see them, the ROMON bit in the MISC register
(bit 0 of register block location 0x13, must be set.

The security bits will be at the 16-bit address of 0xFF0F, because page
0x3F is mapped to the 16-bit addressees of 0xC000 through 0xFFFF.

If PPAGE is set to 0x3F, then the security will also be visible at
16-bit
address 0xBF0F in the "program window".

If you are using "linear" or "physical" addressing (as for an S19 file
for
some flash programming utilities), the address would be 14 bits of
location
in the "program window" 0x3F0F plus 6 bits of PPAGE value shifted left
14
bits 0xFC000, giving 0xFFF0F.

If you are using "banked" or "logical" addressing,the address is the 16
bit
address of the location in the program window 0xBF0F plus the 6 bits of
PPAGE shifted left 16 bits 0x3F0000, giving 0x3FBF0F.

The logical addressing schemes that I am familiar with will display the
16
bit processor address if the 16 bit address is outside the "program
window"
of 0x8000 through 0xBFFF, so "banked" address 0x3FFF0F will display the
same as 0xFF0F and also show you the security bits.

Every time I try to explain it, I'm sorry its so complicated. However,
its
one of the simplest of such schemes around. (Ask someone to explain the

addressing in a modern 8051 derivative.) It does save bits in the CPU
hardware.

Steve

At 06:40 PM 5/31/2003, Steve Russell wrote:
>John,
>
>I have seen similar symptoms when the flash security bits (bits 0 and
>1) in flash at banked address 0x3FFF0F were not set to "unsecure".
>(Bit 1 1 and bit 0 0).
>
>This requires programming banked address 0x3FFF0F after erasing flash
>and before the next reset. You will see special code to do this in may

>HCS-12 flash programming examples.
>
>It appears that some mask sets for HCS-12 parts do not behave as one
>would expect when "secured".
>
>The unsecuring procedure in AN2400/D has made this "partially secured"
>symptom go away for me.
>
> Steve >At 03:14 AM 5/31/2003, Mohan wrote:
> >John,
> >
> >Are you running both the micros at the same system clock frequency?
> >If not you may need to adjust the timer register of EEPROM to get the

> >EEPROM (erase/prg.)module to work between 150KHz to 200KHz.
> >
> >Regards,
> >Mohan
> >
> >
> >
> >
> >John Theofanopoulos <> wrote:
> >Dave,
> >
> >Actually, in both cases I'm running out of Flash (trying to keep
> >things as consistent as possible). I have stepped through the code
> >and it seems to be putting the data in the right memory location and
> >the flash routine seems to be doing its thing. I'm really puzzled by

> >this, but will do a little bit more digging/comparing to see if I can

> >come up with more info
> >
> >John Theofanopoulos
> >
> >-----Original Message-----
> >From: [mailto:]
> >Sent: Thursday, May 29, 2003 5:36 PM
> >To:
> >Subject: Re: [68HC12] Writing to EEPROM
> >
> >
> >John
> >
> >I assume that in the first case, you are running your code out of RAM

> >and in the latter case out of FLASH. Did you actually step through
> >your code in flash to make sure you do not have any paging problems,
> >etc?
> >
> >Are you running in specialsingle chip mode in the first case and
> >regular single chip mode in the latter case?
> >
> >Regards
> >Dave Perreault
> >
> > >
> > > From: "John Theofanopoulos" <>
> > > Date: 2003/05/29 Thu PM 04:39:16 EDT
> > > To: <>
> > > Subject: [68HC12] Writing to EEPROM
> > >
> > > Hi all,
> > >
> > > This relates more to the Start12 (HCS12) architecture, but
> > > hopefully someone can shed some light on this.
> > >
> > > I have code written for the S12DP256 that writes to EEPROM and it
> > > does
> >
> > > so everytime, without any problems. If I take that same code and
> > > put it into an S12DG128, the EEPROM writing functions 'seem' to
> > > work, but in actuality they're not really writing anything to
> > > EEPROM. I'm sort
> >of at
> > > a loss here. When working with a DG128 I do set the INITEE
variable
> >to
> > > 0x09 which should move it to the 0x800->0xFFF range, which should
> > > make
> >
> > > the code for EEPROM storage transparent across the micros (I start

> > > writing at 0x800).
> > >
> > > Does anybody have any suggestions (constructive and relating to
this
> > > particular problem :) )
> > >
> > >
> > > John
> > >
> > >
> > >
> > >
> > > --------------------------------------------------------
> > > To unsubscribe from this group, send an email to:
> > >
> > >
> > > To learn more about Motorola Microcontrollers, please visit
> > >
> <<http://www.motorola.com/mcu>http://www.motorola.com/mcu>http://www.m
> otorola.com/mcu
> > >
> > >
> > > >http://docs.yahoo.com/info/terms/>
> http://docs.yahoo.com/info/terms/
> > >
> > >
> > >
> >
> >
> >
> >--------------------------------------------------------
> >To unsubscribe from this group, send an email to:
> >
> >
> >To learn more about Motorola Microcontrollers, please visit
> ><<http://www.motorola.com/mcu>http://www.motorola.com/mcu>http://www.
> >moto
> rola.com/mcu
> >
> >
> >>http://docs.yahoo.com/info/terms/
> >>htt
> p://docs.yahoo.com/info/terms/
> >
> >
> >
> >Yahoo! Groups Sponsor
> >--------------------------------------------------------
> >To unsubscribe from this group, send an email to:
> >
> >
> >To learn more about Motorola Microcontrollers, please visit
> ><<http://www.motorola.com/mcu>http://www.motorola.com/mcu>http://www.
> >moto
> rola.com/mcu
> >
> >
> >>http://docs.yahoo.com/info/terms/
> >>Yah
> oo! Terms of Service. >***********************************************************************
**
>Steve Russell
mailto:
>Senior Software Design
>Engineer
<http://www.nohau.com>http://www.nohau.com
>Nohau Corporation phone:
(408)866-1820
>51 East Campbell Avenue fax:
(408)378-7869
>Campbell, CA 95008
>***********************************************************************
>**
>
>[Non-text portions of this message have been removed] >Yahoo! Groups Sponsor
>ADVERTISEMENT
><http://rd.yahoo.com/M=244522.3313099.4604523.1261774/D=egroupweb/S=170
>6554205:HM/A=1595056/R=0/SIG=124fv1soh/*http://ashnin.com/clk/muryutait
akenattogyo?YH=3313099&yhad=1595056>565f7b.jpg
>565fe9.jpg
>
>--------------------------------------------------------
>To unsubscribe from this group, send an email to: >To learn more about Motorola Microcontrollers, please visit
><http://www.motorola.com/mcu>http://www.motorola.com/mcu >>Yahoo! Terms of Service. [Non-text portions of this message have been removed]
--------------------------------------------------------
To unsubscribe from this group, send an email to: To learn more about Motorola Microcontrollers, please visit
http://www.motorola.com/mcu




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

Writing to EEPROM - wwsyip - Jun 10 13:44:00 2004

Hi there,

I'm trying to find a way to write a value and be able to retrieve
after resetting the HC12. I have been told by the technological arts
people that this can be done using EEPROM.

Does anyone know how to do it or have any source code? Thanks!




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

Re: Writing to EEPROM - theobee00 - Jun 10 17:05:00 2004

--- In , "wwsyip" <wwsyip@y...> wrote:

> I'm trying to find a way to write a value and be able to retrieve
> after resetting the HC12. I have been told by the technological arts
> people that this can be done using EEPROM.
>
> Does anyone know how to do it or have any source code? Thanks!

My version is in the files area, do check if it is compatible with the chip you use.

Cheers,

Theo



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

Re: Writing to EEPROM - peter_lingier - Jun 11 1:53:00 2004

--- In , "wwsyip" <wwsyip@y...> wrote:
> Hi there,
>
> I'm trying to find a way to write a value and be able to retrieve
> after resetting the HC12. I have been told by the technological
arts
> people that this can be done using EEPROM.
>
> Does anyone know how to do it or have any source code? Thanks!

AN2400/D to be found on the Motorola website, was a big help.
On http://www.dragonsgate.net/pipermail/icc-mot/2003-
November/000718.html, you can find sample code.

Greetings,

Peter



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

Re: Writing to EEPROM - peter_lingier - Jun 11 1:54:00 2004

--- In , "wwsyip" <wwsyip@y...> wrote:
> Hi there,
>
> I'm trying to find a way to write a value and be able to retrieve
> after resetting the HC12. I have been told by the technological
arts
> people that this can be done using EEPROM.
>
> Does anyone know how to do it or have any source code? Thanks!

AN2400/D to be found on the Motorola website, was a big help.
On http://www.dragonsgate.net/pipermail/icc-mot/2003-
November/000718.html, you can find sample code.

Greetings,

Peter



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