Datasheet

ManualsBrandsNXP SEMICONDUCTORS ManualsMicrocontrollers, Microprocessors & QuartzesEmbedded microcontroller HVQFN 32 (7x7) 32-Bit 50 MHz I/O number 28

441

442

443

444

445

446

447

448

449

450

User manual Rev. 12.3 — 10 June 2014 441 of 547

NXP Semiconductors

UM10398

Chapter 26: LPC111x/LPC11Cxx Flash programming firmware

26.7.2 Copy RAM to flash (IAP)

See Section 26.5.4 for limitations on the write-to-flash process.

Table 396. IAP Prepare sector(s) for write operation command

Command Prepare sector(s) for write operation

Input Command code: 50 (decimal)

Param0: Start Sector Number

Param1: End Sector Number (should be greater than or equal to start sector

number).

Status Code CMD_SUCCESS |

BUSY |

INVALID_SECTOR

Result None

Description This command must be executed before executing "Copy RAM to flash" or "Erase

Sector(s)" command. Successful execution of the "Copy RAM to flash" or "Erase

Sector(s)" command causes relevant sectors to be protected again. The boot

sector can not be prepared by this command. To prepare a single sector use the

same "Start" and "End" sector numbers.

Table 397. IAP Copy RAM to flash command

Command Copy RAM to flash

Input Command code: 51 (decimal)

Param0(DST): Destination flash address where data bytes are to be written. This

address should be a 256 byte boundary.

Param1(SRC): Source RAM address from which data bytes are to be read. This

address should be a word boundary.

Param2: Number of bytes to be written. Should be 256 | 512 | 1024 | 4096.

Param3: System Clock Frequency (CCLK) in kHz.

Remark: In parts with less than 4 kB SRAM, Param2 is limited to 1024 (see

Table 3

status code CMD_SUCCESS |

SRC_ADDR_ERROR (Address not a word boundary) |

DST_ADDR_ERROR (Address not on correct boundary) |

SRC_ADDR_NOT_MAPPED |

DST_ADDR_NOT_MAPPED |

COUNT_ERROR (Byte count is not 256 | 512 | 1024 | 4096) |

SECTOR_NOT_PREPARED_FOR_WRITE_OPERATION |

BUSY

Result None

Description This command is used to program the flash memory. The affected sectors should

be prepared first by calling "Prepare Sector for Write Operation" command. The

affected sectors are automatically protected again once the copy command is

successfully executed. The boot sector can not be written by this command.