Attached is version 2 of the JS16/JM16/32/60 version of USBDM.
This includes the following hardware versions:
- JS16 - A very minimal BDM that supports HCS12, HCS08 and Coldfire V1 devices. It is easy to construct and may be initially programmed over the USB.
- JMxx - A full-featured BDM that supports HCS12, HCS08, RS08 and Coldfire V1 devices. It also provides a range of additional features such as target power control and detection.
- JMxx/CF - As for JMxx but also supporting Coldfire V2, 3, & 4 (Only tested on CFV2!)
If you want a simple BDM then I recommend the JS16. This has all the advantages of the previous JB16 version of OSBDM (ability to be programmed over USB & convenient SOIC package) as well as being USB2 Full speed. It is also available as a sample from Freescale
.
If you want a full-featured BDM then I recommend the JMxx version.
BDM Firmware History
- V2.0 (September 2009) - Major change - Please read
- Major revision. The structure of the software has been revised and the operation with various targets made more uniform.
- Introduction of a new API for using the BDM. Existing APIs (TBDML, OSBDM, TBLCF) are now supported by a separate compatibility layer. This has resulted in a very significant reduction in the complexity of both the BDM firmware and the interface DLLs. The previous arrangement was becoming impossible to maintain.
- The handling of RS08 devices has been re-written in a more sensible fashion. This involved moving the bulk of the RS08 code from the BDM firmware to the interface DLLs. This should mean that additional devices can be introduced without changing the BDM firmware. Support for additional RS08 devices has been added. The BDM now supports KA1, KA2, KA4, KA8, LA8 and LE4.
- Because of the above changes, the BDM REQUIRES the use of the provided interface DLLs. The BDM is no longer compatible with the original TBDML or OSBDM dlls.
The provided DLLs maintain some limited compatibility with earlier versions of TBDML, OSBDM and USBDM but may not support all features or targets
- V1.5 (June 2009)
- Improved/corrected connection strategy for external power cycling
- Minor bug fixed (glitch removal)
- Improvements to ALT clock handling
- Changes to USB code to fixed bugs with BDM being recognized on some PCs (Thanks to Macias & Enrico for bug chasing and testing) Tested with USBCV13.exe from USB.ORG - now passes
- V1.4 (February 2009)
- Fixed a bug in the USB code (unlikely to occur but worth fixing)
- Added extra dialogues prompting the user to cycle target power when necessary. Corresponding options added.
- Added connection retry when target power is absent.
- Added support for MC51AC256 (a bit of a hack!)
- Modified HCS macros (to provide considerable size reduction as needed for USBDM_CF in 16K)
- General clean up of code
- V1.3 (November 2008)
- Unified Timer MACROS
- Re-arrangement of Target Vdd control routines
- Minor mods & corrected comments in bdm_syncMeasure()
- Reviewed stack size
- Increased cable_status.waitX size
- V1.2 (October 2008)
- Increased stack size (stack overflow was possible)
- Utilities (setBoot) updated to match.
- Other cosmetic changes
- V1.1 (August 2008)
- Vista compatibility
- V1.0 Initial Release
ToDo list
- Flash programmer for HCS08
Dear TBR Technologies,
The schematic does not have pin numbers on the Mini-usb connector and the layout of the pins is arbitrary. The pins are named correctly on both the schematic and pcb layout.
The placement of the ID pin at the bottom of the schematic symbol makes its layout compatible with the 4-pin connector symbol. It is not an 'error' since the relation between the pins on the symbol and the pins on the footprint are correct in the EDA software used. However it is certainly misleading. I'm sorry if this has caused problems. It will probably change in the next version 
bye
Dear All,
I've been asked to clarify how the versions of USBDM differ. The following summary of the USBDM Ver 2 designs is provided:
JB16 based versions (No longer recommended by me!)
These were mainly produced to be compatible with the previous hardware versions of OSBDM which was based on the MC908JB16. This is a USB low speed device.
There are several hardware designs supplied :
- Complete USBDM - Supports HCS12, HCS08, RS08 & Coldfire V1
- This is a complete fully-featured design using MC68HC908JB16DW (28 pin SOIC)
- Minimal TBDML 20pin SOIC - Supports HCS12, HCS08, Coldfire V1
- This is a very minimal design using MC68HC908JB16DW (28 pin SOIC)
- Minimal TBDML 28pin SOIC - Supports HCS12, HCS08, Coldfire V1
- This is a very minimal design using MC908JB16JDWE (20 pin SOIC)
- WTBDM08/12
- A commercial design available from Witztronics.
- OSBDM
- A previous design posted on Freescale OSBDM board
- HCS08-OSBDM+E
- A previous design posted on Freescale OSBDM board
JS16/JMxx based versions (Recommended by me)
These designs use either the MC9S08JS16CWJ (20 pin SOIC) or MC9S08JM60CLD (44 pin LQFP).
Both of these chips are USB2 Full speed but ONLY the first supports initial programming over USB without needing a BDM.
- Minimal design - Supports HCS12, HCS08, Coldfire V1
- This is a very minimal design using MC9S08JS16CWJ (20 pin SOIC).
- It is easier to construct and doesn't require a BDM for initial programming.
- It replaces the Minimal JB16 designs and is recommended (by me) for newbies!
- A PCB design is supplied but is should be possible to roll-your-own on a prototyping board.
- Complete USBDM - Supports HCS12, HCS08, RS08 & Coldfire V1
- This is a complete fully-featured design using MC9S08JM60CLD (44 pin LQFP).
- It has target power and various other options.
- It REQUIRES a BDM for initial programming.
- USBDM/CF - Supports HCS12, HCS08, RS08 & Coldfire V1, V2, V3 & V4
- This is a complete fully-featured design using MC9S08JM60CLD (44 pin LQFP).
- It has target power and various other options.
- It REQUIRES a BDM for initial programming.
Please note that these design are different from the Freescale OSBDM-JM60 design which was proceeding indpendently while I was doing the above designs
. Some future compatibility may be pursued.
Dear Macias,
I've had a chance to try this with a CN chip.
A process that does appear to work is as described above but select the CFV1 FSL debugger initially. This will produce copies errors but then changing to the correct interface in the debugger (once) and restarting seeems to work OK. It appears the the simulator option doesn't set up the Flash programming as it doesn't have any real flash .
So, in summary:
You can try the following process which should work:
- Set up a project as usual but select the CFV1 FSL Open Source ... as the debugger.
- Start debugging the project which will TRY to use the above debugger with lots of errors!
- In the debugger select Component->Select Connection
- Select CFV1 Open Source BDM
- Exit the debugger and start again
It should now be using USBDM/OSBDM. You should see the usual confirmation dialogue warning you that its going to erase the Flash.
bye
