I just freshly downloaded and installed CCSV4 Beta 5 version 4.0.0.14000 and it says an update is available - service release 4.0.0.14900. However, the updater comes up with an error stating:
ROV (1.0.0) requires plug-in "org.eclipse.rtsc.xdctools.managedbuild.ui".
I have been unable to locate this plug-in and therefore cannot update to the current release. Where can I get this plug-in?
I have this same problem on both of my computers - one is running Windows XP, the other Windows Vista 64
Very odd that those files are not present. Did you do a custom install of CCS? I am wondering if one of the custom install options causes these plug-ins to not get installed. Attached are a couple of plugins that you may need to drop into \ccsv4\eclipse\plugins
Regards,
John
If my reply answers your question please mark the thread as answered
Placing those files in the \ccsv4\eclipse\plugins folder did not work, nor did extracting the jars there.
However, you appear to be correct in your guess that it is related to the custom installs. I had done the "MSP430-only Core Tools" installation - this does not work. I uninstalled, deleted all leftover files, then installed choosing "Microcontroller Edition" and this worked (without needing to copy the plugin files). To verify, I then uninstalled again, deleted leftovers, and installed with the "MSP430-only Core Tools" installation and again it did not work. I verified this on both Windows Vista 64 and Windows XP.
I then did the "Microcontroller Edition" installation again but this time unselected the various emulators associated with the C2000 since I do not need them at this time and this also worked. Something about the MSP430 core tools installation must be missing the plug-ins needed for the updates.
I captured the two lists of components to be installed - the item I noticed that seemed possible is that the MSP430 install does not include DVT.
Now all I need is a Windows Vista 64 compatible driver for the MSP-FET430UIF - I was hoping this update would have it. Windows finds a driver "MSP-FET430UIF - VCP" but says "Driver is not intended for this platform". Any ETA on this?
Thanks
Thanks Edward. That makes sense. The update checker actually goes and scans all the "features" that are installed and does a dependency check on them when doing an update check. If one of them fails it will prevent you from installing additional updates. DVT is a package that we use on DSP & ARM for profiling and OS visualization... things that are currently not applicable to MSP so it doesn't get installed in the MSP-core config, however it looks like something else that does get installed is expecting elements of it to be present. I will talk with our install team and see if this is known and correct and if not get something filed for it as this could be a big issue.
I will try to get some info on the ETB for 64b MSP UIF drivers.
Edward,
We just checked and the update issue is resolved for the core config in the release candidate. BTW we just posted the release candidate if you are interested.
http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v4
Thanks John.
I downloaded and installed the release candidate. MSP-430 core only, on both Windows XP and Windows Vista 64 and noted the following:
1) During the installation, the window that comes up with the list of components that will be installed does not list DVT but the next window that steps through the installation does show DVT being installed. Not a big deal but thought I would mention it. I cannot verify the updater since there are no service updates available yet but it looks positive that it did install DVT - assuming that was the source of the original problem.
2) The installation installed a license file that did not match the host ID of the computer I was on - when selecting the licensing options from the menu it just came up with an error window. I had to manually delete the license file in order for the licensing options to come up. It would have been nice if it could have still brought up the licensing options window rather than make the end user search that nightmare of a path for the offending file. This happened on both of my machines, so I am assuming that this file was not supposed to be included in the installation in the first place, but I can see where this might happen to someone that has to replace their network card (hence changing the host ID making the license file invalid). Ironically, when you already have a valid license the license options comes up just fine - even though you don't need it.
3) The MSP-FETU430UIF is still not working on Windows Vista 64 - same error as before - I assume this is due to no 64-bit driver available yet - any update on this? I really don't like having to switch to my old slow computer to do my debugging so I'll probably keep asking this until you give in and toss me a 64-bit driver :)
-Edward
Two more issues, one simple, one difficult. These issues are not new to the release candidate - the beta 5 release had these as well.
1) The SVSCTL (SVS Control Register, MSP430x2xx Family User's Guide section 9.3, page 9-7) is missing from the header files and linker command files. This also happens to be missing from the IAR header files.
2) On my Windows Vista 64-bit machine, the Project->Properties->C/C++ Build->Configuration Settings tab will not display (shows a large blank area where the configuration settings should be. This works on my Windows XP machine. I'm guessing you will need a bunch of information regarding my machine to be able to fix this one. It is a Gateway FX6800-09 and I am running dual monitors (video card is NVIDIA GeForce GTX 285), display 1 = LG W2361VG, 1920x108 pixels, 32-bit color, display 2 = LG W1952TQ, 1440x900 32-bit color.
The only way I have gotten the configuration settings to show up on the Vista 64 machine is to run in 640 x 480 compatibility mode and even that is hit or miss on it working. As far as I can tell, all of the other property screens appear to be working correctly.
If you need any other information on Item 2 let me know.
Yes we don't list DVT as a user configurable install option it gets installed based on what you select. However now I think it gets installed all the time as many things are making use of it and this fixes the bug you saw.
The way it is supposed to work for the core tools is that you won't ever see the license dialog as it will create a license for you automatically. Something may be going wrong with that, we will test it out some more on our end.
I will let you know as soon as I get an update on this.
4) The SVSCTL (SVS Control Register, MSP430x2xx Family User's Guide section 9.3, page 9-7) is missing from the header files and linker command files. This also happens to be missing from the IAR header files.
I will file an issue for this.
5) On my Windows Vista 64-bit machine, the Project->Properties->C/C++ Build->Configuration Settings tab will not display (shows a large blank area where the configuration settings should be. This works on my Windows XP machine. I'm guessing you will need a bunch of information regarding my machine to be able to fix this one. It is a Gateway FX6800-09 and I am running dual monitors (video card is NVIDIA GeForce GTX 285), display 1 = LG W2361VG, 1920x108 pixels, 32-bit color, display 2 = LG W1952TQ, 1440x900 32-bit color.
Does it happen with any other dialogs? Does it happen on both monitors? My main machine is Vista32 with dual display (1680x1050 + 1280x800), NVIDIA GeForce 8400M.
As far as I could tell it was only that one screen that did not work correctly. One theory I had is that it might have to do with the list panel on that screen with the horizontal and vertical sliders as that seems unique to that screen.
The file extensions screen has a vertical slider but that one seems to work; although there was a small difference on that screen between the XP machine and the Vista machine - on the XP machine the vertical slider looked active and on the vista machine it was greyed out like it was disabled. I am not at those machines right now, but if I recall correctly the slider did not actually work on either the XP or the Vista machine. I did not play around with that screen since it is not something I envisioned needing to ever change.
I don't think that it is related to the multiple tabs on the configuration screen since there are other multi-tabbed screens that are working - unless the build configuration tab panel is implemented differently that the others?
I have not fully tested all of the screen options with the release build, but with the beta 5 build I had tried both monitors in dual mode, each monitor in single mode, various screen resolutions and different compatibility mode settings. The only thing I found that had intermittent success was to use the 640 x 480 compatibility mode. In 640 x 480 mode I could open and close the properties and sometimes the screen came up and sometimes it did not.
Later today I can try disabling some of the video acceleration and other options to see if that makes any difference - do you have any suggestions on what to try?
I tried a bunch of video settings and still the only one that has any success is the 640 x 480 compatibility mode.
One interesting note - in the 640 x 480 mode, if I open the properties screen, select the build settings, close the properties, re-open the properties (so it starts on the build settings), it will not work. I can then select a different screen, such as Info, close properties, open properties, select build and it works. This was 100% repeatable.
Also if I close on the builders screen, open properties and click on build, it will not work. However, if I click on one of the other screens and then on Build it works.
Also of note is that even when the build screen shows up in 640x480 mode it does not show up correctly. Instead of using the whole area it only uses the top left quarter of the area (1/2 the width and 1/2 the height).
Let me know if there is anything else I can try or information I can provide to help figure this one out.
For the SVSCTL issue. Which header files is it missing from. I filed a bug for this and the owner would like to track it down. I looked in msp430x23x.h and I see it defined there.
I am trying to pull in some other people on the display issue.
This may be my error. On looking back through the family user guide I noticed this register is only on "selected" devices in the family. I had thought it was on all of them. We are using the MSP430F2272 and it looks like this part does not have the SVSCTL register so the header is correct as is.
Good news - Adrian replied to me on another thread with a link to the new released beta 64-bit driver and that seems to be working as well as the 32-bit so far.
More news on the display issue:
On the display issue, I have found more screens not displaying correctly. Now that I can debug on the 64-bit machine, I found that the CCS Debug settings are not coming up quite right all the time either. The grouped settings, such as PRogram Verification Options, Realtime Options, Auto Run Options, Launch Options, Connection Options, OS Aware Debug Options, Automatically load module symbols, and the Download Options (under MSP430 Properties) are also not always coming up. This is a little different though in that they were all empty at first but as I switched back and forth between screens they started working and once working did not dissappear again. Not all of them started working at the same time, however, and the Program Verification Options and Automatically load module symbols did not fix themselves at all (those two are still empty).
The Main tab of the CCS Debug Settings is also intermittent on working / coming up partial / coming up blank.
New bug - trouble setting breakpoints - this is happening on both the Windows XP machine as well as the 64-bit machine. The Windows XP machine works fine with the same source code and settings running version 3 but has lots of trouble with version 4. I do not recall having this problem before the release candidate, or at least not this reliably. This happens every time I try to debug with breakpoints.
With no breakpoints set, when I try to add a hardware breakpoint I get an error popup from the Breakpoint Manager that says "Insufficient resources. You can free up one resource by disabling software breakpoint support".
I also get error messages like this:
MSP430: Breakpoint Manager: Could not read Enhanced Emulation Module register MSP430: Trouble Halting Target CPU: Could not terminate EEM polling thread. -Edward
MSP430: Breakpoint Manager: Could not read Enhanced Emulation Module register
MSP430: Trouble Halting Target CPU: Could not terminate EEM polling thread.
I verified that the breakpoint problem is a new bug with the release candidate. I went back and installed the full version of beta 5 (CCS_4.0.0.14000) and it worked fine. I could set a hardware breakpoint, remove or disable the breakpoint, add a new hardware breakpoint, go back and forth between breakpoints, etc. As long as I only had one hardware breakpoint enabled at a time it worked just fine. I only got the error when I tried to have 2 hardware breakpoints enabled. This is correct and expected behavior for the part I am using (MSP430F2272).
To compare apples and apples, I then uninstalled beta 5 and installed the full version of the release candidate (CCS_4.0.0.15000), just to make sure it was not a core-only problem again.
With the release candidate, I can set one hardware breakpoint, once and only once. As long as I keep that breakpoint enabled it works. As soon as I remove or disable that breakpoint I cannot add a new one nor re-enable the one I disabled. It seems as if the debugger is not properly removing the breakpoint (either the MSP still thinks it has a breakpoint or the debugger's internal count of breakpoints is not being updated).
For now, I will have to go back to the 4.0.0.14000 version since I cannot effectively do any debugging with the release candidate until the breakpoint bug is fixed. Let me know when a new release candidate is available and I'll be happy to continue testing it.
By the way, while I had the full 4.0.0.14000 and the full 4.0.0.15000 versions loaded I verified that all of the display problems I have with the core-only release candidate are the same in both full versions so the display issue is not new in the release candidate nor is it a full versus partial installation issue.
Thanks for the detailed analysis, we will look at this right away.
I was unable to reproduce the breakpoint problem with the hardware I have immediately available (the closest device I have is a MSP430F2274). Would you be able to confirm that this test case does not work for you:
Thanks for your help with this.
Andy