UM10139

Philips SemiconductorsVolume 1UM10139Chapter 21: Flash Memory21.4.8 ISP command abortCommands can be aborted by sending the ASCII control character "ESC". This feature isnot documented as a command under "ISP Commands" section. Once the escape code isreceived the ISP command handler waits for a new command.21.4.9 Interrupts during ISPThe boot block interrupt vectors located in the boot block of the flash are active after anyreset.21.4.10 Interrupts during IAPThe on-chip flash memory is not accessible during erase/write operations. When the userapplication 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 inRAM and that the interrupt handlers reside in RAM, before making a flash erase/write IAPcall. The IAP code does not use or disable interrupts.21.4.11 RAM used by ISP command handlerISP commands use on-chip RAM from 0x4000 0120 to 0x4000 01FF. The user could usethis area, but the contents may be lost upon reset. Flash programming commands use thetop 32 bytes of on-chip RAM. The stack is located at RAM top − 32. The maximum stackusage is 256 bytes and it grows downwards.21.4.12 RAM used by IAP command handlerFlash programming commands use the top 32 bytes of on-chip RAM. The maximum stackusage in the user allocated stack space is 128 bytes and it grows downwards.21.4.13 RAM used by RealMonitorThe RealMonitor uses on-chip RAM from 0x4000 0040 to 0x4000 011F. he user could usethis area if RealMonitor based debug is not required. The Flash boot loader does notinitialize the stack for RealMonitor.© Koninklijke Philips Electronics N.V. 2005. All rights reserved.User manual Rev. 01 — 15 August 2005 294