CCS: CCSv9 update fails

Hello Sergey,

My apologies for your bad experience with CCS. 

Have you installed CCS with sudo (or equivalent)? I've seen a similar such message reported in cases where CCS was installed with superuser privileges.

https://e2e.ti.com/support/tools/ccs/f/81/p/635957/2369212#2369212

https://e2e.ti.com/support/tools/ccs/f/81/p/572521/2190144#2190144

ki 

You can't install it from anything but root account -- it is installed under /opt and nobody but root can write there. You _MIGHT_ install it as user but that is plain wrong -- I don't know where it will go then (probably under your home directory) but that would definitely mean nobody else would be able to use it.

All packages in the system should be installed into regular system locations and that requires root privileges.

It is not also all that unusual to have homes mounted as no-exec so no code could be executed from home directories.

Your monster is broken. This doesn't happen e.g. with Microchip MPLabX. Or Altera (now Intel) environment.

Trying to update it as root fails with just another weird message:

=== Cut ===

An internal error occurred during: "Computing size".
Profile epp.package.cpp is not current. Expected timestamp 1581461118533 but was 1559586958502.

=== Cut ===

And the entire weirdo is totally screwed.

Sergey Kubushyn said:

I don't know where it will go then (probably under your home directory) but that would definitely mean nobody else would be able to use it.

yes that is where it goes (by default) and where many users run it from.

Please refer to the below document to configure CCS. It was written for CCSv8 but also apply to v9

https://software-dl.ti.com/ccs/esd/documents/application_notes/appnote-configuring_ccs_for_multiuser.html#procedure

OK, I have never seen anything more broken :(

Guys, do you have _ANYBODY_ there who understands Unix? That procedure is _EXTREMELY_ lame; one should _NEVER EVER_ do something like this in Unix.

One should _NEVER_ make _SYSTEM_ directories writable by anybody but root. By using that procedure you are making a Windoze from Unix and not just Windoze but very bad and broken Windoze.

Can you hire somebody who has at least rudimentary Unix knowledge so he could somehow fix that monster? It is broken beyond repair as of right now and that entire bunch of thousand Java droplets makes it almost impossible to fit into Unix but it might worth a try...

To say it politely I did not expect TI would make something _THAT_ bad :(

Sorry for your bad experience. We will take your feedback to heart and look to improve things in the future.

Thanks

ki

Eh... It is totally, completely broken even with all those entreshats and installing as user to home directory.

Just removed everything related to the old install (ran uninstall command from old installation then removed all crap it left out at several places,) downloaded and installed 9.3.0 as user into home directory, started it up, it found new updates and failed to update yet again:

=== Cut ===

An error occurred while collecting items to be installed
session context was:(profile=epp.package.cpp, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: org.eclipse.update.feature,com.ti.ccstudio.automotive.devicesupport,1.1.6
No repository found containing: binary,com.ti.ccstudio.automotive.devicesupport_root,1.1.6
Artifact not found: software-dl.ti.com/.../com.ti.cgt.msp430.18.linux_root_18.12.5.
software-dl.ti.com/.../com.ti.cgt.msp430.18.linux_root_18.12.5

=== Cut ===

I like TI devices but your guys software is _TOTALLY ABSOLUTELY_ hopeless so I would probably start moving away from whatever TI and tell our 9.5K employees multinational multibillion company to move away from anything TI. It is a shame you guys can't make proper tools for many years. This junk is totally unusable and all my expensive debugging/emulation/whatever hardware I spent quite a lot on are useless without the software supporting them.

Lesson learned, will start switching to something else. It will be difficult to replace your very good DSPs with something else but it is worth an effort.

It is hopeless. I have never seen a single case that monster hadn't failed. It fails 100% of times and I'm finally fed up with it.