Datasheet

3–5
3.5 Writing Data Into the EPROM
When data is written into the EPROM address range, software code is written into RAM locations 214h to
23Dh. All addresses 1000h or higher are assumed to be EPROM. After the write operation is completed,
the code in the RAM is no longer needed. The code is written into RAM when a write into the EPROM address
range is performed. Ensure that the data in these locations are not needed when the EPROM write code
is temporarily loaded into those locations.
A write into EPROM can be done when an application program is executed, or when the monitor is active.
For example, when the mx[n] command is executed:
Available RAM for
User Application
RAM Area Always Reserved
for ROM Monitor
214h
212h
200h
RAM Area Always Reserved
for ROM Monitor
212h
214h
200h
Temporary
Burn Routine
23Dh
23Eh
Available RAM for
User Application
No write to EPROM active
Figure 3–4. Temporary Burn Routine in the MSP430x32x RAM Area
User application data for the MSP430X33x family should be located within the RAM area (from 200h to
5FFh). The locations used statically (200h to 214h), and dynamically (stack) by the Monitor Program limit
the size of the available RAM.
NOTE:
The Identification Bit Pattern defines if the monitor code or a user’s code (program) is
executed after a power-up or hardware reset (PUC). See Section 5.2. The Temporary
Burn Routine user’s addresses are allocated for the EPROM burn routine which must
run in the RAM. When data is written into the EPROM (program memory), code in the
EPROM can not be executed. Therefore, the burn program has to be in the RAM (loaded
from the EPROM so it can be executed).