Isp Command Abort; Interrupts During Isp; Interrupts During Iap; Ram Used By Isp Command Handler - Philips LPC2101 User Manual

Philips Semiconductors
Volume 1

19.4.8 ISP command abort

Commands can be aborted by sending the ASCII control character "ESC". This feature is
not documented as a command under "ISP Commands" section. Once the escape code is
received the ISP command handler waits for a new command.

19.4.9 Interrupts during ISP

The boot block interrupt vectors located in the boot block of the flash are active after any
reset.

19.4.10 Interrupts during IAP

The on-chip flash memory is not accessible during erase/write operations. When the user
application code starts executing the interrupt vectors from the user flash area are active.
The user should either disable interrupts, or ensure that user interrupt vectors are active in
RAM and that the interrupt handlers reside in RAM, before making a flash erase/write IAP
call. The IAP code does not use or disable interrupts.

19.4.11 RAM used by ISP command handler

ISP commands use on-chip RAM from 0x4000 0120 to 0x4000 01FF. The user could use
this area, but the contents may be lost upon reset. Flash programming commands use the
top 32 bytes of on-chip RAM. The stack is located at RAM top − 32. The maximum stack
usage is 256 bytes and it grows downwards.

19.4.12 RAM used by IAP command handler

Flash programming commands use the top 32 bytes of on-chip RAM. The maximum stack
usage in the user allocated stack space is 128 bytes and it grows downwards.

19.4.13 RAM used by RealMonitor

The RealMonitor uses on-chip RAM from 0x4000 0040 to 0x4000 011F. he user could use
this area if RealMonitor based debug is not required. The Flash boot loader does not
initialize the stack for RealMonitor.

User manual

Rev. 01 — 12 January 2006
UM10161
Chapter 19: Flash memory
© Koninklijke Philips Electronics N.V. 2006. All rights reserved.
232