Combined TBDML/OSBDM Code

[pgo]

Dear HCS12/HCS08 users,

I use a HCS12 processor board in undergraduate labs.  To support programming these we made a number of TBDML programmers.  It was reasonably straightforward to extend the use of these to HCS08 through some simple modification of the OSBDM code.  Unfortunately, this had the disadvantage of requiring the flash in the programming hardware to be changed when moving between programming HCS12 and HCS08 devices.

There has been some discussion on these forums about combining the OSBDM and TBDML code to produce a single more flexible programmer.

To make this easier I have produced a combined version of the TBDML/OSBDM code.  It is also necessary to have a modified windows driver file TBDML.dll so that Codewarrior will talk to the modified BDM which identifies itself as an OSBDM.  The OSBDM windows driver file remains unchanged since the software remains compatible with TBDML (at least as far as HCS08 devices).
This code is attached along with brief instructions.

Please let me know if this is useful or if you have other comments - preferably through this discussion board.

Good Luck!

USBDM_Snapshot_2008_2_19.zip

Message Edited by pgo on 2008-02-19 07:10 AM

Message Edited by pgo on 2008-02-19 07:10 AM

Message Edited by t.dowe on 2009-07-28 11:21 AM

[pgo]

Dear Minush,

Restore the renamed DLLs.  They are needed!

The DLLs supplied HIDE ones in the Windows's system Directory - there is no need to rename anything.

bye

[Minush]

Ok pgo,

I renamed the DLL's files into gni directory because I got confussed when I read the help file where explains that. The explanation it's not really clear for me (sorry I'm new) and I'm not really sure about the right process to follow to install the USBDM. With your last answer I understood the next:

- Just copy the opensourcebdm.dll provided into gni directory (without renaming anything).

Is that all, do I have to do something more??, because I did that (just copy the file into gni directory) and codewarrior did not detect the USBDM (appeared "there ir not communication with the hardware" in the burning process).

Thank you.

[pgo]

Dear Minush,

Could I check the following please:

What hardware are you using - reference to a circuit on the web if possible.

Which of the image files did you program into the device.

Check if the BDM appears in the Windows device manager. It should appear under LibUSB-Win32 Devices as Open Source BDM.  Alternatively, run setBoot.exe which is in the USBDM Zip file.  Cut'n'paste the result.  It should give a report on the BDM if found.

Assuming the above works -

When starting the debugger do you get theUSBDM Configuration Dialogue that is shown in the help file within the USBDM Zip file?

If this appears, within the debugger try the HCS08 Open Source BDM->Show Status Command and report the result.

bye

[UcTechnoGeek]

pgo,

I'm having trouble connecting to the target hardware.  I'm using the Witztronics WTBDMS08 (http://witztronics.com/product_info.php?cPath=2_18&products_id=31)  which has the SN74VC1T45 transceivers (works great by the way, but would be kick butt if I could make it work for both S08/S12).  Because they are not tri-state transceivers (they are either input or output), I think there is bus contention.

Any ideas on how I could modify the code to work?

Thanks,
uCTechnoGeek

[UcTechnoGeek]

pgo,

I found the problem and now have a working board.

First, thanks for the great work.  Your coding style is very good.

Second, would you consider releasing the source for the ICPBoot.exe and TBDML.dll files?

Thanks again for all your hard work on this project.

Regards,
uCTechnoGeek