• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 690 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS v3.3 Console Installation

Noel Egemann
Prodigy 20 points

Hello Folks,

I'm currently trying to install CCS v3.3 from my console. I'm using Windows Server 2022 and powershell for that. The installation works fine till the point, where the expected Error messages should appear. Because I'm running the Server 2022 as a Docker Container I don't have a GUI. So i can't ignore these Errors. Therefore the installer seems to be stuck at that point without an option to continue.

When i try to access CCS via a script at that point it won't work and thorw an Error that CCException class is not registered. 

My command to run the installer looks like this: Start-Process msiexec.exe -ArgumentList '/i', "C:\ccs_3.3\setup\setup.msi", '/l', "C:\TI.log", '/quiet', '/qn', '/norestart'

Sadly I'm not aware of any Argument to force msiexec to automaticly ignore those Errors. Is there any workaround to that or an Option to skip these steps on the Installation or just something to continue past this point?

I know, this Version isn't ofically supported anymore but we are forced to work with it cause we are using the Simulator for the TMS320C549. Really need this to work. 


Many thanks in advance

Noel

  • 0
    TI__Guru**** 471851 points

    Hello Noel,

    As you mentioned, CCSv3.3 is very old and unsupported. The last version of Windows that was officially supported by CCSv3.3 is Windows XP. We cannot guarantee it working on a more currently Windows environment. Add the fact that you are running in a docker container (another environment that was never supported by CCSv3.3.) without a GUI, I'm not sure if this would work at all.

    ki

  • 0 in reply to Ki
    Prodigy 20 points

    Yea I sadly know that. Maybe you have an Idea or a Tip in which way the CCException class is registered? I found the corresponding cpp file in SDKv3.3\CC_Automation\Source. Maybe I will be able to register it manually if i know how it is registered in the Installer. Currently trying to get Information out of the regeditor

  • 0 in reply to Noel Egemann
    TI__Guru**** 471851 points

    Unfortunately the people most familiar with the CCSv3 installer is no longer with TI. There is not much support we can provide here. Sorry.

  • 0 in reply to Ki
    Prodigy 20 points

    Sad to hear. Seems like I narrowed down the Problem with the Installer. I printed a complete Log out of Windows during the Installation. The point where the Docker Installation get's stuck is the XDS560 Install. Thats also described in the Installation for Win10. So the devCon XDS presents the Problem, not drpkiont or ISA_BUS Driver. I don't think that you have a setup.msi that skips this Part of the Installation?

    My other hope if not is, trying to manually complete the steps after that point. I may be possible looking at my Log which I got as well on a complete Install on my Win 10, so with GUI and being able to acknowledge the XDS560 Error

  • 0 in reply to Noel Egemann
    TI__Guru**** 471851 points
    Noel Egemann said:
    I don't think that you have a setup.msi that skips this Part of the Installation?

    Unfortunately, no. We do have one that will skip the DSP/BIOS installation on systems where DSP/BIOS would fail to install for unknown reasons. This special msi was created by the person who supported the v3 installer. As mentioned that person is no longer with TI.

  • 0 in reply to Ki
    Prodigy 20 points

    Thanks again. I guess i narrowed down my Problem a lot and maybe got to a point where you have more information on so don't bother if i ask again. I was able to figure out regisration Processes the Installer does after those Error massages and was able to recreate these steps manually. At this point I don't get the Error that the CCException Class is not registered anymore. So a big win already. Now I get the Problem that the CCException Server can't be started. I was able to recreate this on my local machine. The way I got this fixed locally was to run the Setup Code Composer Studio v3.3 and select my Target config. In my case the C54x Simulator. Aftrer saving the Config the Error disappeared and i could successfully run my script without the Installation completing completely and being stuck at the Error. Now i need to convert this to my Docker Container. Of course I cant run the Setup there and select my Target Configuration manually, cause i got no GUI. Do you know or have Information what happens if you Save the Configuration? My guess is that it changes some files, maybe registry values? Thanks for your time again, maybe I get lucky