Problem with OSBDM : Continuous "Speed Change detected" message

[Lumbermatt]

Hello everybody,

We are two students who want to use the OSBDM for our university projects. So we designed two OSBDM which currently have a problem. The error we encounter is the same for the two BDMs.

The USB part seems to work well. The BDM is detected by Windows and Codewarrior and has been flashed in ICP mode without problems.

The target we want to debug works well in debug mode. We tested it with an other OSBDM and everything works perfectly. We even tried to force the target in debug mode when starting it up but this don't change anything.

When we start the debugger in CW, we have following errors :





The "command" window gives following output (the last line (speed change detected) repeats indefintly until we reset the OSBDM) :

Code:

Postload command file correctly executed.main 0x1B22'P TDiGdiGetFeatures()==> Features Already LoadedDiGdiGetFeatures()==> Features Already LoadedTrying to set Software Breakpoint at 0x01B22==> DI_ERR_NONFATALTrying to set Hardware Breakpoint at 0x01B22DiBreakpointSet()==> DI_ERR_NONFATALDiGdiGetFeatures()==> Features Already LoadedSTART FailedGDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_DISPLAYLINE)Target Speed Change Detected - New Speed 16.70 MHzGDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_DISPLAYLINE)Target Speed Change Detected - New Speed 16.70 MHzGDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_DISPLAYLINE)Target Speed Change Detected - New Speed 16.70 MHzGDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_DISPLAYLINE)Target Speed Change Detected - New Speed 16.70 MHz

We tried to upload a empty project, but the code don't get uploaded sine the original program on the target remains there.

We have tested almost everything we could imagine. If somebody had an idea it would be really great.

Thanks in advance.

Message Edited by Lumbermatt on 2008-05-23 12:16 PM

[Witztronics]

First a few questions:

Which version of the OSBDM are you using (hardware / software)?
Which version of CW are you using?
Which micro are you targeting?

My first guess would be that you are not communicating with the target device or it may not be in background debug mode.

Double check your connections from the JB16 to the level transcievers and to the 6-pin BDM header.
If you are using a BDM similar to our with the 74VC1T45 transcrivers, make sure you have the pull-up resistor and reset cap on the reset transciever input.
Check you crystal input on the target device.  Make sure it is within spec of the OSBDM you built.

From the debugger, go to the "HCS08 Open Source BDM" menu, select "Setup" and check the "show protocol" box.  Save the debugger configuration and when you re-connect you will see all the data being sent/received via the BDM.  This may give you a better idea of what is going wrong.

If all else fails, buy one of ours :smileyhappy:

[Lumbermatt]

Ok we resolved the issue this morning. It was a simple error in the schematic. The BDM_DIR line was connected to PTD5 instead of PTC0.

The OSBDM now work well and can debug the program we wrote for an AW60 devboard.

Thanks again for your help.

Regards.