1. Manuals
  2. Brands
  3. Freescale Semiconductor Manuals
  4. Motherboard
  5. ColdFire MCF5275
  6. User manual

Freescale Semiconductor ColdFire MCF5275 User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
MCF5275EVB User's Manual
Devices Supported:
MCF5275
MCF5275L
MCF5274
MCF5274L
MCF5275EVBUM
Rev. 1.1
11/2008

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ColdFire MCF5275 and is the answer not in the manual?

Questions and answers

Related Manuals for Freescale Semiconductor ColdFire MCF5275

Summary of Contents for Freescale Semiconductor ColdFire MCF5275

  • Page 1 MCF5275EVB User’s Manual Devices Supported: MCF5275 MCF5275L MCF5274 MCF5274L MCF5275EVBUM Rev. 1.1 11/2008...
  • Page 2 Freescale Semiconductor does not convey any license under its patent rights nor the rights of others. Freescale Semiconductor products are not designed, intended, or authorized for use as components in systems intended for surgical implant into the body, or...
  • Page 3 EMC Information on M5275EVB This product as shipped from the factory with associated power supplies and cables, has been tested and meets with requirements of EN5022 and EN 50082-1: 1998 as a CLASS A product. This product is designed and intended for use as a development platform for hardware or software in an educational or professional laboratory.
  • Page 4 WARNING This board generates, uses, and can radiate radio frequency energy and, if not installed properly, may cause interference to radio communications. As temporarily permitted by regulation, it has not been tested for compliance with the limits for class a computing devices pursuant to Subpart J of Part 15 of FCC rules, which are designed to provide reasonable protection against such interference.

  • Page 5: Table Of Contents

    CONTENTS Paragraph Page Title Number Number Chapter 1 M5275EVB Introduction MCF5275 Microprocessor .................. 1-3 System Memory ....................1-6 1.2.1 External Flash ....................1-6 1.2.2 SDRAM ......................1-7 1.2.3 ASRAM ......................1-7 1.2.4 Internal SRAM....................1-7 1.2.5 M5275EVB Memory Map................1-7 1.2.5.1 Reset Vector Mapping ................
  • Page 6 CONTENTS Paragraph Page Title Number Number 2.2.1 Unpacking....................... 2-3 2.2.2 Preparing the Board for Use ................2-3 2.2.3 Providing Power to the Board................. 2-3 2.2.4 Power Switch (SW3) ..................2-4 2.2.5 Power Status LEDs and Fuse................2-4 2.2.6 Selecting Terminal Baud Rate ................ 2-5 2.2.7 The Terminal Character Format ..............
  • Page 7 CONTENTS Paragraph Page Title Number Number Appendix C M5275EVB BOM M5275EVB BOM....................C-1 Freescale Contents...
  • Page 8 CONTENTS Paragraph Page Title Number Number M5275EVB User’s Manual Freescale...

  • Page 9: M5275Evb Introduction

    Chapter 1 M5275EVB Introduction This document details the setup and configuration of the ColdFire M5275EVB evaluation board (hereafter referred to as the EVB). The EVB is intended to provide a mechanism for easy customer evaluation of the MCF5274, MCF574L, MCF5275, and MCF5275L ColdFire microprocessors and to facilitate hardware and software development.
  • Page 10 • Motorola MCF5275 Microprocessor (166 MHz max core frequency) • External Clock source: 25MHz • Operating temperature: 0°C to +70°C • Power requirement: 6 – 14V DC @ 1A Typical • Power output: 5V, 3.3V, 2.5V and 1.5V regulated supplies •...

  • Page 11: Mcf5275 Microprocessor

    MCF5275 Microprocessor 2x Ethernet 2x RJ-45 26-pin Debug Header Connector Transceiver ColdFire MCF5275 RS-232 DB-9 25 MHz Transceivers (3) Connectors (3) Osc. USB PHY Connector DDR SDRAM 16 MBytes Flash 2-4 MBytes ASRAM 1 MByte (4) 60 pin Daughter Card Expansion Connectors Figure 1-1.
  • Page 12 MCF5275 Microprocessor • Three universal asynchronous receiver/transmitters (UARTs) with DMA support • Inter-integrated circuit (I C) bus controller • Queued serial peripheral interface (QSPI) module • Hardware cryptography accelerator (optional) — Random number generator — DES/3DES/AES block cipher engine — MD5/SHA-1/HMAC accelerator •...
  • Page 13 MCF5275 Microprocessor QSPI CHIP I2C_SDA (To/From SRAM backdoor) SELECTS I2C_SCL UnTXD UnRXD UnRTS INTC0 INTC1 Arbiter UnCTS DTnOUT DTnIN FAST ETHERNET FEC0 (To/From PADI) CONTROLLER FEC1 (FEC0) UART UART UART QSPI PWMn FAST ETHERNET SDRAMC (To/From PADI) CONTROLLER D[31:16] (FEC1) A[23:0] DTIM DTIM...

  • Page 14: System Memory

    System Memory System Memory The following diagram shows the external memory implementation on the M5275EVB. Buffers MCF5275 ASRAM Data 1MByte Address Control Flash DDR SDRAM (1M x 16) (16MBytes) (2M x 16) Expansion Connectors Figure 1-3. External Memory Scheme NOTE The external bus interface signals to the external ASRAM and Flash are buffered.

  • Page 15: Sdram

    System Memory should use caution to avoid this situation. The M5275EVB dBUG debugger/monitor firmware is programmed into the lower sectors of Flash (0xFFE0_0000 to 0xFFE3_FFFF for 2 MBytes of Flash or 0xFFC0_0000 to 0xFFC3_FFFF for 4 MBytes of Flash). When U11 is fitted on the EVB, jumper 3 (JP3) provides an alternative hardware mechanism for write protection.

  • Page 16: Reset Vector Mapping

    System Memory Table 1-2 shows the M5275EVB memory map. Table 1-2. The M5275EVB Default Memory Map Address Range Chip Select Signal and Device 0x0000_0000 - 0x00FF_FFFF SD_CS0 16 MByte SDRAM (U7) 0x2000_0000 - 0x2000_FFFF — 64 KBytes Internal SRAM 0x3000_0000 - 0x300F_FFFF 512 KByte External ASRAM (not fitted) (U1) 0xFFE0_0000 - 0xFFFF_FFFF 2 MBytes External Flash (U11)

  • Page 17: Support Logic

    Support Logic Support Logic 1.3.1 Reset Logic Reset occurs during power-on or via assertion of the signal RESET which causes the MCF5275 to reset. RESET is triggered by the reset switch (SW5) which resets the entire processor/system. The dBUG Firmware configures the MCF5275 microprocessor internal resources during initialization.
  • Page 18 Support Logic Table 1-7. SW6-[7:5] Chip Mode RCON SW6-5 SW6-6 SW6-7 Mode (SW6-1) Master mode Reserved Reserved Reserved Reserved Master mode Table 1-8. SW6-[9:8] Boot Device RCON SW6-8 SW6-9 Boot Device (SW6-1) External (16-bit) Reserved Reserved External (8-bit) External (16-bit) Table 1-9.

  • Page 19: Clock Circuitry

    Support Logic 1.3.2 Clock Circuitry The are three options to provide the clock to the CPU. Table 1-11 shows how these options can be configured by setting JP9 and JP10. Table 1-11. M5275EVB Clock Source Selection JP10 Clock Selection 25MHz Oscillator (default setting) 25MHz External Clock 25MHz Crystal The 25MHz oscillator (U19) also feeds the Ethernet transceiver chips (U8 and U9).

  • Page 20: Ta Generation

    Support Logic • I C module • QSPI module • Timer modules • Fast Ethernet Controller (FEC0) • Periodic Interrupt Timers (PIT0–PIT3) • Random Number Generator (RNG) • Symmetric Key Hardware Accelerator (SKHA) • Message Digest Hardware Accelerator (MDHA) • USB module Interrupt controller 1 (INTC1) handles these interrupt sources: •...

  • Page 21: User's Program

    Communication Ports 1.3.6 User’s Program JP4 on the 2 MByte Flash (U11) or JP5 if using the 4 MByte Flash (U12) allows users to test code from boot/POR without having to overwrite the dBUG ROM Monitor. When the jumper is set between pins 1 and 2, the behavior of the system is normal, dBUG boots and then runs from 0xFFE0_0000 (0xFFC0_0000).

  • Page 22: Bdm/Jtag Port

    Communication Ports — 10-Mbps IEEE 802.3 MII — 10-Mbps 7-wire interface (industry standard) • IEEE 802.3 full duplex flow control • Programmable max frame length supports IEEE 802.1 VLAN tags and priority • Support for full-duplex operation (200Mbps throughput) with a minimum system clock rate of 50MHz •...

  • Page 23: I2C

    Communication Ports BKPT DEVELOPER RESERVED DSCLK TCLK (only for JTAG) RESET I/O or Pad Voltage PST3 PST2 PST1 PST0 DDATA3 DDATA2 DDATA1 DDATA0 MOTOROLA RESERVED MOTOROLA RESERVED PSTCLK Core Voltage Figure 1-4. J1- BDM Connector pin assignment The BDM connector can also be used to interface to JTAG signals. On reset, the JTAG_EN signal selects between multiplexed debug module and JTAG signals.

  • Page 24: Qspi

    Connectors and User Components 1.4.5 QSPI The QSPI (Queued Serial Peripheral Interface) module provides a serial peripheral interface with queued transfer capability. It will support up to 16 stacked transfers at one time, minimizing CPU intervention between transfers. Transfer RAMs in the QSPI are indirectly accessible using address and data registers.
  • Page 25 Connectors and User Components Table 1-12. J3 Pinout (Continued) Signal Signal FEC0_RXDV FEC0_RXD2 FEC1_COL FEC0_RXD1 FEC0_RXCLK FEC0_RXD0 FEC0_CRS FEC0_COL FEC0_MDC FEC0_MDIO RTS0 CTS0 RTS1 TXD0 CTS1 RXD0 TXD1 RXD1 B_A12 B_A16 B_A13 B_A19 B_A14 B_A20 B_A15 B_A21 B_A16 B_A22 B_A17 B_A23 Table 1-13.
  • Page 26 Connectors and User Components Table 1-13. J4 Pinout (Continued) Signal Signal FEC1_TXD3 FEC1_TXD2 FEC1_TXD0 FEC1_TXD1 FEC0_TXD3 FEC0_TXD2 FEC0_TXD1 FEC0_TXD0 FEC1_MDIO FEC1_MDC TOUT0 TOUT1 TOUT2 TOUT3 TIN0 TIN1 TIN2 TIN3 SDWE SD_CAS SD_RAS SD_CKE SD_DQS1 B_D31 B_D30 SD_CS1 B_D29 SD_CS0 B_D27 B_D28 B_D25 B_D26...
  • Page 27 Connectors and User Components Table 1-14. J5 Pinout (Continued) Signal Signal B_A9 B_A3 B_A8 B_A2 B_A7 B_A1 B_A6 B_A0 IRQ7 IRQ6 IRQ5 TSIZ1 IRQ4 TSIZ0 IRQ3 IRQ2 USB_SPEED IRQ1 USB_CLK USB_TN USB_RN USB_TP USB_RP USB_TXEN USB_RXD EXTAL USB_SUSP XTAL RSTOUT EXT_RST TRST/DSCLK RESET...

  • Page 28: Reset Switch (Sw5)

    Connectors and User Components Table 1-15. J6 Pinout (Continued) Signal Signal SD_CLKOUT SD_A10 SD_CLKOUT RTS2 RCON RXD2 TXD2 CTS2 PST3 PST2 PST1 PST0 DDATA3 DDATA2 DDATA1 DDATA0 QSDO CLKOUT PCS0 PSC2 PSC3 PSC1 QSDI CLKMOD0 CLKMOD1 JTAG_EN 1.5.2 Reset Switch (SW5) The reset logic provides system initilization.

  • Page 29: User Leds

    Connectors and User Components An OR gate (U21) is used to OR all three of the boards reset sources. The output of the OR gate is connected directly to the MCF5275’s RESET pin. dBUG configures the MCF5275 microprocessor internal resources during initialization. The instruction cache is invalidated and disabled.
  • Page 30 Connectors and User Components Table 1-17. LED Functions (Continued) Function Reset (RESET) asserted D21-D28 User LEDs (See Table 1-16) 1-22 M5275EVB User’s Manual...

  • Page 31: Initialization And Setup

    Chapter 2 Initialization and Setup System Configuration The M5275EVB board requires the following items for minimum system configuration: • The M5275EVB board (provided). • Power supply, +6V to 14V DC with minimum of 1 A (9V, 2.7A supply provided). • RS232C compatible terminal or a PC with terminal emulation software. •...

  • Page 32: Installation And Setup

    Installation and Setup RS-232 Terminal Or PC dBUG> +7 to +14VDC Input Power Figure 2-1. Minimum System Configuration Installation and Setup The following sections describe all the steps needed to prepare the board for operation. Please read the following sections carefully before using the board. When you are preparing the board for the first time, be sure to check that all jumpers are in the default locations.

  • Page 33: Unpacking

    Installation and Setup interface may be used by following the instructions provided in Appendix A, “Configuring dBUG for Network Downloads.” 2.2.1 Unpacking Unpack the computer board from its shipping box. Save the box for storing or reshipping. Refer to the following list and verify that all the items are present. You should have received: •...

  • Page 34: Power Switch (Sw3)

    Installation and Setup Figure 2-2. 2.1mm Power Connector V+(7-14V) Figure 2-3. 2-Lever Power Connector 2.2.4 Power Switch (SW3) Slide switch SW3 can be used to isolate the power supply input from the EVB voltage regulators if required. Moving the slide switch to the left (towards connector P2) will turn the EVB ON. Moving the slide switch to the right (away from connector P2) will turn the EVB OFF.

  • Page 35: Selecting Terminal Baud Rate

    Installation and Setup If no LEDs are illuminated when the power is applied to the EVB, it is possible that either power switch SW3 is in the “OFF” position or that the fuse F1 has blown. This can occur if power is applied to the EVB in reverse-bias where a protection diode ensures that the fuse blows rather than causing damage to the EVB.
  • Page 36 Installation and Setup section 1.9.5 The Terminal Character Format.) The baud rate should be set to 19200. Power can now be applied to the board. Figure 2-4. Pin Assignment for Female (Terminal) Connector Pin assignments are as follows: Table 2-2. Pin Assignment for Female (Terminal) Connector DB9 Pin Function Data Carrier Detect, Output (shorted to pins 4 and 6)
  • Page 37 Installation and Setup Figure 2-5. Jumper Locations Chapter 2. Initialization and Setup...

  • Page 38: System Power-Up And Initial Operation

    Hard Reset DRAM Size: 16M Copyright 1995-2004 Motorola, Inc. All Rights Reserved. ColdFire MCF5275 EVS Firmware v2e.1a.xx (Build XXX on XXX XX 20XX xx:xx:xx) Enter 'help' for help. dBUG> The board is now ready for operation under the control of the debugger as described in Chapter 3, “Using the Monitor/Debug Firmware.”...

  • Page 39: Using The Monitor/Debug Firmware

    Chapter 3 Using the Monitor/Debug Firmware The M5275EVB single board computer has a resident firmware package that provides a self-contained programming and operating environment. The firmware, named dBUG, provides the user with monitor/debug interface, inline assembler and disassembly, program download, register and memory manipulation, and I/O control functions. This chapter is a how-to-use description of the dBUG package, including the user interface and command structure.
  • Page 40 What Is dBUG? Most commands can be recognized by using an abbreviated name. For instance, entering “h” is the same as entering “help”. Thus, it is not necessary to type the entire command name. The commands DI, GO, MD, STEP and TRACE are used repeatedly when debugging. dBUG recognizes this and allows for repeated execution of these commands with minimal typing.

  • Page 41: Operational Procedure

    Operational Procedure Operational Procedure System power-up and initial operation are described in detail in Chapter 2, “Initialization and Setup.” This information is repeated here for convenience and to prevent possible damage. 3.2.1 System Power-up • Be sure the power supply is connected properly prior to power-up. •...

  • Page 42: System Initialization

    After the EVB is powered-up and initialized, the terminal will display: Hard Reset DRAM Size: 16M Copyright 1995-2004 Motorola, Inc. All Rights Reserved. ColdFire MCF5275 EVS Firmware v2e.1a.xx (Build XXX on XXX XX 20XX xx:xx:xx) Enter 'help' for help. dBUG>...

  • Page 43: Command Line Usage

    Command Line Usage Command Line Usage The user interface to dBUG is the command line. A number of features have been implemented to achieve an easy and intuitive command line interface. dBUG assumes that an 80x24 ASCII character dumb terminal is used to connect to the debugger.
  • Page 44 Commands Table 3-1. dBUG Command Summary Mnemonic Syntax Description asm <<addr> stmt> Assemble bc addr1 addr2 length Block Compare bf <width> begin end data <inc> Block Fill bm begin end dest Block Move br addr <-r> <-c count> <-t trigger> Breakpoint bs <width>...
  • Page 45 Commands Assembler Usage: ASM <<addr> stmt> The ASM command is a primitive assembler. The <stmt> is assembled and the resulting code placed at <addr>. This command has an interactive and non-interactive mode of operation. The value for address <addr> may be an absolute address specified as a hexadecimal value, or a symbol name.
  • Page 46 Commands Block Compare Usage:BC addr1 addr2 length The BC command compares two contiguous blocks of memory on a byte by byte basis. The first block starts at address addr1 and the second starts at address addr2, both of length bytes. If the blocks are not identical, the address of the first mismatch is displayed.
  • Page 47 Commands Block Fill Usage:BF<width> begin end data <inc> The BF command fills a contiguous block of memory starting at address begin, stopping at address end, with the value data. <Width> modifies the size of the data that is written. If no <width>...
  • Page 48 Commands Block Move Usage:BM begin end dest The BM command moves a contiguous block of memory starting at address begin and stopping at address end to the new address dest. The BM command copies memory as a series of bytes, and does not alter the original block. The values for addresses begin, end, and dest may be absolute addresses specified as hexadecimal values, or symbol names.
  • Page 49 Commands Breakpoints Usage:BR addr <-r> <-c count> <-t trigger> The BR command inserts or removes breakpoints at address addr. The value for addr may be an absolute address specified as a hexadecimal value, or a symbol name. Count and trigger are numbers converted according to the user-defined radix, normally hexadecimal. If no argument is provided to the BR command, a listing of all defined breakpoints is displayed.
  • Page 50 Commands Block Search Usage:BS<width> begin end data The BS command searches a contiguous block of memory starting at address begin, stopping at address end, for the value data. <Width> modifies the size of the data that is compared during the search. If no <width> is specified, the default of word sized data is used.
  • Page 51 Commands Data Conversion Usage:DC data The DC command displays the hexadecimal or decimal value data in hexadecimal, binary, and decimal notation. The value for data may be a symbol name or an absolute value. If an absolute value passed into the DC command is prefixed by ‘0x’, then data is interpreted as a hexadecimal value. Otherwise data is interpreted as a decimal value.
  • Page 52 Commands Disassemble Usage:DI <addr> The DI command disassembles target code pointed to by addr. The value for addr may be an absolute address specified as a hexadecimal value, or a symbol name. Wherever possible, the disassembler will use information from the symbol table to produce a more meaningful disassembly.
  • Page 53 Commands Download Console Usage:DL <offset> The DL command performs an S-record download of data obtained from the console, typically a serial port. The value for offset is converted according to the user-defined radix, normally hexadecimal. Please reference the ColdFire Microprocessor Family Programmer’s Reference Manual for details on the S-Record format.
  • Page 54 Commands DLDBUG Download dBUG Usage:DL <offset> The DLDBUG command is used to update the dBUG image in Flash. It erases the Flash sectors containing the dBUG image, downloads a new dBUG image in S-record format obtained from the console, and programs the new dBUG image into Flash. When the DLDBUG command is issued, dBUG will prompt the user for verification before any actions are taken.
  • Page 55 Commands Download Network Usage:DN <-c> <-e> <-i> <-s> <-o offset> <filename> The DN command downloads code from the network. The DN command handle files which are either S-record, COFF, ELF or Image formats. The DN command uses Trivial File Transfer Protocol (TFTP) to transfer files from a network host. In general, the type of file to be downloaded and the name of the file must be specified to the DN command.
  • Page 56 Commands Flash Utilities Info Usage: FL Erase Usage: FL erase addr bytes Write Usage: FL write dest src bytes The FL command provides a set of flash utilities that will display information about the Flash devices on the EVB, erase a specified range of Flash, or erase and program a specified range of Flash.
  • Page 57 Commands Execute Usage:GO <addr> The GO command executes target code starting at address addr. The value for addr may be an absolute address specified as a hexadecimal value, or a symbol name. If no argument is provided, the GO command begins executing instructions at the current program counter.
  • Page 58 Commands Execute To Usage:GT addr The GT command inserts a temporary breakpoint at addr and then executes target code starting at the current program counter. The value for addr may be an absolute address specified as a hexadecimal value, or a symbol name. When the GT command is executed, all breakpoints are inserted into the target code, and the context is switched to the target program.
  • Page 59 Commands Internal Register Display Usage:IRD <module.register> This command displays the internal registers of different modules inside the MCF5275. In the command line, module refers to the module name where the register is located and register refers to the specific register to display. The registers are organized according to the module to which they belong.
  • Page 60 Commands Internal Register Modify Usage:IRM module.register data This command modifies the contents of the internal registers of different modules inside the MCF5275. In the command line, module refers to the module name where the register is located and register refers to the specific register to modify. The data parameter specifies the new value to be written into the register.
  • Page 61 Commands HELP Help Usage:HELP <command> The HELP command displays a brief syntax of the commands available within dBUG. In addition, the address of where user code may start is given. If command is provided, then a brief listing of the syntax of the specified command is displayed. Examples: To obtain a listing of all the commands available within dBUG, the command is: help...
  • Page 62 Commands Loop Read Usage:LR<width> addr The LR command continually reads the data at addr until a key is pressed. The optional <width> specifies the size of the data to be read. If no <width> is specified, the command defaults to reading word sized data. Example: To continually read the longword data from address 0x20000, the command is: lr.l...
  • Page 63 Commands Loop Write Usage:LW<width> addr data The LW command continually writes data to addr. The optional width specifies the size of the access to memory. The default access size is a word. Examples: To continually write the longword data 0x12345678 to address 0x20000, the command is: lw.l 20000 12345678 Note that the following command writes 0x78 into memory:...
  • Page 64 Commands Memory Display Usage:MD<width> <begin> <end> The MD command displays a contiguous block of memory starting at address begin and stopping at address end. The values for addresses begin and end may be absolute addresses specified as hexadecimal values, or symbol names. Width modifies the size of the data that is displayed.
  • Page 65 Commands Memory Modify Usage:MM<width> addr <data> The MM command modifies memory at the address addr. The value for addr may be an absolute address specified as a hexadecimal value, or a symbol name. Width specifies the size of the data that is modified. If no <width> is specified, the default of word sized data is used.
  • Page 66 Commands MMAP Memory Map Display Usage:mmap This command displays the memory map information for the M5275EVB evaluation board. The information displayed includes the type of memory, the start and end address of the memory, and the port size of the memory. The display also includes information on how the Chip-selects are used on the board and which regions of memory are reserved for dBUG use (protected).
  • Page 67 Commands Register Display Usage:RD <reg> The RD command displays the register set of the target. If no argument for reg is provided, then all registers are displayed. Otherwise, the value for reg is displayed. dBUG preserves the registers by storing a copy of the register set in a buffer. The RD command displays register values from the register buffer.
  • Page 68 Commands Register Modify Usage:RM reg data The RM command modifies the contents of the register reg to data. The value for reg is the name of the register, and the value for data may be a symbol name, or it is converted according to the user-defined radix, normally hexadecimal.
  • Page 69 Commands RESET Reset the Board and dBUG Usage:RESET The RESET command resets the board and dBUG to their initial power-on states. The RESET command executes the same sequence of code that occurs at power-on. If the RESET command fails to reset the board adequately, cycle the power or press the reset button.
  • Page 70 Commands Stack Dump Usage:SD The SD command displays a back trace of stack frames. This command is useful after some user code has executed that creates stack frames (i.e. nested function calls). After control is returned to dBUG, the SD command will decode the stack frames and display a trace of the function calls.
  • Page 71 Commands Set Configurations Usage:SET <option value> The SET command allows the setting of user-configurable options within dBUG. With no arguments, SET displays the options and values available. The SHOW command displays the settings in the appropriate format. The standard set of options is listed below. baud - This is the baud rate for the first serial port on the board.
  • Page 72 Commands SHOW Show Configurations Usage:SHOW <option> The SHOW command displays the settings of the user-configurable options within dBUG. When no option is provided, SHOW displays all options and values. Examples: To display all options and settings, the command is: show To display the current baud rate of the board, the command is: show baud...
  • Page 73 Commands STEP Step Over Usage:STEP The STEP command can be used to “step over” a subroutine call, rather than tracing every instruction in the subroutine. The ST command sets a temporary breakpoint one instruction beyond the current program counter and then executes the target code. The STEP command can be used to “step over”...
  • Page 74 Commands SYMBOL Symbol Name Management Usage:SYMBOL <symb> <-a symb value> <-r symb> <-c|l|s> The SYMBOL command adds or removes symbol names from the symbol table. If only a symbol name is provided to the SYMBOL command, then the symbol table is searched for a match on the symbol name and its information displayed.
  • Page 75 Commands TRACE Trace Into Usage:TRACE <num> The TRACE command allows single-instruction execution. If num is provided, then num instructions are executed before control is handed back to dBUG. The value for num is a decimal number. The TRACE command sets bits in the processors’ supervisor registers to achieve single-instruction execution, and the target code executed.
  • Page 76 Commands Upload Data Usage:UP begin end filename The UP command uploads the data from a memory region (specified by begin and end) to a file (specified by filename) over the network. The file created contains the raw binary data from the specified memory region. The UP command uses the Trivial File Transfer Protocol (TFTP) to transfer files to a network host.
  • Page 77 Commands VERSION Display dBUG Version Usage:VERSION The VERSION command displays the version information for dBUG. The dBUG version, build number and build date are all given. The version number is separated by a decimal, for example, “v 2b.1c.1a”. In this example, v 2b . 1c . 1a dBUG common CPU major board major...

  • Page 78: Trap #15 Functions

    TRAP #15 Functions TRAP #15 Functions An additional utility within the dBUG firmware is a function called the TRAP 15 handler. This function can be called by the user program to utilize various routines within the dBUG, to perform a special task, and to return control to the dBUG. This section describes the TRAP 15 handler and how it is used.

  • Page 79: In_Char

    TRAP #15 Functions asm (“trap#15”); /* make the call */ #endif 3.5.2 IN_CHAR This function (function code 0x0010) returns an input character (from terminal) to the caller. The returned character is in D1. Assembly example: move.l #$0010,d0 Select the function trap Make the call, the input character is in d1.

  • Page 80: Exit_To_Dbug

    TRAP #15 Functions 3.5.4 EXIT_TO_dBUG This function (function code 0x0000) transfers the control back to the dBUG, by terminating the user code. The register context are preserved. Assembly example: move.l #$0000,d0 Select the function trap Make the call, exit to dBUG. C example: void board_exit_to_dbug (void) asm (“move.l#0x0000,d0”);...

  • Page 81: Appendix A Configuring Dbug For Network Downloads

    Appendix A Configuring dBUG for Network Downloads The dBUG module has the ability to perform downloads over an Ethernet network using the Trivial File Transfer Protocol, TFTP (NOTE: this requires a TFTP server to be running on the host attached to the board). Prior to using this feature, several parameters are required for network downloads to occur.

  • Page 82: Configuring Dbug Network Parameters

    Configuring dBUG Network Parameters Configuring dBUG Network Parameters Once the network parameters have been obtained, the dBUG ROM Monitor must be configured. The following commands are used to configure the network parameters. set client <client IP> set server <server IP> set gateway <gateway IP>...

  • Page 83: Troubleshooting Network Problems

    Troubleshooting Network Problems Finally, perform the network download with the ‘dn’ command. The network download process uses the configured IP addresses and the default filename and filetype for initiating a TFTP download from the TFTP server. Troubleshooting Network Problems Most problems related to network downloads are a direct result of improper configuration. Verify that all IP addresses configured into dBUG are correct.
  • Page 84 Troubleshooting Network Problems M5275EVB User’s Manual...

  • Page 85: Appendix B Schematics

    Appendix B Schematics M5275EVB Schematics Appendix B. Schematics...
  • Page 86 M5275EVB Schematics M5275EVB User’s Manual...
  • Page 87 M5275EVB Schematics MOTOROLA Appendix B. Schematics...
  • Page 88 M5275EVB Schematics M5275EVB User’s Manual...
  • Page 89 M5275EVB Schematics MOTOROLA Appendix B. Schematics...
  • Page 90 M5275EVB Schematics M5275EVB User’s Manual...
  • Page 91 M5275EVB Schematics MOTOROLA Appendix B. Schematics...
  • Page 92 M5275EVB Schematics M5275EVB User’s Manual...
  • Page 93 M5275EVB Schematics MOTOROLA Appendix B. Schematics...
  • Page 94 M5275EVB Schematics B-10 M5275EVB User’s Manual...
  • Page 95 M5275EVB Schematics MOTOROLA Appendix B. Schematics B-11...
  • Page 96 M5275EVB Schematics B-12 M5275EVB User’s Manual...
  • Page 97 M5275EVB Schematics MOTOROLA Appendix B. Schematics B-13...
  • Page 98 M5275EVB Schematics B-14 M5275EVB User’s Manual...
  • Page 99 M5275EVB Schematics MOTOROLA Appendix B. Schematics B-15...
  • Page 100 M5275EVB Schematics B-16 M5275EVB User’s Manual...
  • Page 101 Appendix C M5275EVB BOM M5275EVB BOM Appendix C. M5275EVB BOM...
  • Page 102 M5275EVB BOM M5275EVB User’s Manual...
  • Page 103 M5275EVB BOM M5275EVB Evaluation Board Revised: Tuesday, June 22, 2004 Rapid PCB QTY's PART INFORMATION 521525 Item Assy. Part Number Manufacturer Description & Package Type Ref. Des. 0805CG102J9BB0 Phycom Cap., 1nF,NPO or COG, 25v, C1,C2,C8,C9,C10,C15,C16,C1 Stock 0805,5% 7,C18,C24,C26,C28,C29,C30, C31,C32,C42,C43,C50,C54,C5 8,C59,C62,C65,C68,C71,C78, C80,C82,C84,C86,C87,C88,C8 9,C90,C91,C92,C93,C94,C95, C96,C97,C98,C99,C100,C101,...
  • Page 104 M5275EVB BOM DB9 RS232 PORT THRU HOLE DB9 (No populate) 4x 4.7K KOA or Philips RP1,RP41,RP42,RP43,RP44,R Stock P47,RP48,RP49,RP50,RP53,R P54,RP55,RP56,RP57,RP58,R 4x 22 KOA or Philips RP2,RP3,RP4,RP5,RP6,RP7,R Stock P8,RP9,RP10,RP11,RP12,RP1 3,RP14,RP21,RP22,RP23,RP2 4x 51 KOA or Philips RP15,RP16,RP17,RP18,RP19, Stock RP20,RP25,RP26,RP27,RP28, RP29,RP30,RP31,RP32,RP33, RP35,RP36,RP37,RP38 4x 470 KOA or Philips RP34 Stock...

This manual is also suitable for:

Coldfire mcf5275lColdfire mcf5274Coldfire mcf5274l

Table of Contents