Codewarrior 10 Can't Debug

[sebasira]

Well, hello everyone!!!

I manage to get a project to build with this new version of codewarrior. I'm using v10 on a win7 64-bits. I've installed the driver version 10 from P&E. and I'm using a USB BDM connected to a QE32. This worked fine on a winXP PC with Codewarrior v6.1

When I click on "debug" the following screen appears:

'Launching My_Project_MCF51QE32_Internal_Flash_PnE USB BDM' has encountered a problem.

ColdFire GDI Protocol Adapter: Can't connect. The Debugger can not connect to the PnE BDC interface or targetted hardware board.

This also appears on the CONSOLE:

Info: USB-ML-12 detected - Flash Version 5.83
Info: USB-ML-12 detected - Flash Version 5.83
Error: Connect failed.
Error : The Debugger can not connect to the P&E BDC interface or targetted hardware board.

 I guess it maybe a driver problem. How can I fix it?

One more thing... when I first ran the debugger an unusual screen appears with a picture of a blue BDM and said something like "updating firmware or software". I've never seen it before and haven't seen it again.

Please help... I can`t go further from here if I cannot debug or even download firmware to my hardware

Thanks Everyone!!!!

[sebasira]

I've got some more information that may help you help me.

I said I use an USB BDM, well actually it's a demoJM board used like a BDM... I don't put any daugther card and connect to my board using BDM pins... That worked fine for me on win XP, CW 6.1

When I first try to debug with this demoJM with Codewarrior v10 on Win 7, I said a screen appears with the image of a blue BDM, and it actually says updating firmware (I assume BDM's firmware)... That happen t0o fast for me and couldn't see well.

Now I have a "real" USB BDM, not the demoJM board... I just plugged it and work fine on win7 Codewarrior v10. The screen with the blue BDM appears again says updating firmware, and when it finished it said updated succesfully.... Then I went back to the demoJM an happend the same as the post above.

I've notice 2 things. There are 2 "CW v10 MCU"  fodlers, one on Program Files and the other under Program Files (x86)

1- The one inside Program Files has a Driver folder wich contains a folder named  "osbdm-JM60". I assume those are the drivers for the demoJM board BDM. It's sourprise me that it says OSBDM... it's an OpenSource BDM? Because when I created the project I didn't choose OSBDM, I've chosen P&E USB MULTILINK BDM

2-The folder inside Porgram Files (x86) has a folder named "pemicro" wich is the same folder I've got on win XP. I assume those are the drivers for the USB BDM

I just went to my win XP PC... I've not installed CW 10 there, the demoJM works fine as a BDM... and the fodler "osbdm-JM60" does not exits...

Any clue? Now I'll try installing CW 10 on win XP and see if the demoJM works

As always thanks!!!

[peg]

Hello Sebastian,

It would appear that you have the problem detailed here.

CW10 probably still deliberately breaks this as 6.3 did.

"osbdm-JM60" refers to the open source BDM made with a JM60

Refer to the community projects section of the fora.

[sebasira]

It doesn't even work on a win XP PC... That's bad... really bad... I can't continue with my applications!!! Is any way to solve that? I mean, is there a way to use demo JM Board with CW 10?????

I'd really appreciatte any help here!!

Best of lucks!

One more thing: the DEMO JM Board has a P&E Multilinkd BDM embedded, it's not an OSBDM, right?

[peg]

Hello,

It seems I forgot to link in what I was talking about. https://community.freescale.com/message/49272#49272

The embedded BDM in the Demo JM board is indeed a P&E Multilink.

Supposedly it has less protection fitted to it than the real thing but retains ALL of the functionality in the hardware.

Where the problem comes is that since Codewarrior 6.2 (6.3?) a supplied DLL deliberately hobbles the embedded multilink into only communicating with the type of device that the board is meant to be a demo for.

There is no technical reason for this!

Neither is there any reason given by Freescale.

The problem seems to be that the demoboards identify themselves as a DEMOQE or whatever.

Later DLL's pick this up and then deliberately do not allow any other device.

A hack to bypass this is detailed in the linked thread.

I don't know whether this works with CW10. Please let us know.

[sebasira]

Peg... well I read the whole thread about the hack, but there's no folder "prog" under CW 10 installation path. There's new one named "Drivers" but under it there aren't such DLL files...

I found a "prog" folder under other one named "MCU" but those files weren't there, neither.

What can I do?

Beste Regards

[peg]

Hi Sebastian,

I don't generally use Codewarrior, so I don't have CW10 installed nor the time to muck around with it now.

Your options at the moment are:

1. Use CW6.1.

2. Use a real Multilink

3. Figure it out for yourself, post the method here and become a legend

[sebasira]

Well peg, as I need to continue my development kind of  "right-now" I decided to try using CW 6.1 over win 7 x64... I'm having some problems and I open a new thread, here it is.

I think you may help me, I've noticed you had a lot of participation in every thread I mention.

Please, unless any of you find a solution to "Using a DEMO BOARD to Debug a MCU different from what the demo board was ment to with CW 10 over win 7 x64" do not reply on this thread... I'll continue in the new one, linked above.

Thanks everyone!

[sebasira]

Peg, thanks for the linked thread! I'll take a look a it and see if this solve my problem... Any news I have, I'll let you know!

Thanks! have a nice day

[kef]

What MCU are you trying to debug with DEMOJM? I think DEMOJM can be used to debug only MCU's it was designed for: S08 JM128 and CFV1 JM128. And nothing else, I think. It is similar with DEMOQE board. I can debug QE128. But if I choose for example QE32 or QE64, it won't connect. CW V6.1 allowed connection to other MCUs, but not more recent CW versions. Do you have problems connecting to original DEMOJM MCU modules?

[sebasira]

Well Kef, I'm using it to debug a CFV1, it's a QE32... Works fine with CW 6.1 over win XP. So you say that codewarrior versions above v6.1 won't let me connect to other MCU different from JM?

I haven' try with the daugther cards yet.. It's a good test, I'll give it a try and let you know

Thank you!