topic Using COM API with HiWave Debugger in CodeWarrior for MCU

Using COM API with HiWave Debugger

jgirard1 — Fri, 17 Feb 2012 00:57:39 GMT

This is going to be a very difficult question to answer...

I have two version of CodeWarrior installed. One that I use for legacy programs and one for a new HCS08 program.

I have V4.6 and V6.3.

I have developed Matlab/Simulink tools that use the COM API to aid in the debugging of Stateflow charts. The tools use the COM API calls to control the debugger. The tools were originally developed using the V4.6 CodeWarrior for HCS12. When I run the tools and create a COM object within Matlab, it would create an instance of the V4.6 debugger.

Now, since I have recently installed the V6.3 CodeWarrior, when I run the tools to create the COM object, it wants to create an instance of V6.3 of the debugger. For some reason, the tools are not working with the V6.3 debugger because it is setup for HSC08. The V4.6 debugger is setup for HCS12.

Here is a snippet of my MatLab code that creates the instance:

% Constant definitions

HiWave_Path = 'j:\out\';

HiWave_Project = 'project.ini';

HiWave_Source = 'JLR_PEPS_KVM.abs';

% Declare access to global variables

global HiWave;

HiWave = actxserver('Metrowerks.Hiwave');

if (strcmp(class(HiWave), 'COM.Metrowerks_Hiwave'))

% Load the defined project

HiWave_Result = HiWave.ExecuteCmdRes(['OPENPROJECT ', HiWave_Path, HiWave_Project]);

end

Questions:

Is there a way to instruct which version of the debugger that the COM object creates?

Is there a way to get the HSC08 debugger to work with HSC12? It seems like it returns errors about missing library files, etc.

Re: Using COM API with HiWave Debugger

BlackNight — Fri, 17 Feb 2012 01:55:44 GMT

Hello,

I'm not a COM expert, but if I remember right there is a setting in the windows registry which tells where the executable is? At least that way you should be able to specify/change which version shall be used. I might be wrong.

To the second part: I'm not aware of any API changes between the two HI-WAVE versions, so the *should* work the same way. It would be useful to list te error messages you get. Maybe HI-WAVE is started with the wrong CPU settings, then it will complain about missing DLL's.

Hope this helps,

Re: Using COM API with HiWave Debugger

jgirard1 — Fri, 17 Feb 2012 02:43:26 GMT

The error messages I am getting are related to the BDM files. My configuration is as follows:

I have HCS12 BDM support integrated into the V4.6 install.

I have HCS08 BDM support integrated into the V6.3 install.

The legacy project, which is HCS12, requires HCS12 BDM type files to run properly. The newer V6.3 install was only integrated to run with HCS08.

I need to figure out how to get the HCS12 BDM files integrated with the newer V6.3 install. I am using P&E USB Multilink Interface (purple), which has InDART...something...something for the HCS08 driver and MultilinkCyclePro for the HCS12.

If I want both to run on the V6.3 install (not at the same time), I believe I need to get the HCS12 files installed. I probably need to dig up the install disk for HCS12 BDM drivers and run it.

Re: Using COM API with HiWave Debugger

CrasyCat — Fri, 17 Feb 2012 15:00:28 GMT

Hello

To inform the COM script which occurrence of the IDE should be started just run regservers.bat located in your CodeWarrior

{Install}\bin directory before starting the script.

This will update the registry accordingly.

CrasyCat