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

See Also

DSPFPGAElectronics

Discussion Groups | 68HC12 | Using eeprom constants in CW

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

Using eeprom constants in CW - jfrom90 - Apr 2 3:37:00 2004

Hi,
I use codewarrior v3.0 in my project (processor = HCS12 DG128).
My intention is to map the eeprom to addresss 0x800.

The Hiwave-debugger uses the s-record fpp-file to support
eeprom-writing (I believe) during program loading.
In my case the fpp file CW12_V3.0\prog\FPP\mcu03D9.fpp
is used .

Is there a limitation in the fpp-file that places the eeprom at
address 0x2000?

I have only manage to load constants into eeprom at address 0x2000.
When my load file containing eeprom constants on address 0x800
in the eeprom will remain empty after loading.

If there is a restricton in the fpp-file. How do I change the fpp-
file?

Where can I find the source code to the fpp-file?

Thanks in advance,
Jan-Olov From




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


Re: Using eeprom constants in CW - Gilles Blanquin - Apr 2 4:59:00 2004


Hi.

The FLASH/EEPROM driver cares about the INITEE register value and EEPROM
location. So if you move it, and can flash and erase it where it was moved.
This was a must, as usually the eeprom is partially or totally hidden under
chip registers and onchip ram.

You can try this if you want:
Execute a WB command from the Command window to set INITEE register.
Then open the NMVC dialog. You will see that the EEPROM location range changes.
Remind that if the reset the chip after the command is played, the eeprom
turns back to default location.

Regards,

Gilles At 10:37 AM 4/2/2004, you wrote:
>Hi,
>I use codewarrior v3.0 in my project (processor = HCS12 DG128).
>My intention is to map the eeprom to addresss 0x800.
>
>The Hiwave-debugger uses the s-record fpp-file to support
>eeprom-writing (I believe) during program loading.
>In my case the fpp file CW12_V3.0\prog\FPP\mcu03D9.fpp
>is used .
>
>Is there a limitation in the fpp-file that places the eeprom at
>address 0x2000?
>
>I have only manage to load constants into eeprom at address 0x2000.
>When my load file containing eeprom constants on address 0x800
>in the eeprom will remain empty after loading.
>
>If there is a restricton in the fpp-file. How do I change the fpp-
>file?
>
>Where can I find the source code to the fpp-file?
>
>Thanks in advance,
>Jan-Olov From >
>--------------------------------------------------------To learn more
>about Motorola Microcontrollers, please visit
>http://www.motorola.com/mcu
>o learn more about Motorola Microcontrollers, please visit
>http://www.motorola.com/mcu
>
>Yahoo! Groups Links



______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


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

Re: Using eeprom constants in CW - jfrom90 - Apr 2 6:27:00 2004


Thank you for your reply,
you are right about that I can do this by the wb-command.
The NVMC window was together with the log in the command window
the clue to see that someone prefers to have eeprom at 0x2000.

It is also true for HCS DG128 that the eeprom is totally hidden
after a reset. For that reason I can see the need for handling
the INITEE in the FLASH/EEPROM driver.

Is the INITEE hard coded in the FLASH/EEPROM driver (the .fpp-file)?

How do I generate a new driver?

Can we agree that it should be the decision of my project
to have the eeprom at address 0x800?

I don't like the idea to do some kind of workaround to fix
loading of eeprom at 0x2000.

By the way I noticed that the fpp filename should be

CW12_V3.0\prog\FPP\mcu03DC.fpp for HCS12 DG128. Kind regards Jan-Olov From

--- In , Gilles Blanquin <gblanquin@m...> wrote:
>
> Hi.
>
> The FLASH/EEPROM driver cares about the INITEE register value and
EEPROM
> location. So if you move it, and can flash and erase it where it
was moved.
> This was a must, as usually the eeprom is partially or totally
hidden under
> chip registers and onchip ram.
>
> You can try this if you want:
> Execute a WB command from the Command window to set INITEE register.
> Then open the NMVC dialog. You will see that the EEPROM location
range changes.
> Remind that if the reset the chip after the command is played, the
eeprom
> turns back to default location.
>
> Regards,
>
> Gilles > At 10:37 AM 4/2/2004, you wrote:
> >Hi,
> >I use codewarrior v3.0 in my project (processor = HCS12 DG128).
> >My intention is to map the eeprom to addresss 0x800.
> >
> >The Hiwave-debugger uses the s-record fpp-file to support
> >eeprom-writing (I believe) during program loading.
> >In my case the fpp file CW12_V3.0\prog\FPP\mcu03D9.fpp
> >is used .
> >
> >Is there a limitation in the fpp-file that places the eeprom at
> >address 0x2000?
> >
> >I have only manage to load constants into eeprom at address 0x2000.
> >When my load file containing eeprom constants on address 0x800
> >in the eeprom will remain empty after loading.
> >
> >If there is a restricton in the fpp-file. How do I change the fpp-
> >file?
> >
> >Where can I find the source code to the fpp-file?
> >
> >Thanks in advance,
> >Jan-Olov From
> >
> >
> >
> >--------------------------------------------------------To learn
more
> >about Motorola Microcontrollers, please visit
> >http://www.motorola.com/mcu
> >o learn more about Motorola Microcontrollers, please visit
> >http://www.motorola.com/mcu
> >
> >Yahoo! Groups Links
> >
> >
> >
>




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

Re: Re: Using eeprom constants in CW - Gilles Blanquin - Apr 2 7:12:00 2004


Hi.

The driver relocates automatically (for debugging only, of course) the
EEPROM to $2000 (writing 0x21 to INITEE) if ((INITEE & 0xFE) == 0).
Indeed, there is no memory overlap at $2000 at chip reset. So it makes easy
eeprom programming without interfering with the Registers block.

Anytime you reset the chip/debugger, the eeprom goes back to default range
0-7FF.

Up to your application to map the eeprom wherever it wants. The driver
remapping is only done for programming facilities.

You are right about the driver and path. However, if you edit the fpp file,
you will notice some S-Record section. Algorithms there are not intended to
be modified by users. However, you can always contact the Support team if
you think that the fpp file should be modified.

For sure, the NVMC/Flash programming interface will not be able to map the
entire eeprom if it's located at its default address 0-7FF, especially with
the 0-3FF range below the Registers block.

If know you want to program the eeprom to a different place, first use a WB
command to set INITEE then reopen the NVMC dialog. The driver will display
the new eeprom address range. (INITEE & 0xFE) != 0 => no eeprom auto
relocation.

I hope this will help.

Regards,

Gilles At 01:27 PM 4/2/2004, you wrote:

>Thank you for your reply,
>you are right about that I can do this by the wb-command.
>The NVMC window was together with the log in the command window
>the clue to see that someone prefers to have eeprom at 0x2000.
>
>It is also true for HCS DG128 that the eeprom is totally hidden
>after a reset. For that reason I can see the need for handling
>the INITEE in the FLASH/EEPROM driver.
>
>Is the INITEE hard coded in the FLASH/EEPROM driver (the .fpp-file)?
>
>How do I generate a new driver?
>
>Can we agree that it should be the decision of my project
>to have the eeprom at address 0x800?
>
>I don't like the idea to do some kind of workaround to fix
>loading of eeprom at 0x2000.
>
>By the way I noticed that the fpp filename should be
>
>CW12_V3.0\prog\FPP\mcu03DC.fpp for HCS12 DG128. >Kind regards Jan-Olov From
>
>--- In , Gilles Blanquin <gblanquin@m...> wrote:
> >
> > Hi.
> >
> > The FLASH/EEPROM driver cares about the INITEE register value and
>EEPROM
> > location. So if you move it, and can flash and erase it where it
>was moved.
> > This was a must, as usually the eeprom is partially or totally
>hidden under
> > chip registers and onchip ram.
> >
> > You can try this if you want:
> > Execute a WB command from the Command window to set INITEE register.
> > Then open the NMVC dialog. You will see that the EEPROM location
>range changes.
> > Remind that if the reset the chip after the command is played, the
>eeprom
> > turns back to default location.
> >
> > Regards,
> >
> > Gilles
> >
> >
> > At 10:37 AM 4/2/2004, you wrote:
> > >Hi,
> > >I use codewarrior v3.0 in my project (processor = HCS12 DG128).
> > >My intention is to map the eeprom to addresss 0x800.
> > >
> > >The Hiwave-debugger uses the s-record fpp-file to support
> > >eeprom-writing (I believe) during program loading.
> > >In my case the fpp file CW12_V3.0\prog\FPP\mcu03D9.fpp
> > >is used .
> > >
> > >Is there a limitation in the fpp-file that places the eeprom at
> > >address 0x2000?
> > >
> > >I have only manage to load constants into eeprom at address 0x2000.
> > >When my load file containing eeprom constants on address 0x800
> > >in the eeprom will remain empty after loading.
> > >
> > >If there is a restricton in the fpp-file. How do I change the fpp-
> > >file?
> > >
> > >Where can I find the source code to the fpp-file?
> > >
> > >Thanks in advance,
> > >Jan-Olov From
> > >
> > >
> > >
> > >--------------------------------------------------------To learn
>more
> > >about Motorola Microcontrollers, please visit
> > >http://www.motorola.com/mcu
> > >o learn more about Motorola Microcontrollers, please visit
> > >http://www.motorola.com/mcu
> > >
> > >Yahoo! Groups Links
> > >
> > >
> > >
> > >
>
>--------------------------------------------------------To learn more
>about Motorola Microcontrollers, please visit
>http://www.motorola.com/mcu
>o learn more about Motorola Microcontrollers, please visit
>http://www.motorola.com/mcu
>
>Yahoo! Groups Links




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