Tool/software:
EDIT: Managed to solve by creating the /sbin/start_udev file as recommended here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1462212/ccstudio-ccs-20-1-installation-problem-blackhawk-breaks-installation/5617129#5617129
Hopefully this bug will be addressed in newer versions of the installer.
Hi there!
It's been a while since I last used CCS, so I wanted to update from v12 to the shiny new v20. I'm on Arch Linux and have never had issues with installing or running CCS before. However, during the installation of v20.2.0.00012 I get an error that the installation of the BLACKHAWK-EMUPACK component failed. Upon further inspection, it seems to be failing because the BH-EMUPACK installer tries to run "service" but I (and almost all modern Linuxes) use systemd instead of sysvinit.
I am able to successfully manually run the BH-EMUPACK installer in attended mode, and while it does pop up the error, it's not fatal as it's just trying to restart udev. I guess because of this, the installer is returning a failed error code to the main installer executable, which assumes the component failed to install at all. I'm stuck at this point as there seems to be no way to tell the installer to either not install that component, or continue even with errors.
On the first fail, I did submit the error logs, but I would really like to get up and running again fairly quickly. If I manually install all the other components (a slightly tedious task) will that result in a successful installation? Are there any hidden options to the ccs_installer that can allow me to continue even on errors? It seems silly to me that the installer is reporting a fail code when trying to run a command that almost no modern Linux machines have -- yet I don't see any other complaints about this installer, which makes it all the more confusing.
Images of the main installer failing:
And then the Warning when I run the BLACKHAWK_EMUPACK installer separately:
Hoping anyone out there has solved this problem!
