Freescale Semiconductor Microcontrollers - Manual (Page 712)

Flash Programming
NVMC Commands
712 Microcontrollers Debugger Manual
FLASH LOADCONTEX restores current buffer content into the MCU SRAM.
FLASH OVLBACKUP backups application code overlap with programming runtime/
algorithm (RAM preset for debugging). Execute the command before loading the
application/file.
FLASH OVLRESTORE restores/installs (writes in RAM) the application code overlap
with programming runtime/algorithm. Execute the command after the last FLASH
command.
FLASH PROTOCOLON displays the Flash programmer debug protocol.
FLASH PROTOCOLOFF stops displaying the Flash programmer debug protocol.
FLASH SKIPSTATUSON skips the Flash programmer device Non-Volatile Memory
blocks diagnostic. You can use this command to speed up project application loading and
programming from the IDE debug run. The Flash programmer does NOT verify that
blocks are programmed or erased.
FLASH SKIPSTATUSOFF removes the SKIPSTATUSON mode and therefore
diagnostics are performed again.
FLASH NVMFREQUENCY <frequency in Hz> specifies the Non-Volatile Memory
programming frequency in Hertz; typically the device bus speed after reset. When used,
the Flash programmer does not try to evaluate this speed and the debugger gains 2-3
seconds at application loading time. A value of “0” enables the speed detection.
FLASH NVMIF2RELOCATE Command not relevant for HCS08 devices.
FLASH NVMIF2WORKSPACE Command not relevant for HCS08 devices.
FLASH UNSECURE After device mass erasing, the Flash programmer automatically
programs the device security byte to the “Unsecure” state to enable code debugging
(default behavior).
FLASH NOUNSECURE After device mass erasing, the Flash programmer does not
program the device security byte to the “Unsecured” state. The command must be placed
in a Startup command file, to be executed before any erase operation.
TIP Use this command when the user application contains the code to program the
device security byte. This guarantees that no over-programming is performed on
the Flash security byte cell.
CAUTION If the device security byte is not programmed to the “Unsecured” state,
after the device is reset, debugging is no longer possible until the next
mass erase and security byte is programmed to “Unsecured” state.
[ <blockNo>]
blockNo is a list of Flash block/module numbers, according to this syntax:
blockNo = {number["-"number][","]}