HC12: trouble with automation

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HC12: trouble with automation

Jump to solution
1,855 Views
aarons
Contributor I
I'm trying to use CmdIDE.exe to automate our build process, but I think the documentation is out of sync with our actual version of CW. Specifically, the documentation says I can get to the command window by going to View->Command Window from the IDE. There is no such option in the view menu.

Also, when I run cmdide either via the explorer shell, cmd.com, or through cygwin, all I get is the prompt "Metrowerks CodeWarrior IDE. Hit /? for help" with no prompt. It doesn't seem to respond to any other input at that point.

This is with CW IDE 5.5.1272 from version 3.1 of the HC12 compiler.

Originally we had a build application written in C# using the COM interface which worked, but unfortunately we have two versions of CW installed (one for the HC12, and another for the HC08) and I can't find a way to specify which platform I'm building for with that interface.

Does anyone have any pointers for getting this working?

Message Edited by CrasyCat on 2007-04-13 11:13 AM

Labels (1)
Tags (1)
0 Kudos
Reply
1 Solution
1,051 Views
CompilerGuru
NXP Employee
NXP Employee
The command window is not being delivered with HC12 or HC08 as we do not include debugger parts of the CW ide.
The simplest way to pick the right ide with COM is to call the bin\regserver.bat of the ide you want to control before you create the initial connection.
I think also launching CW and then using COM to connect to the currently running ide works, but you never know how long you have to wait until the ide is really up and running, so I prefer to let COM start the ide.
Notes:
regserver.bat supports /s as option, then it does not stay open.
Use the bin folder as current directory when launching regserver.bat, I think it is a bit limited in this respect.
Simple builds can also be done with CmdIDE.exe, it has some options to let you specify the mcp and the build target. However it is not an interactive shell, it just pipes through the output of the build process happening inside of CW.

Daniel

View solution in original post

0 Kudos
Reply
1 Reply
1,052 Views
CompilerGuru
NXP Employee
NXP Employee
The command window is not being delivered with HC12 or HC08 as we do not include debugger parts of the CW ide.
The simplest way to pick the right ide with COM is to call the bin\regserver.bat of the ide you want to control before you create the initial connection.
I think also launching CW and then using COM to connect to the currently running ide works, but you never know how long you have to wait until the ide is really up and running, so I prefer to let COM start the ide.
Notes:
regserver.bat supports /s as option, then it does not stay open.
Use the bin folder as current directory when launching regserver.bat, I think it is a bit limited in this respect.
Simple builds can also be done with CmdIDE.exe, it has some options to let you specify the mcp and the build target. However it is not an interactive shell, it just pipes through the output of the build process happening inside of CW.

Daniel
0 Kudos
Reply