EmbeddedTargetforMotorolaMPC555(5xx)–R14.docVIP

Embedded Target for Motorola MPC555 (5xx) – R14 Targeting External Flash TOC \o 1-3 \h \z \u Introduction 1 FLEN and Chip Select Configuration 1 Target Board Configuration 2 Phytec MPC555 Example 2 Axiom MPC564 Example 2 Debugger Configuration 2 SingleStep Example 2 CodeWarrior Example 3 Bootcode Configuration 3 Downloading to the External Flash 3 External Flash on the Phytec MPC555 Development Board 4 External Flash on the Axiom MPC555 Development Board 4 Installing the Bootcode S19 4 Installing the Application Code S19 5 Combining the Bootcode and Application Code S19’s 5 Tested Platforms 5 Introduction This application note describes how to target the External Flash (rather than Internal Flash) memory of your MPC5xx board. Both the bootcode and application code will be placed in External Flash, and Internal Flash will not be used. It should be noted that memory accesses to External Flash are slower than those to Internal Flash. This means that an application may incur a performance penalty when executed from External Flash. The configuration changes required for targeting External Flash memory require familiarity with the MPC5xx hardware, and with your particular development board. FLEN and Chip Select Configuration The Flash Enable bit (FLEN) effectively enables / disables the Internal Flash of the MPC5xx: FLEN=0 ? On-chip Flash disabled, internal accesses to flash address space are mapped to external memory FLEN=1 ? On-chip Flash enabled The chip select settings are also important when configuring a target to use External Flash. In this document, we shall generally assume that: External Flash is on Chip Select 0 (CS0) (mapped to address 0x0) External RAM is on Chip Select 1 (CS1) (mapped to address 0x800000) Target Board Configuration Your target board will likely need some jumper configuration changes in order to disable the Internal Flash and enable the External Flash memory. Additionally, jumpers may