|
|||||||||||
Technical Support On-Line Manuals µVision User's Guide About µVision User Interface Creating Applications Utilities Debugging Debug Commands Debug Functions Simulation Flash Programming Flash Download Configuration ULINK Configuration Pre-Download Scripts BUS Configuration Program Objects Flash Algorithms HEX Files Dialogs Example Programs Command Line Appendix |
BUS ConfigurationThe BUS can be configured using predefined functions (for example, _WBYTE or _WDWORD) that write to the target memory. Use these functions in pre-download scripts. Some devices require a BUS configuration prior to accessing attached devices. Typically, this is true for external Flash ROM devices. For example: _WDWORD(0xFFE00000, 0x20003CE3); // BCFG0: Flash Bus Configuration _WDWORD(0xE002C014, 0x0E6001E4); // PINSEL2: CS0, OE, WE, BLS0..3 Functions can use the Configuration Wizard syntax to create a menu-driven configuration file: /***********************************************************************/ /* FLASH.INI: Flash Initialization File */ /***********************************************************************/ //*** Use Configuration Wizard in Context Menu *** FUNC void Setup (void) { // External Memory Controller (EMC) // Bank Configuration 0 (BCFG0) // IDCY: Idle Cycles (0-15) // WST1: Wait States 1 (0-31) // WST2: Wait States 2 (0-31) // RBLE: Read Byte Lane Enable // WP: Write Protect // BM: Burst ROM // MW: Memory Width 0=8-bit 1=16-bit // 2=32-bit 3=Reserved // _WDWORD(0xFFE00000, 0x20003CE3); // BCFG0: Flash Bus Configuration _WDWORD(0xE002C014, 0x0E6001E4); // PINSEL2: CS0, OE, WE, BLS0..3 // D0..31, A2..23, JTAG } Setup(); // Setup for Flash | ||||||||||
|
Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.