CCS Version: 4.0.1.01001 *** No rule to make target

 It sounds like the path to the runtime library rts2800_ml.lib is hardcoded to the default path in CCS 3.3 during the migration.

Go to the Project Build Properties->CCS Build Settings, and for Runtime Support Library, click on Browse and select it from the CCS v4 install path (default path would be C:\Program Files\Texas Instruments\ccsv4\tools\compiler\c2000\lib). Then try rebuilding the project.

I believe you are right, however,  I tried your suggestion, but encountered a warning window  when I applied the change. The warning  message is as follows…

Problem encountered while initializing build-configuration 'F2802x_RAM' of project 'FlashingLeds'. Please see the migration.log file, in the root of the project, for details.

The migration.log file only has one statement

!ERROR: Unresolved source file: F28335_FLASH_FlashingLeds.CMD

I was then exited out of the Project properties window without the changes saved.

I looked at my other PC with the c: drive and it has the same message in the migration.log file, but I do not seem to have any trouble loading the program into my F28027 target and blinking the LED. Is this ERROR message a problem I should be concerned about on this PC?

I think I am going to continue my development on the older PC with the C: drive. This is no problem for me. AND return my newer PC to IT and inform them to never give me a PC with no C: drive (Not sure why they did that anyway)

If you wish, for your own information, I would be glad to keep trying to get this PC to work. Just let me know.

Thanks

My gut feeling is that it doesn't have to do with the D: drive, but I could be wrong.

Is this project migrated from CCS 3.3 or 3.1? And are you saying that the same project migrated in a similar manner works fine on CCS v4 installed on a different PC?

If after making the change to select a different runtime library it did not save the changes, then you're not going to get a successful build.

Can you try making a copy of your active configuration (Debug or Release) and then modify that copied configuration to select the runtime library from the appropriate path?
To make a copy of your active configuration:
1) Go to Project Properties->C/C++ Build
2) Click on Manage next to Configuration
3) Click New, give it a name, and select Copy Settings from Existing configuration (Debug or Release)

Now you should have a new configuration which you can make active, try to update the runtime library for this and see if you can save changes and build.

Yes I did migrate this project from the FlashLED project that I downloaded from your website for the F28027 Experimenters kit. I am not sure what version of CCS that it was originally generated for. Yes I did perform the exact same steps on my older PC and was able to compile and blink the LED. If its not because of no c: drive then maybe it is something to do with XP64. I am new to CCS and have not been able to find any detailed users guides for CCS v4.0. It would be helpful to have documents for the compiler and linker. I will continue playing around with this problem, but my main goal is to get your  FOC motor control software running. So, since my old computer is working, I downloaded your MotorCtrl+PfcKit and migrated the 2xPM_Motors.pjt with no migration errors.

I then tried to compile the project, but got multiple errors. I noticed that several include files could not be found. It seems the 2xPM_Motors.pjt does not have the ~support files included with the download, so I searched for the latest versions and added them to the include path. This resolved many of the errors, but the compiler is still looking for the header file named PeripheralHeaderIncludesIndus.h .  Isearched my whole PC, the TI websight, and Google with no success. Can you help me find all the headers I need for this project? Or maybe you guys have already migrated this project and can email it to me.

I know that you are developing new Motor Driver board and I am suppose to travel to Houston for a days worth of training on the 20th of this month. I think I will be meeting with Charley Ice. I suppose you guys have a CCS v4.0 project for this new board already. If so, the best thing for me is to get this software before my trip and make sure I can compile it on my PC. Since I only have one day, anything I can do before my trip will give me more time for other things on the 20th.

I am working on my own board using the F28027 that will ultimately be used in our product. I am hoping my trip to Houston will allow me to get my board up and running ASAP.  I am trying to get as much up to speed as I can before I arrive in Huston and anything you can do to help with that will be appreciated. If you are located in Houston, I would be glad to bring both PCs.

I appreciate your patients. 

I added a txt file of my build output to the console.

One thing I see in the build output is the option --silicon_version=27 when it should be 28. Can you modify this from the Project Properties->C/C++ Build->Compiler Basic Options?

This might resolve the assembler errors. I'd still have to look into the other errors.

I do not know if this is a good idea or not, but I created a Fresh Motor project and started adding the source files and header files to the project as I slowly determined which ones are needed. I got to a point where I needed the header file f2802xpwmdac.h, but once again I can not find this header file anywhere. At least this incremental approach gives fewer errors which make debug a little more manageable. I included the console output for this fresh project. Is there anyway to get a minimum list of files needed to compile this project for the F28027 only? Have you guys converted these projects before or am I the first? OR as I mentioned in my previous message Do you have a CCS v4.0 project for your new motor board? If so, I would rather spend my time getting that to work.