topic Re: Communication with the target failed: The target MCU has no clock or wrong BDM clock speed is used or derivative is secured. in CodeWarrior Development Tools

Communication with the target failed: The target MCU has no clock or wrong BDM clock speed is used or derivative is secured.

gjjude — Tue, 08 Nov 2016 09:02:57 GMT

Hi Everyone,

I'm trying to erase the memory from the HCS12 Microcontroller. Upon doing so, I encountered the following errors attached in the word document.

First error seems to be:

Communication with the target failed:

The target MCU has no clock or wrong BDM clock speed is used or derivative is secured.

Will you be able to help me resolve the issue, and what are the necessary troubleshooting steps from this:

Regards,

Jude

Re: Communication with the target failed: The target MCU has no clock or wrong BDM clock speed is used or derivative is secured.

ZhangJennie — Wed, 09 Nov 2016 02:58:05 GMT

Hi Jude,

Commonly, if you meet “fails to find communication speed” error, The problem is caused by BDM wrong clock detection or BDM debugging interface connection. please consider the following possible reasons.

First, May I suggest you test your BDM Multilink, USB cable, board with another PC to confirm if the firmware and hardware are in good condition.

it is necessary to check if your USB BDM Rev C firmware is still in good condition. And also check if the USB cable is in good condition too! Any damage in BDM firmware itself will prevent the connection.

if you are using demo/evb board, you need check if the jumper are setting well. You need to check if osc is in normal condition as well

1.This issue may be caused by a driver conflict. P&E's lastest driver download “P&E Hardware Interface Drivers v12 ” ( http://www.pemicro.com/support/download_processor.cfm ) .

2 If you can not load any SW into the MCU it is more probable that the MCU is secured.

Sometimes when you change the MCU on the BDM it can happen that MCU get secure (depends on internal MCU memory configuration and the last debugger configuration). There are two possibilities how to unsecure the MCU:

a) use external unsecure SW – can be downloaded from pemicro.com. (You have to create your own account to get access to Unsecure_12) Unsecure_12 (27932 KB): Utility which unsecures HCS12 devices via P&E's BDM Interfaces such as Cyclone-PRO, USB-ML-12, and BDM-Multilink. http://www.pemicro.com/support/download_processor.cfm

Unsecure_12 Help Files: This .hlp file describes the use and operationg of the Unsecure_12 program which is used with P&E's interface devices to unsecure proeviously secured HCS12 microcontrollers.

Regarding wrong BDM clock detection:

You could workaround this by detection the BDM speed manually:

BDM clock problem

BDM needs IO_DELAY_COUNT value to be set. This value should be detected automatically, but check it for your debugging HW and oscillator frequency. You could go to menu “MultilinkCyclonePro”, “Set Communication Speed” to check this option.

Please check also your connection, communication settings in CW debugger menu.

As you can see the value is depending on your debugging HW tool and oscillator clock.

Disable the “Auto detect” and set the number depending on your oscillator frequency and debugging tool. For example: I use USB BDM Multilink 2.0 and 16 MHz osc.

IO_DELAY_COUNT = (240/16)-1 = 14. But I should also try the values near 14 (13, 15)

Wrong target is set in the debugger.

Please go to menu “Component”, “Set connection”, And also menu “MultilinkCyclonePro”, “Derivative” to check if you have set the right target.

Next thing which is suitable to be set (mainly if PLL is used is) in TTSRTD is: Main Menu-> MultilinkCyclonePro ->Communication->Special setup->match: Set CLKS bit in BDM…..

6 Check whether your “USB multilink, ….” is active. It sometimes happens to me that even it is connected and powered the signal diodes on the USB multilink are off => USB is inactive.

7 Check whether MCU has correct clock signal on the EXTAL pin (2.5V), XCLKS=log.1.

This may be caused by wrong osc. circuit or e.g. cold-soldered junction on your PCB osc. circuit… BDM connection problems may be caused by bad oscillator clock signal too.

Please check your oscillator signal with scope.

Check clock source and osc. mode (Pierce-External/Colpitts) settings (XCLKS pin).

Please also check on your PCB schematics design:

Do you have the TEST pin connected directly to GND?

Do you have the MODC (BKGD) pin connected to Vcc via pull-up resistor ~3.3k?

Do you have any external reset circuit or capacitor connected to MCU reset pin?

Note: You should NOT connect any capacitor to MCU RESET pin (It is causing reset signal malformation).

You should NOT have any copper plane under osc. circuit.

Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: Communication with the target failed: The target MCU has no clock or wrong BDM clock speed is used or derivative is secured.

gjjude — Mon, 14 Nov 2016 08:50:45 GMT

Hello Jennie,

Thank you very much for the information. Have you tried to check the attached file I sent? Is it expected that the first error that showed up, will result to the next following errors.

Also, can you help me or provide me with a step by step process, on how to completely erase the contents from my memory. I guess I need to start with a fresh memory first.

Regards,

Jude

Re: Communication with the target failed: The target MCU has no clock or wrong BDM clock speed is used or derivative is secured.

ZhangJennie — Tue, 15 Nov 2016 07:52:15 GMT

yes. I checked your doc file. above is the checking list I provided.

in addition, please verify the problem is in the specific project or a common issue for all project.

if the problem is only in one project, send the project here, we can test it.

Have a great day,
Jennie Zhang

Re: Communication with the target failed: The target MCU has no clock or wrong BDM clock speed is used or derivative is secured.

gjjude — Wed, 16 Nov 2016 06:50:51 GMT

Hello Jennie,

Please see attached code. We are testing it first only in this project. Can you try it on your side. Basically, the microcontroller is connected in the Freescale board which is attached to NI ELVIS board.

Regards,

Jude

Re: Communication with the target failed: The target MCU has no clock or wrong BDM clock speed is used or derivative is secured.

ZhangJennie — Thu, 17 Nov 2016 03:20:38 GMT

Hi Jude,

I don't see your demo code under your post. this what I see from my side

can you please post your project again?

Have a great day,
Jennie Zhang

Re: Communication with the target failed: The target MCU has no clock or wrong BDM clock speed is used or derivative is secured.

johnjferris — Tue, 16 Apr 2019 17:46:30 GMT

I was looking for answers because I had same problem. I found obvious problem. ON/OFF switch in off position.