Last update: 1 November 2005

Features: low-cost BDM pods for all HC12 targets use Motorola DBug12 commands on target board supports hardware and software breakpoints in target RS232 interface to PC (or any platform with terminal emulation capability) 10-pin ribbon cable compatible with all Adapt12 boards no power supply required-- draws power from target board housed in a robust plastic enclosure for maximum reliability includes power and activity indicator LEDs standard version runs D-Bug12 version 2.1 on 68HC912B32 (supports baudrates up to 38.4K) DX version runs D-Bug12 version 3 on 68HC912D60 (supports baudrates up to 38.4K) SX version runs D-Bug12 version 4.0 on 9S12DP256 (supports baudrates up to 115K) SX version now works with NoICE12 debugger!

Here's how to use MicroBDM12:
Just connect the supplied ribbon cable to the target board's "BDM IN" connector. The target board could be any Adapt12-family board, or any other 'HC12 board that has a 6- or 10-pin BDM interface connector. The host for the BDM Pod can be any type of computer running a terminal program. The BDM pod will receive its 5V operating power from the target board through the ribbon cable.  A couple of suggested Windows terminal programs are MiniIDE and Hyperterminal.  For details on using other terminal programs with D-Bug12, refer to the appendix of Motorola's EVB912 Manual.  The big advantage of using a BDM pod is that it frees up all of the target board's memory for your application, while still offering you debugging capability.  You can examine memory and registers, disassemble a memory range, set breakpoints, and do tracing in the target board's on-chip memory, among other things.

Note:  MicroBDM12 does not support programming the newer "A"-suffix 68HC912 chips and the new HCS12 parts.  For that, you'll need MicroBDM12DX or MicroBDM12SX.  For C source-level debugging with NoICE12, you'll need MicroBDM12SX.

Chips supported:
MicroBDM12:        68HC812A4, 68HC912B32, 68HC912BC32, 68HC912D60, 68HC912DA128 (non-paged only), 68HC912DG128 (non-paged only)
MicroBDM12DX:    68HC812A4, 68HC912B32, 68HC912BC32, 68HC912D60/A, 68HC912DA128/A, 68HC912DG128/A, 68HC912DT128/A, limited support for 9S12DP256 and 9S12 derivatives
MicroBDM12SX:    68HC812A4, 68HC912B32, 68HC912BC32, 68HC912D60/A, 68HC912DA128/A, 68HC912DG128/A, 68HC912DT128/A, and all current 9S12 derivatives (supports 5V operation only)

What's inside the box:
MicroBDM12 is a minimal 68HC912B32 board, running D-Bug12 v2.1, in Pod mode.  MicroBDM12DX is a minimal 68HC912D60 board, running D-Bug12 v3.0.  MicroBDM12SX is a minimal 9S12DP256 board, running D-Bug12 v4.0. All three configurations consist of the MCU, a crystal, an RS232 interface circuit, and a few miscellaneous components, all mounted on a small board less than 2 inches square.  A 10-pin ribbon cable is attached to one edge, and a 9-pin D-sub connector is on the opposite edge, and the whole assembly is housed in a small plastic box.  A 9-pin serial cable is included for the PC serial port interface.

Firmware Updates:
If DBug12 ever needs to be updated, it can be done using another BDM pod.  By opening the box, applying regulated 12VDC to the power connector on the circuit board, and moving two jumpers to make the ribbon cable function as BDM IN, the board becomes a target, and Flash can be erased and re-programmed as needed.  (Note:  a regulated 12V supply is not required for the 'SX version--  just 5VDC or higher)

BDM Pod Transformer For customers using Adapt9S12DP256, we've created a small circuit board to transform your module into the equivalent of a MicroBDM12SX pod.  It includes a connector that fits over the section of pins on H1 that DBug12 uses to implement BDM OUT functionality.  Just plug it onto the matching section of H1, and plug the included 10-pin ribbon cable into your HC12 target board.  Order #BDM256XFMR-�.  Choose the appropriate connector option (�) to mate with H1 on your Adapt9S12DP256, as follows: - choose "F" if your module's H1 connector is RA1, M, or FM - choose "F1" if your module's H1 connector is RA, M1, or FM1 - choose "M" if your module's H1 connector is FRA, F (or FM) - choose "M1" if your module's H1 connector is FRA1, F1 (or FM1)