Slide 1
Slide 2
Slide 3
Slide 4
Slide 5
Slide 6
Slide 7
Slide 8
Slide 9
Slide 10
Slide 11
Slide 12
Slide 13
Slide 14
Slide 15
Slide 16
Slide 17
Slide 18
Slide 19
Slide 20
Slide 21
Slide 22
Slide 23
Slide 24
Slide 25
Slide 26
Slide 27
Slide 28
Slide 29
Slide 30
Slide 31
Slide 32
Slide 33
Slide 34
Slide 35
Slide 36
Slide 37
Slide 38
Slide 39
Slide 40
Slide 41
Slide 42
Slide 43
Slide 44
Slide 45
Slide 46
Slide 47
Slide 48
Slide 49
Slide 50
Slide 51
Slide 52
Slide 53
Slide 54
Slide 55
Slide 56
Slide 57
Slide 58
Product List
Simply put, the flash accelerator attempts to have the next Cortex-M3 instruction that will be needed in its latches in time to prevent CPU fetch stalls. Internally, the flash accelerator includes an array of eight 128b buffers to store both instructions and data in a configurable manner. The operations within this module are completely transparent to the end user. Programming this block is achieved by the “FLASHCFG” register alone. After reset, the flash accelerator defaults to the enabled state. Software can turn memory access acceleration on or off, or change the acceleration configuration at any time. Following reset, the flash access timing is also set to a default value of 6 CPU clocks. This is considered as a “safe setting” and will work for any condition. As an illustration, if the application needs to execute at 20MHz, the timing can be set to 1 CPU clock and if the application needs to execute at 100MHz, the timing can be set to 5 CPU clocks. Flash programming operations are not controlled by the flash accelerator, but are handled as a separate function.
PTM Published on: 2011-11-02