Preliminary C8051F120/1/2/3 C8051F124/5/6/7 - KEMT FEI TUKE

More documents

Recommendations

Info

C8051F120/1/2/3 C8051F124/5/6/7 Preliminary tates updating data without wasting program memory or RAM space. The 128-byte sectors are double-mapped over the 128k byte FLASH memory for MOVC reads and MOVX writes only; their addresses range from 0x00 to 0x7F and from 0x80 to 0xFF (see Figure 15.2). To access the 128-byte sectors, the SFLE bit in PSCTL must be set to logic 1. Code execution from the 128-byte Scratchpad areas is not possible. The 128-byte sectors can be erased individually, or both at the same time. To erase both sectors simultaneously, the address 0x0400 should be targeted during the erase operation with SFLE set to ‘1’. See Figure 15.1 for the memory map under different COBANK and SFLE settings. Figure 15.1. FLASH Memory Map for MOVC Read and MOVX Write Operations SFLE = 0 SFLE = 1 Internal COBANK = 0 COBANK = 1 COBANK = 2 COBANK = 3 Address 0xFFFF Bank 0 Bank 1 Bank 2 Bank 3 Undefined 0x8000 0x7FFF Bank 0 Bank 0 Bank 0 Bank 0 Scratchpad Areas (2) 0x00FF 0x0000 15.1.2. Erasing FLASH Pages From Software When erasing FLASH memory, an entire page is erased (all bytes in the page are set to 0xFF). The 128k byte FLASH memory is organized in 1024-byte pages. The 256 bytes of Scratchpad area (addresses 0x20000 to 0x200FF) consists of two 128 byte pages. To erase any FLASH page, the FLWE, PSWE, and PSEE bits must be set to ‘1’, and a byte must be written using a MOVX instruction to any address within that page. The following is the recommended procedure for erasing a FLASH page from software: Step 1. Disable interrupts. Step 2. If erasing a page in Bank 1, Bank 2, or Bank 3, set the COBANK bits (PSBANK.5-4) for the appropriate bank. Step 3. If erasing a page in the Scratchpad area, set the SFLE bit (PSCTL.2). Step 4. Set FLWE (FLSCL.0) to enable FLASH writes/erases via user software. Step 5. Set PSEE (PSCTL.1) to enable FLASH erases. Step 6. Set PSWE (PSCTL.0) to redirect MOVX commands to write to FLASH. Step 7. Use the MOVX instruction to write a data byte to any location within the page to be erased. Step 8. Clear PSEE to disable FLASH erases. Step 9. Clear the PSWE bit to redirect MOVX commands to the XRAM data space. Step 10. Clear the FLWE bit, to disable FLASH writes/erases. Step 11. If erasing a page in the Scratchpad area, clear the SFLE bit. Step 12. Re-enable interrupts. Page 174 DS008-0.8-AUG02 © 2002 Cygnal Integrated Products, Inc.
Preliminary C8051F120/1/2/3 C8051F124/5/6/7 15.1.3. Writing FLASH Memory From Software Bytes in FLASH memory can be written one byte at a time, or in small blocks. The CHBLKW bit in register CCH0CN (Figure 16.4) controls whether a single byte or a block of bytes is written to FLASH during a write operation. When CHBLKW is cleared to ‘0’, the FLASH will be written one byte at a time. When CHBLKW is set to ‘1’, the FLASH will be written in blocks of four bytes for addresses in code space, or blocks of two bytes for addresses in the Scratchpad area. Block writes are performed in the same amount of time as single byte writes, which can save time when storing large amounts of data to FLASH memory. For single-byte writes to FLASH, bytes are written individually, and the FLASH write is performed after each MOVX write instruction. The recommended procedure for writing FLASH in single bytes is: Step 1. Disable interrupts. Step 2. Clear CHBLKW (CCH0CN.0) to select single-byte write mode. Step 3. If writing to bytes in Bank 1, Bank 2, or Bank 3, set the COBANK bits (PSBANK.5-4) for the appropriate bank. Step 4. If writing to bytes in the Scratchpad area, set the SFLE bit (PSCTL.2). Step 5. Set FLWE (FLSCL.0) to enable FLASH writes/erases via user software. Step 6. Set PSWE (PSCTL.0) to redirect MOVX commands to write to FLASH. Step 7. Use the MOVX instruction to write a data byte to the desired location (repeat as necessary). Step 8. Clear the PSWE bit to redirect MOVX commands to the XRAM data space. Step 9. Clear the FLWE bit, to disable FLASH writes/erases. Step 10. If writing to bytes in the Scratchpad area, clear the SFLE bit. Step 11. Re-enable interrupts. For block FLASH writes, the FLASH write procedure is only performed after the last byte of each block is written with the MOVX write instruction. When writing to addresses located in any of the four code banks, a FLASH write block is four bytes long, from addresses ending in 00b to addresses ending in 11b. Writes must be performed sequentially (i.e. addresses ending in 00b, 01b, 10b, and 11b must be written in order). The FLASH write will be performed following the MOVX write that targets the address ending in 11b. When writing to addresses located in the FLASH Scratchpad area, a FLASH block is two bytes long, from addresses ending in 0b to addresses ending in 1b. The FLASH write will be performed following the MOVX write that targets the address ending in 1b. If any bytes in the block do not need to be updated in FLASH, they should be written to 0xFF. The recommended procedure for writing FLASH in blocks is: Step 1. Disable interrupts. Step 2. Set CHBLKW (CCH0CN.0) to select block write mode. Step 3. If writing to bytes in Bank 1, Bank 2, or Bank 3, set the COBANK bits (PSBANK.5-4) for the appropriate bank. Step 4. If writing to bytes in the Scratchpad area, set the SFLE bit (PSCTL.2). Step 5. Set FLWE (FLSCL.0) to enable FLASH writes/erases via user software. Step 6. Set PSWE (PSCTL.0) to redirect MOVX commands to write to FLASH. Step 7. Use the MOVX instruction to write data bytes to the desired block. The data bytes must be written sequentially, and the last byte written must be the high byte of the block (see text for details, repeat as necessary). Step 8. Clear the PSWE bit to redirect MOVX commands to the XRAM data space. Step 9. Clear the FLWE bit, to disable FLASH writes/erases. Step 10. If writing to bytes in the Scratchpad area, clear the SFLE bit. Step 11. Re-enable interrupts. © 2002 Cygnal Integrated Products, Inc. DS008-0.8-AUG02 Page 175
Page 1 and 2:
Preliminary C8051F120/1/2/3 C8051F1
Page 3 and 4:
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
© 2002 Cygnal Integrated Products,
Page 45 and 46:
© 2002 Cygnal Integrated Products,
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124: Preliminary C8051F120/1/2/3 C8051F1
Page 173: Preliminary C8051F120/1/2/3 C8051F1
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
show all

Preliminary C8051F120/1/2/3 C8051F124/5/6/7 - KEMT FEI TUKE

Create successful ePaper yourself

Delete template?

Save as template?