Reply by bharath kumar February 9, 20042004-02-09
Hi Robert,
When u have mapped the EEPROM to 0x4000 the tables
can be found at the same address. So what u observed
was coorect and u will not find any tables in 0x400 to
0x3fff. you also please note that the EEPROM can be
mapped in 4K blocks only.

Regards
Bharath

--- "Robert L. Harris" <> wrote:
> The calibration tables have grown to exceed the 3k
> of EEprom normally
> visible with the "normal" mapping. Until now,
> default tables have been
> placed between 0x400 and 0xfff and programming the
> chip with the default
> tables and the code was easy.
>
> (Default tables are included to get the unit running
> sufficiently well that
> the ATE can program it with final values during
> calibration prior to
> shipment)
>
> I moved the EEprom to 0x4000 (previously unused).
> When I did that, the code
> changed appropriately and almost everything is cool.
> BUT the tables go into
> flash at 0x4000, not into the EEprom so the EEprom
> appears to be blank to
> the program when the program starts and sets the
> INITEE register.
>
> I have poured over the manuals to find a way using
> CodeWarrior 2 to remap
> the EEprom prior to the loading of the S19 file so
> it will become programmed
> by the debugger interface and cannot find the
> necessary information. The S19
> file expects to write the calibration data to 0x4000
> - 0x4fff.
>
> Can someone point me to how to achieve what I need
> to do?
>
> Thanks a bunch.
>
> Bob Harris >
> ------------------------ Yahoo! Groups Sponsor
--------------------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 >


__________________________________



Reply by Robert L. Harris February 7, 20042004-02-07
The calibration tables have grown to exceed the 3k of EEprom normally
visible with the "normal" mapping. Until now, default tables have been
placed between 0x400 and 0xfff and programming the chip with the default
tables and the code was easy.

(Default tables are included to get the unit running sufficiently well that
the ATE can program it with final values during calibration prior to
shipment)

I moved the EEprom to 0x4000 (previously unused). When I did that, the code
changed appropriately and almost everything is cool. BUT the tables go into
flash at 0x4000, not into the EEprom so the EEprom appears to be blank to
the program when the program starts and sets the INITEE register.

I have poured over the manuals to find a way using CodeWarrior 2 to remap
the EEprom prior to the loading of the S19 file so it will become programmed
by the debugger interface and cannot find the necessary information. The S19
file expects to write the calibration data to 0x4000 - 0x4fff.

Can someone point me to how to achieve what I need to do?

Thanks a bunch.

Bob Harris