topic Re: MCF5225x Debug Interface problem in ColdFire/68K Microcontrollers and Processors

MCF5225x Debug Interface problem

wl5684 — Wed, 26 Sep 2018 12:19:31 GMT

I have a trouble with the MCF5225x-TWR debug interface. My debug tool is multilink universal. The usbdm mode runs fine on the demo board. But when I try to debug the board with multilink universal throgth the 26-pin interface. The retry interface appears ,and I can‘t connect to my target at all. But out project board is the 26-pin interface, which means I can't debug our board at all. Can anyone help me with the problem? I'm looking forward for your reply.

Thank you very much!

Re: MCF5225x Debug Interface problem

miduo — Thu, 27 Sep 2018 08:38:34 GMT

Hello,

Please let me know what IDE you used for the programming? The CW? And what version? What is the " project board" you mentioned? The customer board or our evaluation board?

Re: MCF5225x Debug Interface problem

wl5684 — Thu, 27 Sep 2018 12:44:07 GMT

Hi,

Thank you for your reply! My development software is Codewarrior V10.7. The "project board" means the customer board, which is designed by us.

Re: MCF5225x Debug Interface problem

wl5684 — Thu, 27 Sep 2018 13:26:42 GMT

Hi，

My development sofware is codewarrior 10.7. The project board means our customed board. And my OS on PC is 64bit win7, i think this

message may be help with the problem.

I also want to

~~-Original~~-

Re: MCF5225x Debug Interface problem

miduo — Fri, 28 Sep 2018 07:29:09 GMT

Hello,

Got it. So first please check the jumper settings for the TWR-MCF5225X especially the J14, J15, J16, all them should be on 1-2.

Please pay attention to SH1 resistor which is not installed at default, however it is used to connect MCU_RSTOUT pin to pin 1 of BDM header, so please make sure to install this resistor. This signal is to used checking if the MCU has come out of reset.

And from software side, please download updated Multilink driver from P&E micro at:

http://www.pemicro.com/downloads/download_file.cfm?download_id=346

Re: MCF5225x Debug Interface problem

wl5684 — Sat, 29 Sep 2018 06:35:30 GMT

Hi,

I'll try it. I didn't place the SH1 resistor on the board. Thankyou for your support!

Re: MCF5225x Debug Interface problem

wl5684 — Sat, 29 Sep 2018 08:18:45 GMT

Hi,

I have placed the SH1 resistor and update the driver of the Multilink Universal debugger, but I just can't connect to the target either. I also check the cable of the connecter, I found the Pin24(PSTCLK) is disconnected! I have recovered the cable, but it doesn't work. Is there any other method I should try to solve this problems? It troubles me.

Thank you!

Re: MCF5225x Debug Interface problem

wl5684 — Sat, 29 Sep 2018 08:46:21 GMT

Hi,

I found the Pin 1 of the 26-pin PE debugger connector is NC(however the TWR-MCF5225x demo board is MCU_RSTOUT singal) , so whether place the SH1 resistor will not affect the connection between the debugger and the board. I found Pin 26 of the 26-pin PE debugger is TA (however the TWR-MCF5225x demo board is NC). Is there some design problem of the demo board? I seems that Pin1 and Pin26 signal is reverse.

Re: MCF5225x Debug Interface problem

miduo — Sun, 30 Sep 2018 17:05:08 GMT

Hello,

First the schematic of the TWR-MCF5225X is correct. Let me try to explain. regarding the SH1, actually the SH1 leads the reset out signal from MCU to BDM, that will tell if the hardware reset is issued successfully. If you would use the BDM connector instead of the OSBDM, the SH1 should been installed.

For the PIN 26, it is really no need for BDM debugger, so leave it open is OK.

Please pay attention to PSTCLK, this is an important pin need for BDM communication, I am confused that you mentioned this pin is "unconnected"

Re: MCF5225x Debug Interface problem

wl5684 — Mon, 15 Oct 2018 07:11:13 GMT

Hi,

Thank you for your reply. I mean the cable of PSTCLK signal between debugger and target board is unconnected. But I have changed a new cable, but the appearance is the same. Now I changed the debugger to USBDM , now it works fine with the 26-pin connector!