topic HC12 target communication problem with P&E USB Multilink in CodeWarrior for MCU

HCS12 target communication problem after upgrading from CW HCS12 3.0 to C.W. 3.1

rimh — Tue, 31 Jan 2006 18:43:37 GMT

Hello

I have a strange problem where the true-time-simulater and debugger for an identical Codewarrior HCS12 project is no longer able to successfully communicate with the target MC9S12DP256B via a P&E USB Multilink after upgrading from CW HCS12 3.0 to CW 3.1.

The communication port and speed setting seems to be identical, and they use the same fpp definition and P&E ICD.ini settings file.

The only clue I found is that the command log on CW 3.1 (see below) shows an erroneous address for the flash block 1, "bad device", whereas under CW3.0 this is not the case.

But I have not been able to determine where to correct this ...

Any help would be most welcome!

Command log:

FLASH parameters loaded for MCS912DP256B_V4 from C:\Program Files\Metrowerks\CodeWarrior CW12_V3.1\prog\FPP\mcu03C6.fpp

MCU clock speed: 296747000 Hz
Block Module Name Address Range Status
0 FLASH_4000 4000 - 7FFF Enabled/Blank/Unprotected - Unselected
1 FLASH_C000 C0C0 - 1C0BE Bad Device - Unselected

Re: HCS12 target communication problem after upgrading from CW HCS12 3.0 to C.W. 3.1

hdj100r — Thu, 02 Feb 2006 19:49:33 GMT

Hi,

I had a very similar problem when updating from Ver 3.0 to Ver 3.1 with the DP512 processor. It turned out that the fpp file in 3.1 was broken, and I was sent a new one from Metrowerks, and that fixed the problem. As the DP512 and DP256 are pretty similar, I would think that a similar problem could exist.

I actually found that if you copied the v3.0 fpp file into V3.1 it also seemed to work.

What I find very disappointing is that as far as I can see there is no mention of this problem or any bug fixes which rectify the issue, so people waste vast amounts of time trying to get around bugs which are known to Metrowerks/Freescale. This bug was reported and fixed in March 2005.

Cheers

David

Re: HCS12 target communication problem after upgrading from CW HCS12 3.0 to C.W. 3.1

rimh — Sat, 04 Feb 2006 15:42:45 GMT

Hello David

many thanks for your suggestion! But I had already tried that, to no avail ...

Best regards
Robert

Re: HCS12 target communication problem after upgrading from CW HCS12 3.0 to C.W. 3.1

marc_paquette — Thu, 09 Feb 2006 02:04:48 GMT

I forwarded your post to tech support. Without knowing more information to work with, tech support suggested that this patch might correct your problem:

ftp://ftp.metrowerks.com/pub/updates/CWHC12/CW12_V3_1_ICD12_USB2_0_Sim_patch.exe

From the release notes:

CW12 V3.1 USB 2.0 Service Pack Release date: 1/11/2005

CW12_V3_1_ICD12_USB2_0_Sim_patch.exe contains simulation updates and P&E Microcomputer interface DLLs for CodeWarrior Development Studio for HC12 Microcontrollers, Version 3.1. The updates include the following:

Simulation
- Updated ECT module simulation to match silicon performance
- Correct memory map
P&E interface DLLs
- Option to connect to a running target - "hot plug"
- Option to insert control points "live" on HCS12 derivatives that allow the on chip break module to be modified while the CPU is running.
- Option to ensure no device memory accesses while CPU is running.
- Option to Resynchronize from COP/watchdog reset
- Improved, faster FLASH programming support
- "Banked Memory Location" dialog has been replaced by a more general purpose Debugging Memory Map dialog and manager
- Support for P&E USB 2.0 BDM Multilink cable (USB-ML-12 rev. B).
- Latest P&E firmware will be downloaded to cables automatically.

The use of the USB 2.0 BDM Multilink interface for HCS08 and HCS12 microcontrollers are fully supported on the following operating systems: Microsoft Windows 98, 2000 and XP.

NOTICE: If a derivative specific service pack has been installed, this HC12 USB 2.0 Service Pack will replace the installed dynamic link libraries, flash programming algorithms and other functional binaries with updated versions.

It is not recommended to install derivative specific service packs that were released prior to January 2005 once the HC12 USB 2.0 Service Pack has been installed. The HC12 USB 2.0 Service Pack cannot be removed once installed.

This archive was submitted on 1/11/2005 and occupies 4.7 MB of disk space.
You can download it at URL:

Download Update (4.7 MB)

Marc.

Re: HCS12 target communication problem after upgrading from CW HCS12 3.0 to C.W. 3.1

rimh — Thu, 09 Feb 2006 16:32:59 GMT

Hello Marc

The CW12_V3_1_ICD12_USB2_0_Sim_patch update did the trick -- thank you so much!

(Since the CW 3.1 installation that I had just downloaded a little while ago has a later date and because this problem had not been there with CW 3.0, it hadn't occurred to me to look for an update!)

Best regards
Robert

Re: HCS12 target communication problem after upgrading from CW HCS12 3.0 to C.W. 3.1

Lola — Thu, 23 Feb 2006 16:27:21 GMT

Hi,

I have the same problem with the DP512, installing the patch has not fixed it. I haven't CW v3.0. Where can I get the fpp file?

Thanks,

Lola.

Re: HCS12 target communication problem after upgrading from CW HCS12 3.0 to C.W. 3.1

marc_paquette — Wed, 01 Mar 2006 23:30:36 GMT

Attached is "Mcu03cd.fpp", for MC9S12DP512, from CodeWarrior for HC12 v3.0.

Make a copy of the 3.1 version of this file and set it aside before placing this attached file in the prog\FPP subfolder of the CodeWarrior CW12_V3.0 folder.

Let me know if this file fixes your problem.

Marc.

Mcu03cd.zip

Message Edited by t.dowe on 2009-09-03 06:04 PM

HC12 target communication problem with P&E USB Multilink

hooligan — Sun, 12 Mar 2006 19:39:16 GMT

Hello

I have a strange problem where the true-time-simulator and debugger for a Codewarrior HC12 project is no longer able to successfully communicate with the target MC68HC912B32 via a P&E USB Multilink i try all the previous solutions but it doesn't work