Running "Lean and Mean" on a travelling laptop

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

Running "Lean and Mean" on a travelling laptop

2,748 Views
Curt
Contributor IV
OK -- I have CW loaded on my Win98 laptop, and I am impressed.  But my sole, only and exclusive interest is in writing assembly language for the 'RS08 -- and it's clear that CW5.1 does a whole lot more than this.
 
So my question is:  which files can I safely delete from my CW5.1 folder to get down to a lean, mean RS08-asm machine?   Does anybody here have a script for euthanizing unneccessary files from Code Warrioin this context?
 
My usual practice is to move anything with a ".h" or ".c" or ".cpp" extension to a "trash" folder and then see if I can still do an assembly.  If so, everything in the trash folder goes to code heaven.  Will that work here?
 
 
 
Labels (1)
Tags (1)
0 Kudos
Reply
5 Replies

1,592 Views
bigmac
Specialist III
Hello Curt,
 
For absolute (not relocatable) assembly projects for HC08, I often do not use the CW IDE (as this requires the complex project directory structure), but run the assembler and debugger as stand-alone tools.  I assume this would also be OK for the 'RS08 tools.  I use my own preferred text editor on these occasions.
 
For simplicity, I would generally put the main asm file, and all the include files required for a project in a single project folder.  So you would need to keep separate copies of the include files that define the registers for the MCUs you are using.
 
Suggest you copy the more obvious files associated with the tools into a separate program folder, and attempt to run.  The error messages should then indicate what other necessary files are missing, or at least some of them.  There are quite a few files associated with the (hiwave) debugger, and fewer for the (ahc08) assembler.  Probably not much point in listing all the files because the 'RS08 tools probably use different file names.  However, some of the extensions applicable to the debugger - exe, dll (multiple files), hlp, fts, tgt, gid and wnd (multiple files).  You will also need to copy your licence.dat file into the new folder.  There may also be other MCU specific files required for debug and programming.
 
With this approach, you don't need to erase anything from the laptop until you are sure each tool works properly.  And then you can simply de-install CW from its "normal" location.
 
Regards,
Mac
0 Kudos
Reply

1,592 Views
CompilerGuru
NXP Employee
NXP Employee
One possible trap with this approach is that some drivers (I think of usb drivers) have to be installed into the windows folder. So when uninstalling they might go away too, and then the carefully extracted debugger might stop working.
It may also just work fine, depends on how you connect to the target, just be careful.

Daniel
0 Kudos
Reply

1,592 Views
Curt
Contributor IV
I've done some poking around in the files, but haven't found the stand alone assembler
or debugger yet.  Did drop all the .h, .c and .cpp files though (lots of 'em), and now get some error messages when the IDE launches -- nothing critical though, and I'm still able to do assembles and debug just fine.
 
I like the IDE, and think I'll be able to shrink it more as I learn to use it.
 
0 Kudos
Reply

1,592 Views
peg
Senior Contributor IV
Hi Curt,
 
Most of the major components to which Mac refers are found as .exe's in the prog directory under the main Codewarrior installation directory.
You can just start these from here to run the individual components seperately. Perhaps a good idea before doing any moving/stripping.
If you could document this procedure I'm sure others would be interested.
 
0 Kudos
Reply

1,592 Views
rocco
Senior Contributor II
Here is the tedious way that I determine what files are required.

A few files at a time, I will append a ".tst" extension to the filenames of the files that may be unnecessary, preserving the old extension in front of the ".tst". I then do a test compile, to see if anything barfs. If everything runs fine, I leave the ".tst" appended to the filename.

Since you never know when you might change something that causes the required files to change, I leave them that way for at least a few months. If something should fail to work later, I will go through the even more tedious process of determining which one of those files were required.

When I am comfortable that a particular file is unnecessary, I will delete it. Usually about a year later.

Message Edited by rocco on 2007-03-2301:39 PM

0 Kudos
Reply