CCSv4 Beta 5 Available

Stickied for a month to get the word out.

Do we need to uninstall Beta 4 before installing Beta 5?

I didn't uninstall Beta 4 and I got the following message when installing Beta 5:

Error in action ExecuteScript

Could not find Setup Type '<%PreviousInstallInstallType%>'
    while executing
"::InstallJammer::actions::$component $this"
Error in action ExecuteScript

Could not find Setup Type '<%PreviousInstallInstallType%>'
    while executing
"::InstallJammer::actions::$component $this"
    while executing
"$obj execute"
    (procedure "::InstallJammer::ExecuteActions" line 65)
    invoked from within
"::InstallJammer::ExecuteActions $id -when $when"
    (procedure "::InstallJammer::RaiseEventHandler" line 79)
    invoked from within
"::InstallJammer::RaiseEventHandler  .wizard"
    (command bound to event)

Please advise.

Thank you!

Mateja

Appropriately, the Beta 5 installer is trying to install in the same directory as where Beta 4 lives.  It seems logical to uninstall Beta 4 at this point.

Mateja

Hi Mateja,

It is always recommended to uninstall the previous version before installing a new version in the same location. Sometimes even the uninstaller does not remove everything so it is recommended to delete any leftover folder/files after the uninstall.

Thanks

ki

Hi Ki:

I have exactly the same problem although having read these posts prior to downloading Beta 5 (direct download) I uninstalled the previous Beta 4 before downloading and wound up in the same situation with the same error complaint about not finding the same files as above.  Ki, can you give us any listing of various places our PCs have squirrled these files away in?  Or a description of where other folks have found these recalcitrant files and removed them with happy results?  I've searched and searched and can't find any more files appearing to belong to beta 4 but I still get the same complaint about Beta 4 lurking inside somewhere (but with no hint as to where) and the 'Wizard' stops installation there.

Much appreciation for your help.

Larry

Larry,

    I uninstalled Beta 4 using the uninstall tool and then immediately installed Beta 5 without any manual deletions.  As of yet, I have not had any issues, and what's more, my plugins are still working as they were in Beta 4.  I believe most files for CCS are stored in \Program Files\Texas Instruments\ccsv4, did you try looking there?

Mateja

Hi Mateja:

Apparently some do work out easily and some don't.  I've looked down that path and many others.  The only CCS now listed (in Program Files/Texas Instruments/ccsv4) is:

CCSv4_4.0.0.14000_package.  Uninstalling Beta 4 removed the obvious files and pulled indications of it out of the directory.  Now the computer cannot find it under various search strategies including internal search and manual examination of various folders.  Yet I just tried the Beta 5 download again and it's still the same story, the Wizard goes until the error message you described appears, then I can either quit and try to clean the remainders out, or put Beta 5 in a new location without any guarantee that the system will access it when starting up Beta 5.  I would prefer to use standard routes to work this out because it doesn't introduce new possibilities for error.  Unless someone has  better answer.

Having seen the previous posts about uninstalling Beta 4 before installing Beta 5 I too did that immediately and I'm getting stopped because the Wizard still thinks Beta 4 is in there somewhere that it doesn't like.  I've also noted the caution from someone else above that simple uninstall may not get the program totally out and that some form of manual intervention may be necessary but how to do it wasn't clearly described, just that it could be necessary.

Larry

Larry,

CCSv4 is pretty self contained. Nearly all the files are within the installation directory (ex: C:\Program Files\Texas Instruments). Deleting the folders should be sufficient enough (in fact, simply deleting the whole folder insteas of running the uninstaller should be fine). You can also try emptying out your system TEMP folders. It is possible that left over files in TEMP directories could be causing a problem.

If you are still having problems installing beta 5 in the original directory, try installing in a new one. One other note is that you can also relocate your install of CCSv4 if you wish. This is a big advantge of CCSv3 where you could not do that because of CCS windows registry entries

ki

Have installed Version: 4.0.0.14000 on XP64, and actually got the Blackhawk 560 driver to work after a whole lot of hassle and support from Blackhawk, BUT something seems badly wrong.

My aim is to be able to do as much as CCS will allow on an OMAP35xx target running Linux on the ARM Cortex A-8 and various codecs on the C64x+. In the Code Generation Tools listing the only relevant entry is .../tms470. As an ARM dummy I would suppose that is a far cry from the Cortex architecture, even if based on the ARM7 architecture.

Initially Window/Preferences/Code Generation Tools the Discovered Tools list only shows me msp430. I go to .../ccs4/tools/compiler and Add - then the whole list shows up as seen in

http://tiexpressdsp.com/index.php?title=Specifying_New_TI_Code_Generation_Tools_with_CCS

I press Apply and OK. Next time I come back the Discovered Tools list again only contains msp430.

[btw, the menu Item is called Window, not Windows as stated in a couple of places in helper docs]

As said, have the Blackhawk 560 and a live target connected, but I cannot find any way to make CCS 4 aware of this. Is this something wrong with my installation? I have used CCS for years and previously there was a setup program where CCS could be configured to work with specific hardware, but that is all different now I see. Would be grateful for any tips.

So really I'm asking two questons here, (a) is there something wrong with my CCS 4 installation?; (b) how, if at all, can I proceed to use CCS 4 as the only tool I need to develop OMAP35xx applications with Linux running on the ARM? If not the only tool, what's a good hybrid toolset?

Having gotten past the first hurdles described above I've got a working CCSv4 Beta 5... Sort of...  The problem seems not that distant from the one just above.  I can't seem to properly configure my TMDXDOCK28027 Dev. Kit or know if I've loaded the proper programs into CCS simply to blink the LED.  The documentation does not seem very clear.  What files do I load exactly and into where?

I'm using the description for starting up LED blink that comes with the programs for flashing LEDs and it is not very accurate... or something.

After telling me to connect my board and turn it on and start CCS it says:

3.  Connect to the board by clicking:

      Dbug (arrow) Connect.

Where is this?  Which 'Debug'? There is a consistent problem industry wide in that people tend to shortcut path descriptions and don't include the whole thing, or don't mention that it comes from the tool bar or fail to indicate an easy route in to some function or feature.  They jump start the process by naming about the last two places in the path and then we're expected to pull the rest out of the same ether we fill in all the other missing pieces with.

I guess.

The point is these are tutorials, examples supposedly designed to initiate the unfamiliar into some new experience or knowledge or usage and examples should start everything carefully from the ground floor, especially examples designed for the terminally deficient like Flashing LEDs is.  Yet this example has proven a time waster without getting even a single response out of any part of my CCSv4 Beta 5.  When I build the 'program' such as it is, I can run it and then another requester from somewhere else in the program says I've got no code to load even though the program seems to think it's loaded and running.

Whew! 

It says that if the board does not connect I should look for 'Setup Code Composer vX.X' which is supposed to be installed with Code Composer Studio.  I don't think I've found it yet and have been trying to configure for my board using other routes but.....  The user in the comment above seems to be having the same kind of problems with trying to get his CCSv4 to settle down with a larger request list, I'll be happy with blinky lights.

Line 5 of the LED blinky instructions is a whizzer:

"This project can be configured to create code for multiple target control Cards and can be ran (sp) in either flash or RAM.  In the project window, right-click on FlashingLEDs.pjt and select 'Configurations..."  

I don't get this when I do that.  I also find that telling me that I can set up multiple control cards is utterly silly  to have here.  I'll be happy to get ONE card to run let alone get distracted by this comment at this point.  This is a point for later and only slows down what is already a pretty poorly done sentence.

Can anyone give me an actual description of how to work with the LED example that applies to CCSv4 Beta 5 and the TMDXDOCK28027 and actually works? 

Larry

One additional note to add is that under "On-Chip Flash' I find that the chip listed is the TMS320C28XX, yet my chip would look like 280XX so that's part of why I think I'm not setting up CCSv4 for the proper chip to drive.

Larry

Hi Paul,

'tms470' refers to all ARM devices including Cortex (see readme.1st doc in .\ccsv4\tools\compiler\tms470).

By default, CCS 4 should already be aware of all the code generation tools in .\ccsv4\tools\compiler. If you installed the full tools (and the the Microcontroller version) with a 'typical' installation, you should have several CGT versions availe (one for each ISA).

In CCS 4, the setup program completely changed. It is now tightly integrated into the main CCS IDE (in CCS 3.3, there was a completely separate executable for setup). There is some information on how target configuration is done in CCS 4 in the online help (Go to the 'Help' menu in CCS 4 and select 'Help Contents'. This will bring up the Help. Next expand 'Code Composer Help' then the 'Views and Editors' node underneath and select 'Target Configuration View').

So in short

a) If you did install the full tools with all the ISAs and only the msp430 compiler is showing up, then you may indeed have a bad installation of CCSv4 since you mentioned you saw a tms470 entry on .\ccsv4\tools\compiler. Why CCS 4 is not picking up the other CGT besides msp430 is very strange

b) CCS 4 should be all you need to develop OMAP 35xx application with Linux running on the ARM. In fact, this wiki topic may be of interest:

http://tiexpressdsp.com/index.php?title=Linux_Aware_Debug

It highlights the new Linux aware debugging capabilities of CCS 4 for Linux 2.6 running on the ARM Cortex A8 of the OMAP 3530.

ki

Hi Larry,

I am not too familiar with the TMDXDOCK28027Dev. Kit but the documention you are following (which presumably came with the Dev Kit) sounds like it is for CCS v3. In CCSv4, many thing have changed. For example, it is no longer 'Dbug (arrow) Connect.' (as it was in CCSv3) to connect to the target but 'Target (arrow) Connect Target' in CCSv4. And you need to be in the 'Debug Perspective' to have that menu item available. There are no '*.pjt' files anymore. Also 'Setup Code Composer vX.X' is referring to the legacy setup program for CCS v3.x (or earlier). As mentioned in the post above, target setup has changed in CCSv4. I'd recommend that you first get familiar with the new CCSv4 environment first and also see this Migration document on the major changes in CCSv4 from CCSv3. Otherwise trying to follow the TMDXDOCK28027Dev. Kit documention ( that was meant for CCSv3) step-by-step on CCSv4 will just cause confusion because of all the differences between the two environments.

Thanks

ki

Hi Ki:

I was beginning to suspect that might be the answer.  I agree that I need the correct complete set of instructions and demos to match Beta 5.

Larry

Dear Ki,

I just want to say thanks for your encouraging reply. I will follow up the leads you suggest, and further investigate this strange behaviour with the Code Generation Tools list. So expect more postings from me shortly.

I have to admit that I can't work out what ISA stands for [:$]

Also embarrassingly enough, being a dummy for Oriental names I can't tell whether you would be Mr. or Ms [:$]

And btw, nothing teaches better than example, can you point me at some CCS 4 example projects relevant to an OMAP35 platform?

Best,

Paul

Ki:

The answer was to put Beta 5 in a new directory/folder.  Thanks for your excellent suggestions and especially comments about the advances both in CCS4 and in Beta 5.

Larry

Hi Paul,

Sorry for the acronym.. I used 'ISA' to mean 'Instruction Set Architecture' like ARM, C6000, C5500, etc...

What I'd suggest is to try and create some simple "hello world" type application for ARM and see if you can successfully build it. If you are able to, then CCS is able to find the ARM code gen tools even though the list is not getting properly populated.

As for OMAP 35x examples... I can't help you there as that is out of my domain but I'll see if I can find someone to post here to offer some suggestions. As you know, CCSv4 is very new and we are working on creating more examples for it but still have a ways to go...

And no worries... I certainly understand that it can be difficult to determine gender from a traditional Korean name alone! (It's MR. Lee in this case)

ki

Hi Ki,

thanks for your reply. I already tried that with a little hello world app. I have quite a lot of bug/failure reports and queries to post about CCS4 and I am currently trying to put them into some kind of order. It would be much simpler and of course more "graphic" if I could paste screen dumps here but that doesn't work. Have you any suggestions?

/Paul

paulspignon said:

It would be much simpler and of course more "graphic" if I could paste screen dumps here but that doesn't work. Have you any suggestions?

You should be able to insert/attach images to posts using the insert media icon button in the tool bar at the top of the post editor, it should look something like  (which was inserted with the very same button).

If you have large dumps of error messages that don't format properly in a post for some reason  you can attach them as a file by using the options tab of the post editor and clicking on the add/update attachments button.

Are you having trouble attaching images, files, or both?

Hi Bernie, Ki.

I am still trying to put together a passably systematic problem report, and decided to make it an OpenOffice document. Thanks Bernie for pointing out the option of attaching a file.

Another point, I'm trying CCS 4 across 3 [4] different computers, running XP, XP 64 and Vista 64, and also comparing with CCS 3.3 on at least one machine, all using the same Blackhawk 560 and a Mistral OMAP3530 EVM as the target. But it is only on one machine (XP 64) that I have a licensed version of CCS 4. What consequences might that have for the validity of comparisons?

Best,

/Paul

Well, here is something, a pretty massive (only because it contains a lot of screen dumps) file, zipped, it is an .odt file so OpenOffice, I'm using 3.0.1. Anything else will mess up the formatting, at least that's my experience. Sorry ti is not better organized, my head is spinning trying to evaluate two versions of CCS on 3-4 different machines. I will proceed with further tests meanwhile.

In a nutshell,  CCS 4

- on my xp64 machine is a total dead loss (but this is the computer of choice for me)

- on my old 32-bit XP machine, sets up apparently OK but fails miserably to communicate with the target

- CCS 3.3 on both the 32-bit and the 64-bit XP machines does communicate with the same HW as it should

So, what can I say, please look at my report and help, I'm at an impasse.

/Paul

I have what I must call a trivial gripe compared with all the other grief I'm having with CCS4, but why this

deployment.browser.path=C:\Program Files (x86)\Internet Explorer\iexplore.exe?

Why does Ti choose to make me use IE, which I never do otherwise? Is it not possible to find out what is the default browser in the system and use that, and/or provide a setup option?

/Paul

Paul,

Eclipse uses IE as its internal browser.  You can configure which browser it users as its external browser (when a page is opened in a new window).  Go to windows->preferences.  Type browser in the search box.

Regards,

John

Guess the huge file of grief I posted is putting everyone off - not seen any reaction at least.  Well as noted I proceeded with investigations, discovered the following which may be useful to others:

- if the CCS 4 copy is not licensed it will NOT work with a 560 emulator. I know it says that somewhere, but it's pretty easy to overlook, as I did. I posted a query about that somewhere AFAIR but got no answer. Now got licensed copies on two 32-bit machines and verified that CCS 4 is able to communicate with the OMAP3530 via the JTAG connector on a Mistral EVM.

- if you do get something wrong, like that with the license, or accidentally select the wrong type of emulator, then try to initiate debug, CCS 4 will hang, trying forever to do something, you can't stop it except by killing the process. What happened to error handling people?

- I am still facing the issue that CCS 4 is quite unusable on my XP64 machine, for the reasons expounded in the file attached to an earlier post.

/Paul

Paul,

Open office is not something that is general available in a corporate environment so we have been having issues getting to the contents of the document.  We did manage to get it convert to a word doc today and can see the contents (all 90 pages ;) and are going through it.

On your XP and Vista 64bit machines you are going to want to uncheck the option to install the XDS560 PCI emulator.  From your doc I am assuming you don't have one of these anyway.  The windows driver installer for this emulator has a problem where it is always trying to installer the 32 bit drivers even on 64 bit machines.  The blackhawk and spectrum installers correctly install th 64bit verisons of their drivers.

Yes CCSv4 needs a license to work.

Regards,

John

Hi John,

Thanks for your reply.

Sorry to have caused aggro with file conversion. In our company, small agreed, I have made OO the standard. We can open any MS documents we have to, and save in MS formats or export to .pdf if needed. It's only when one starts to do some rather tricky stuff like including bitmaps and drawing elements in text files that it can get messy if one tries to save/export to some other format. Most of our business and academic partners (including Mistral)  have no issues with OO.

On the machines and with internet connections such as you surely have it takes perhaps 15 minutes to download and install OO, and it's free. And the general impression  is that though you work for a huge corporation the policy is an overlapping with the open-source community, so I rather assumed that would make OO a natural choice, at least to have even if not the corporate standard.

Be that as it may, I hope the file didn't turn out too garbled in Word, or perhaps you did opt for  the simpler solution (IMHO) of installing OO.

As seen from my early posting today, most of the issues I had to date on 32-bit XP have been resolved already. The main gripe there is that CCS4 hangs trying to start communication with the target when there's something wrong with the setup.

Regarding XDS560 drivers not installing on 64-bit machines, we did the installs without that option, as I already noted in the report.

As for the license issue, somewhere its says that without the license only 510-type emulators will work, but unfortunately I was trying to get it working with the Blackhawk 560.

No worries on OO.  I found a plug-in for Word that let me open it and convert for the rest of the team.  I used to use StarOffice many years ago.  We are definitely going open source or utilizing open source in many of our products these days including CCS, things are a little different on the IT side though.

To use CCSv4 you need a license.  It is true that we have different types of licenses.  I think the license type you are thinking of is that we will have a free license option available that allows you to use the emulation built into EVM/DSK boards as well as XDS100 class emulators.  XDS510/560 emulators don't work with that license.  The license that you get when you click on the register beta button can be used with all classes of emulators.

John

I just installed CCS4 last week and have a general question about it maybe someone can answer.  It doesn't look like CCS4 includes the Chip Support Library (CSL) for C55x.  When I try to manually download the CSL from this TI link it shows that the link is broken.

http://focus.ti.com/docs/toolsw/folders/print/sprc133.html

I tried the update manager and read through a lot of documentation but can't seem to find a way to get CSL installed for CCS4.  Why would this not just get installed automatically when I install CCS4?

Paul,

TI has moved to a web distribution for CSL.  I will contact the appropriate people to get that link fixed.  Ideally it would be nice if it was tied into update manager, i.e. if you installed C55x it would configure an update site for C55x CSL, however there is no plan for that at this time.

If you are importing a CCSv3.3 project we try to configure the project to look at the location where CSL was located in the old install.

Regards,

John

Thanks for the quick update.  I had used the CCS3 project migration wizard but it didn't find the previous location of the CSL that I had installed under CCS3.  I ended up just copying the whole CSL directory under the CCS4 install directory and that works.

Paul,

The download link for CSL seems to be working now.  Must have been a temporary issue.

Are you running beta 5 or an earlier build?  The import wizard should have handled the 55x CSL in beta 5.

Regards,

John

Yes, I just tried again and the download link for CSL is working.

When I started CCS4 this morning it gave me a new update and now the import wizard correclty pathed the CSL directory for me.  I ran into some other trouble migrating a project over but eventually got everything all worked out.  Thanks for your help.

Hi ,

Is there any document available on how to use the Profiler tool with CCS4.

Thanks..

Faraday,

There is a mediawiki topic that may help.

http://tiexpressdsp.com/index.php/Profiler

Regards,

John

Thanks for the reply John.

One more quick question.

When i try to launch the TI debugger, it works sometimes( i mean stops in main function) and sometimes nothing happens, it does not load the symbols at all.

Is it unpredicted behaviour a bug or do i need to take care of something?

Thanks!.

Are you using Launch TI debugger or Debug Active Project?  If you have a project then Debug Active Project is the default action of the bug button.

Debug Active Project will

-build yourproject if needed

-launch the debugger

-connect to the device

-load the program

-run to the label specified (default is main)

In beta5 if connecting or loading fails then it terminates the whole debug session.  This will change shortly in that we will prompt you if either of these happen and ask you if you want to continue.  This is because the problem may be that you just need to reset your target or fix an issue with your GEL script and it is easier to do that from within a debug session.

Thus I am a bit concerned that you mentioned that symbols were not loaded.  If you used debug active project that should have resulted in the session launch failing.  I am hoping that what is happening is that symbols were actually loaded (you could test this by punching in a symbol into the start address of the memory view) and that the problem is that the device is just in a bad state and could not run to main.  You could try hitting disconnect, power cycle the board and then connect again and hit the reload button.

Launch TI debugger will

Launch a debug session

You then manually connect, load, run...

Regards,

John

I was trying to use TI debugger. Now i am using debug active project and it seems to be working fine.......

Thanks a lot John.!

No problem.  Glad it is working!

John

Help:

I am new to TMS320F28335, and newer to CCSV4.

Can someone help me find some simple example projects that will demo for example GPIO, PWM, ADC?

I have examples projects for CCSV3.3, but they don't import well. I get:

C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: *** No rule to make target `DSP2833x_ADC_cal.obj', needed by `Example_2833xGpioToggle.out'.

Thanks very much.

Blaine

Hi Blane,

Could you check to see if the build options circled in the attached screenshot is empty? If it is not and you see a full path, could you try clearing it and trebuild again?

Thanks

ki

Ki:

Thank you, that resolved the problem.

I now get only a warning:

creating ".stack" section with default size of 0x400; use the -stack option to change the default size  Example_2833xGpioToggle line 0 1244142974795 413

Do you know how to resolve this warning?

Thank you, Blaine

Blane - try setting the stack and heap size in the build properties (see attached screenshot) to resolve the warnings.

Thanks

ki

Ki:

Thank you, that works.

One last question, how can I get C and Assembly code in one view?

I tried View->Disassembly, but I never get a listing.

Thank you

Blaine

Blane,

Right-click in the Disassembly view and select  "Show Source"

ki

Ki:

"Show Source" is disabled (grayed-out). Does that require a "debug" configuration?

Also, what is the best download for a "Programmers Reference Manual" for the TMS320F28335?

Finally, what is required to access the SIN / COS ROM tables?

Thank you

Blaine

Yes you need to be in a debug session

For your other questions, try posting in the C2000 forums

Thanks

ki

Blaine,

The Optimizing C/C++ Compiler User's Guide is the best reference about the Compiler and its options, but it is not intended to be a tutorial or a C/C++ standard library API guide - these can be found all over the internet.

Information about the ROM contents on TI devices are usually found in documents called ROM reference guides or Bootloader reference guides. Just answering your question on Sine ROM table, check section 1.2 of the BOOT ROM reference guide (SPRU963) for the F28335 device.

Hope this helps,

Rafael

Can someone help me with a linker control file?

I need all possible RAM for arrays of unsigned ints.

Without changing the "28335_RAM_lnk.cmd" file, I can only allocate about 3600 unsigned ints.

I'd like at least 16000 unsigned ints.

Thanks in advance

Blaine

The toolchain will try to find a memory segment declared which can fit the section containing your unsigned ints.  If it does not find a memory segment large enough,  it will not complete the link.
An array of unsigned ints, like you have stated, will need to be in contiguous memory.

A way I see  you getting this to work is to modify the linker command file to combine two contiguous memory segments.  You must be very careful though.  They must be contiguous memory.