Motorola MCU MC9S12DP256 User Manual

Motorola development board user's manual.
Hide thumbs



Development Board for Motorola MC9S12DP256
2813 Industrial Ln.
Garland, TX 75041
(972) 926-9303 FAX (972) 926-6063


   Related Manuals for Motorola MCU MC9S12DP256

   Summary of Contents for Motorola MCU MC9S12DP256

  • Page 1

    CML12S-DP256 Development Board for Motorola MC9S12DP256 xiom anufacturing 2000 2813 Industrial Ln. Garland, TX 75041 (972) 926-9303 FAX (972) 926-6063 email: web:

  • Page 2: Table Of Contents

    C M L 1 2 S D P 2 5 6 GETTING STARTED...3 Installing the Software ...4 Board Startup ...4 Support Software...4 Software Development ...5 TUTORIAL ...5 Creating source code...5 Assembling source code...6 Running your application ...7 Programming HCS12 Flash EEPROM...8 MON12 OPERATION ...9 Mon12 Monitor Commands ...10 MON12 Interrupt Support ...10...

  • Page 3: Getting Started

    Development board users should also be familiar with the hardware and software operation of the target HCS12 device, refer to the Motorola User Guide for the device and the CPU12 Reference Manual for details. The development board purpose is to assist the user in quickly developing an application with a known working environment or to provide an evaluation platform for the target HCS12.

  • Page 4: Installing The Software, Board Startup, Support Software

    C M L 1 2 S D P 2 5 6 Follow the steps in this section to get started quickly and verify everything is working correctly. Installing the Software 1. Insert the Axiom 68HC12 support CD in your PC. If the setup program does not start, run the file called "SETUP.EXE"...

  • Page 5: Software Development, Tutorial, Creating Source Code

    ASCII text without any document formatting added. Once your source code is written and saved to a file, you can assemble or compile it to a Motorola S-Record (hex) format. This type of output file usually has a .MOT, .HEX or .S19 file extension and is in a format that can be read by the programming utilities and programmed into the CML12SXXX board.

  • Page 6: Assembling Source Code

    C M L 1 2 S D P 2 5 6 0 7 / 1 7 / 0 2 It is important to understand the development board's use of Memory and Addressing when writing source code so you can locate your code at valid addresses. For example, when in debug mode, you should put your program CODE in External RAM.

  • Page 7: Running Your Application

    HC12 Paging operation, check the web site for updates. Running your application After creating a Motorola S-Record file you can "upload" it to the development board for a test run. The provided example “HELLO.ASM” was created to run from external RAM so you can use the MON12 Monitor to test it without programming it into Flash.

  • Page 8: Programming Hcs12 Flash Eeprom

    C M L 1 2 S D P 2 5 6 You can modify the hello program to display other strings or do anything you want. The procedures for assembling your code, uploading it to the board and executing it remain the same.

  • Page 9: Mon12 Operation

    C M L 1 2 S D P 2 5 6 MON12 OPERATION Mon12 is an embedded monitor / debug utility that allows loading a compiled software program (S record) into Ram memory for testing and debug. The monitor may control the execution of the software by applying the SWI software interrupt service.

  • Page 10: Mon12 Monitor Commands, Mon12 Interrupt Support

    C M L 1 2 S D P 2 5 6 A) Determine if Auto Start in enabled and proceed to vector if not a value of $FFFF. B) Set Stack, Initialize memory map and SCI0 port and send prompt. C) Receive first character from Console port and execute monitor if ASCII text / command, else start utility mode for programming services.

  • Page 11: Noice Operation, Mon12 And Noice Memory Map

    C M L 1 2 S D P 2 5 6 This vector initialization should remain after debug when auto start will be applied for launching the user's application. Note that the user interrupt service routines must be located in the $4000 - $7FFF address range for correct operation. See Autostart for more details. MON12 and NOICE Memory Map ADDRESS TYPE MEMORY...

  • Page 12: Bdm Operation, Autostart

    C M L 1 2 S D P 2 5 6 The CML12S-DP256 provides the NOICE debug monitor kernel as a subset of the MON12 monitor in reserved flash memory. User may apply the NOICE development system by setting the MON12 Autostart for the $F800 vector, reset the board and launch the NOICE host software on the PC.

  • Page 13: Options And Jumpers, Mem_en

    C M L 1 2 S D P 2 5 6 User application must perform all initialization including Stack setting, hardware startup, and external memory bus enable if needed, when the Autostart is applied. MON12 Ram Interrupt Vector table must also be applied in the same manner as under MON12 supervision or application interrupts will be trapped instead of serviced.

  • Page 14: Modc, Auto Off / Spare, Mode, Osc_sel, Rom_off

    C M L 1 2 S D P 2 5 6 0 7 / 1 7 / 0 2 MODC The MODC option jumper provides Special Mode enable during Reset. This option must be open or idle when operating with the MON12 or NOICE monitors. If a BDM cable is applied to BDM port, the MODC option must be installed to enable Special Mode.

  • Page 15: Cut-away Options 1 - 6, Ports And Connectors, Tb1 And J1 Power

    C M L 1 2 S D P 2 5 6 0 7 / 1 7 / 0 2 JP1 and JP2 JP1 and 2 option jumpers provide an easy method of connecting or isolating the HCS12 SCI0 and SCI1 serial channel RXD pins respectfully from the provided on-board RS232 transceiver. To apply the RXD pins on the SCI channels for other user applications requires that the transceiver driver be removed from the HCS12 pin.

  • Page 16: Analog Port

    C M L 1 2 S D P 2 5 6 The VDD supply is for reference or external 2.5V input only and should not be loaded by external circuitry or damage to the HCS12 device may occur. MCU_PORT +5V 60 59 GND PT7 58 57 PT6 PT5 56 55 PT4 PT3 54 53 PT2...

  • Page 17: Bus_port, Keypad / Port H, P_com1 And P_com2

    C M L 1 2 S D P 2 5 6 BUS_PORT D11/PA3 PA2/D10 D12/PA4 PA1/D9 D13/PA5 PA0/D8 D14/PA6 9 10 D15/PA7 A1 11 12 A2 A10 13 14 A3 OE* 15 16 A4 A11 17 18 A5 A9 19 20 A6 A8 21 22 A7 A12 23 24 A13 WE* 25 26 A14...

  • Page 18: Can Port

    C M L 1 2 S D P 2 5 6 JP1 will isolate the SCI0 RXD pin from the transceiver. The 1,4,6,7,8, and 9 pins provide RS232 flow control and status. These are connected on the on the bottom of the development board to provide NULL status to the host. User may isolate pins and provide flow control or status connection to the host by applying HCS12 I/O signals and RS232 level conversion.

  • Page 19: P1 - P4 Hcs12 Header Ring, Lcd_port

    C M L 1 2 S D P 2 5 6 CAN BUS TERMINATION The CAN port provides RC11,12, and 13 1206 SMT size termination resistors on the bottom of the CML12Sxxx board that are not installed at the factory. The termination resistors provide optional bias and termination impedance for the CAN bus connected to the CAN Port.

  • Page 20: Bdm Port, Test Points

    3) CUT-AWAY 1 - 3 provide a means to isolate the LCD Port from the HCS12 SPI channel. BDM PORT The BDM port is a 6 pin header compatible with the Motorola Background Debug Mode (BDM) Pod. This allows the connection of a background debugger for software development, programming and debugging in real-time without using HC12 I/O resources.

  • Page 21: Troubleshooting

    C M L 1 2 S D P 2 5 6 TROUBLESHOOTING The CML12SXXX board is fully tested and operational before shipping. If it fails to function properly, inspect the board for obvious physical damage first. Ensure that all IC devices in sockets are properly seated.

  • Page 22

    C M L 1 2 S D P 2 5 6 Tips and Suggestions Tips and Suggestions Following are a number of tips, suggestions, and answers to common questions that will solve many problem users have with the CML12SXXX development system. You can download the latest software from the Support section of our web page at: Utilities...

  • Page 23: Table 1. Lcd Command And Character Codes

    C M L 1 2 S D P 2 5 6 TABLE 1. LCD Command and Character Codes Command codes are used for LCD setup and control of character and cursor position. All command codes are written to LCD panel address $B5F0. The BUSY flag (bit 7) should be tested before any command updates to verify that any previous command is completed.

  • Page 24: Table 2. Mon12 Interrupt Table

    C M L 1 2 S D P 2 5 6 TABLE 2. MON12 Interrupt Table MON12 Ram Interrupt Vector 3F8C 3F8E 3F90 3F92 3F94 3F96 3F98 3F9A 3F9C 3F9E 3FA0 3FA2 3FA4 3FA6 3FA8 3FAA 3FAC 3FAE 3FB0 3FB2 3FB4 3FB6 3FB8...

This manual also for:


Comments to this Manuals

Symbols: 0
Latest comments: