After wrestling with FET issues I rebooted my computer and fired up FET-Pro430. It updated the MSP-430FETUIF. Then I was able to toggle power on my test board and upload the firmware from it. So fa, so good.
I fired up CCS 4 and clicked the debug icon. The project compiled without errors, but the loader complained that there was no FET connected. This is the same FET that just uploaded code from the board I'm trying to program.
I fired up CCS 5 and imported the project. CCS 5 complains that the project is not hardware-specific.
Anyone have any idea what's going on?
Can you provide more information? How did you create your project? Is is a CCS project with a target device selected in the project properties?
Have a look here as well
please keep us informed.
The project exists in two pieces. My part of the project is on my machine, the major part is on the project leader's machine. Both are under version control, using Subversion. Both have been compiled and run under the debugger, mine using CCS 5 and his using CCS 4.
The task at hand is to merge my code and his and test the combination. I imported his project without copying the files. It compiled just fine, but subsequently began to deny the existence of the FET.
I have tried so many things since then without success I have decided to start from scratch and see if that works. I have uninstalled CCS4 and CCS 5, and for good measure I have uninstalled FETPro-430, which, by the way, has no trouble seeing, controlling or uploading flash memory through, the "non-existent" FET. I have also cleared out the Texas Instruments folder in Program Files and removed anything TI-ish from Documents and Settings and its subfolders. If I can find the name of the driver dll I'll delete that, too. The next step is to reboot my computer and install CCS 4 from a freshly downloaded installation zip file.
I have convinced myself that the origin of the problem is CCS, since FETPro works as well as ever. The question is whether the problem source is CCS 5, CCS 4, or the combination.
Thanx for your help,
The process I outlined in my previous reply worked. I had to install both CCS 4 and CCS 5 (which I had hoped to avoid) so I had access to the MSP-FET430UIF downgrader. I was careful not to fire up CCS 5 after the install, so I wouldn't create the problem all over again. After running the downgrader I started CCS 4, and was more than a little surprised to have it come up telling me that it had to update the FET firmware. With great trepidation I let it perform the upgrade, but nothing bad happened.
I couldn't use the workspace where my project lived under CCS 5 (CCS 4 got all uppity), so I had to build a new workspace and copy my code into it. Then my project compiled and ran as expected.
The moral of the story is that there's no going back. Either upgrade to CCS 5 or don't, but if you do, live with it. Until the rest of the team upgrade, I'll stay with CCS 4.
Hi Jim, glad to hear that you got a working setup. Yes, v4 only works with the v2 dll and v5 only with the v3 dll.
All the best with development and thanks for the update.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.