USBDM-CF (USBDM/CF/DSC /ARM)-JM60 полностью Функциональная модель может быть выставлена ​​на счет

Меры предосторожности перед покупкой:

1. Нужно прочитать чип Заказчикам программ или данных необходимо самостоятельно исследовать, этот магазин не предоставляет техническую поддержку! Не покупайте, если не умеете читать, спасибо за сотрудничество!

Codewarrior V10.00 - V10.6 Вся поддержка!!!

USBDM/CF (JMxx Version) V4.5
USBDM/CF (combined TBDML/OSBDM/TBLCF/DSC code) for JM32/60
Introduction
The attached files provide a port of a combined TBDML/OSBDM/TBLCF code to a MC9S08JM16/32/60 processor. The primary motivation for this was to produce a single BDM that could be used with the HC12, HCS08, Coldfire V1-4 microcontrollers and MC56F80xx Digital Signal Controllers. Other features have also been added.

Features
This version of the code & BDM hardware provides the following features:

A single BDM interface for programming and debugging of the following targets:
 1,HCS12(including those without SYNC feature (e.g. 9S12DP256B)
 2,HCS08
 3,RS08
 4,Coldfire V1microcontrollers
 5,Coldfire V2, V3 & V4microcontrollers
 6,MC56F80xxDigital Signal Controllers

Compatible IDEs

• • Codewarrior V10.x(Eclipse version)
    • Tested on Windows-XP-32bit,
    •           Windows-7-64bit
    • Tested on Ubuntu-32-bit
  • CodeWarriorLegacy versions
  • Студия разработки Codewarrior для HCS12 (X) V5.1（HCS12 ）
  • Tested on Windows-XP-32bit,
  • Tested on Windows-7,win8,win10,64 бит / 32 бит,
  •  
  • CW for Microcontrollers V6.3(RS08 is supported)
    • Tested on Windows-XP-32bit,
  • Initial support for CodeSourcery Lite for Coldfire
    • Tested on Windows-XP-32bit 

   CW for Coldfire V7.1 CodeWarrior for DSC56800E v8.3 (USBDM-JMxx-CF or MC56F8006Demo board only)
   Tested on Windows-XP-32bit,
   Initial support for CodeSourcery Lite for Coldfire
   Tested on Windows-XP-32bit
   Initial support for Coldfire Flasher (CFFlasher)
   Tested on Windows-XP-32bit
   Trimming of target internal clock (Eclipse version or standalone programming tools only).
    Higher USB communication speed cf. JB16 version BDMs (USB full speed cf. USB low speed)
   Vista compatible
   Linux compatible

Target Vdd supply & control. This allows the target power to be cycled when required for a reliable reset into BDM mode. It is also (obviously) convenient since it allows debugging small target boards without a separate target power supply. An external target supply may also be used instead. The Target supply is protected by a polyfuse and software detection of overload.
HCS12, HCS08, RS08, Coldfire V1 specific features:
Target reset detection & control (required for HC12 processors). This allows HC12 processors to be reset into BDM mode as required for debugging.
Target Vdd monitoring. This allows the hardware to detect changes in the Target supply to provide reliable resetting into BDM modes on HCS08 and RS08 microcontrollers. It also is used to implement the target power supply protection.
A higher BDM interface speed than the existing JB16 OSBDMs. Up to 56MHz. (BDM clock 28MHz).
Several software options over the existing OSBDM code
Automatic re-connection. The existing OSBDM code appears to have problems debugging a target when the target clock speed is changed by the code execution. The software has an option to continuously update the interface speed to prevent loss of communication in this case.
Control of BDM clock selection in HC12/HCS08/Coldfire microcontrollers. Most of these targets provide an alternative BDM clock selection. This can have advantages when connecting to high speed targets as the alternative clock may operate at a lower speed.
Selection of 3.3V and 5V target supply (if hardware supports this).
Trial-and-error determination of communication speed for earlier HC12 targets.
User prompting for target supply cycling with BKGD low as may be needed for HCS08 targets
Coldfire V2,3,4 specific features and limitations:
Higher communication speed with target - The target communication speed may be selected.
The BDM uses asychronous communication with the target i.e. the BDM signals are not synchronized with the target clock. This means that the BDM should not be used with early Coldfire targets. Check the description of the BDM interface timing in the appropriate Coldfire Processor manual to determine if this limitation applies.

The drivers and programmers have been tested with the following devices (basic programming, debugging and clock trim where applicable):

  RS08KA1, -KA2, -KA8, -LA8, -LE4 (only with the Eclipse version of Codewarrior)
  MC9S08AC128, -DN16, -DZ128, -EL16, -FL16, -GB60A, -GT16A, -GT32, -JM16, -JM60, -  JS16, -LG32, -LL64,
   -LM26, -QA4, -QB8, -QD4, -QE8, -QE16, -QG8, -RD16, -SE8, -SF4, -SH8, -SV16,

   MC13213

   MC9S12A64, -C32, -C128, -DP256B, -DG128, -XDT512, -NE64, -XD256, -UF32(unsecure is not available)

   MCF51AC256, -CN128, -EM256, -JM128, -QE96,

   MCF52233, MCF52210 and some other ones that I can't recall at the moment.       These are all V2 chips - I don't have any V3/4 to test with.
    MC56F8006, MC56F8014, NC56F8323
   Complete system - Axiom MC56F8006 Demo board.