Codewarrior debugging problem

[kenchill]

Hi all,

I'm using CodeWarrior for MCU, Version: 10.5, Build Id:130916 and evaluating a MC9S08PT60 using the TWR-S08DC-PT60, I cannot get debbuging or programming working correctly.

The PC is running Windows 8.1 and has an Intel i5-3330S 2.70GHz processor.

I bought three TWR-S08DC-PT60 in case there was a hardware problem, they are from two different batches but with the same hardware revision (REV A0) - so it is unlikely that the problem is there.

When debugging is started I get the "P&E Connection Assistant" dialog saying "An error occurred while connecting to the interface hardware...." the boxes in the dialog show the correct hardware, pressing retry brings up the same window or brings up the "Power Cycle Dialog".

After many retries an error box eventually comes up saying "Error launching xxxx_FLASH_PnE U-MultiLink HC/RS/S12Z GDI Protocol Adapter : Can't connect. The Debugger can not connect to the P&E device" (the xxxx being the project name).

The odd thing is I can eventually get one of the boards going after trying many-many times by re-connecting, pressing board reset now and again, drinking lots of tea, standing on one leg, etc - this may take 60 plus tries - but once it is going it works fine.

I was hoping that the problem would show its ugly head but now I am ready to start a prototype run and I am no wiser - could it be a processor multi-threading issue, I had this with COM ports and VisualStudio ??

Is there anyone out there who can help with this problem, please ??

[Jorge_Gonzalez]

Hello Ken:

I'm just guessing here, but I wonder if the problem is related to your OS. P&E drivers support Windows 8, but I'm not sure about 8.1.

- Have you tried with a different computer?

- When using Multilink, both LEDs must be on. And also we have known of cases with defective ribbon cables.

Some extra help from colleague Erich Styger that could narrow down the possible causes:

- For general debugging rules:

“An error occurred…”: Applied Debugging Rules | MCU on Eclipse

- In cases with corrupted or malfunctioning USB drivers:

Fixing the USB Drivers | MCU on Eclipse

- If you have a memory overlap but you do not see it:

Problem Occurred: Flash programming with overlapping memory | MCU on Eclipse

I hope some of this solves your problem. Keep us posted.

/Jorge Gonzalez

[kenchill]

Hello Jorge

I'm replying to your response here as I can't seem to login to Freescale

community to reply there.

Thanks for your response, but I've tried your recommendations with no

success, I have an old XP laptop with CodeWarrior 10.5 on it which has the

same problem, I tried CodeWarrior 6.3 (on the laptop as it won't work with

64bit win8) but this wasn't any help as there is no support for the S08 P

series. I have the same problems with Freescale's sample projects as well as

my own.

I've ordered a PE multilink to check if that works.

I will look deeper when the multilink turns up and try some of the Freedom

dev boards I have to try and pinpoint the problem.

I'll answer the discussion properly once I can login.

Regards

Ken Roberts

[Jorge_Gonzalez]

Hi Ken:

I guess you replied from your email, right? You don't have to worry, your response is automatically added to this conversation in community.

Now, your last comment was strange:

"I've ordered a PE multilink to check if that works".

But in your original post the error you received was:

"Error launching xxxx_FLASH_PnE U-MultiLink HC/RS/S12Z GDI Protocol Adapter : Can't connect. The Debugger can not connect to the P&E device"

So, what is the actual interface you are using right now with your boards? If you are using the mini USB OSBDM/OSJTAG, so the connection selected is not correct.

Let us know more details.

Regards!

Jorge Gonzalez

[kenchill]

Hello Jorge

I'm trying to use the TWR-S08DC-PT60 demo board, I have three of these and I

can get one going as per my original post if I keep retrying about 20 to 60

times !! The other two don't want to work, although once it works it carries

on working fine all day - to me it seems like a BDC clock sync problem (of

course I may be totally wrong) . I'm guessing these demo boards have a cut

down version of the PE multilink.

Regards

Ken...

[Jorge_Gonzalez]

Hello Ken:

Sorry, I mixed boards and thought you were using TWR-S08PT60, when you actually have TWR-S08DC-PT60.

From my side I created a new project and flashed a TWR-S08DC-PT60 with no problems, so I'm actually out of ideas here :S, other than the ugly and not certain uninstall/reinstall CodeWarrior.

Let's see if the P&E Multilink you ordered gives us some clue. Or you can always submit a service request if you see no possible resolution.

Regards!

Jorge Gonzalez

[kenchill]

Hi Jorge,

My PE Multilink has arrived and it worked first time without problems, both

on the new Win8.1 PC and the old XP laptop.

So I guess the firmware on the TWR-S08DC-PT60 is out of date, I did have a

look to see if there was any update but I've found nothing.

There are three labels on the TWR-S08DC-PT60 boards (apart from the serial

number) these say: "FW V1.0", "700-27325 REV B" and "SCH 27325 REV B", are

you aware if there are any firmware updates?

Thanks for you help, I can now start a pre-production trial.

Ken...

[Jorge_Gonzalez]

My board has exactly the same labels. And I think whenever the firmware is outdated CodeWarrior should warn you and either upgrade it automatically (for Multilink) or prompt you to change a jumper setting so the debugging MCU can enter in bootloader mode. So this is still odd to me.

However, it is great that you are moving on! :smileycheck:.

/Jorge Gonzalez