• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 235 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.

SENSOR-CONTROLLER-STUDIO: Docker windows container installation through cmd or shell

Iván Moreno
Prodigy 20 points
Part Number: SENSOR-CONTROLLER-STUDIO

Tool/software:

Hi! I am building a docker container with code composer studio and sensor controller studio for CI/CD purposes. The objective is to build the project and create a .hex that I can upload to a Gitlab release. The first step of the prebuild process runs a sensor controller command (sensor_controller_studio_cli.exe -g {file} -s -q).

I first tried to do it with a linux image but even though all the tools were installed correctly and the project compiled, the .hex image was different from my usual windows counterpart, as it decided to place the code in a different order from what  I could see in the .map. So it should work the same but it could be a problem if any bug appeared accessing a specific memory address, so I decided to build a windows container instead.

The problem with the windows container is that sensor controller comes in an .exe installer instead of the cli folder for Linux, so when I try to run the exe to install with "C:\temp\sensor_controller_setup.exe --mode unattended" or "powershell -Command  "Start-Process -FilePath 'C:\temp\sensor_controller_setup.exe ' -ArgumentList '--mode unattended -Wait" it doesn't do anything. I'm guessing the instalattion needs a visual interface and cannot be installed through cmd/shell alone in a terminal of a contained. Doing "C:\temp\sensor_controller_setup.exe --help" doesn't return anything either.

I have no problem with installing code composer and it does everything else in the build process creating a correct .hex image, but the sensor controller part I just can't get working. I tried copying my actual windows Program Files (x86) Sensor controller folder into the container but I still get an error when running the program:
"C:/Program Files (x86)/Texas Instruments/Sensor Controller Studio/bin/sensor_controller_studio_cli.exe" -g "C:/firmware/MeteringClipOn/simple_peripheral_cc2640r2lp_app/Application/sce_diehl/GConta.scp" -s -q
makefile:222: recipe for target 'pre-build' failed
gmake[1]: [pre-build] Error -1073741701 (ignored)

I'm new to dockerization and using windows/linux without GUI so I might be skipping some easy solution, so any help is appreciated. 

  • 0
    TI__Guru**** 463941 points
    Iván Moreno said:
    I have no problem with installing code composer and it does everything else in the build process creating a correct .hex image, but the sensor controller part I just can't get working.

    I will bring this thread to the attention of the device team most familiar with Sensor Controller Studio.

    Thanks

    ki

  • 0
    TI__Guru**** 217237 points

    Hi Ivan,

    Here are some SCS resources:

    https://www.ti.com/lit/swru439 
    https://software-dl.ti.com/lprf/sensor_controller_studio/docs/cc13x2_cc26x2_help/html/index.html 

    I know TI has tested the Windows and Linux CLIs, as well as the Windows installer, but I'm not sure whether there is a precedence for a Docker Windows container.  I would expect the sensor_controller_setup.exe to require a GUI for installation, and I don't know what to expect from copying the SCS installation from your local Windows machine.  What behavior or error is returned when you use sensor_controller_studio_cli.exe --help?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 20 points

    Hello Ryan, thank you for your reply!

    I had already taken a look at the resources but obviusly, I'm probably the first to try to do this so is no surprise there's nothing about the installation on a GUI-less windows machine. After copying the installation from my own windows machine, invocking the .exe in any way like with --help results in nothing, it freezes for like 0.1 seconds and then exits the command as if nothing had happend, no logs, no traces, not a nothing on the terminal. When trying to do it through CCS pre-build step I see the error I posted but obviously is a CCS error log, no SCS.

    I know for a fact that after installation that the CLI works on both windows and linux, and linux needs no installation. I wish I could just tell all my colleagues that if Linux is generating slightly different .hexs with the same input we should all just use Linux all the time while developing, but they just love their windows a bit to much.

    Regards,

    Ivan.

  • 0 in reply to Iván Moreno
    TI__Guru**** 217237 points

    I will reach out to the SCS developers to see whether they have encountered a similar situation before and have any recommendations.

    Regards,
    Ryan

  • 0 in reply to Iván Moreno
    TI__Guru**** 217237 points

    Hi Ivan,

    Here is the response from the SCS Development Team:

    "We have not enabled any of our Windows installers to run silently from the command line (or even attempted to run them from the command line). Something would have to be done, as there are multiple options during the GUI-based installation.

    If you do code export only, then the only dependency is the Microsoft Visual C++ 2015 Redistributable, which is version 14.0.23026.0 for SCS 2.9.0. Later builds should also work fine. The installer run it with these options: "vc_redist.x86.exe /install /quiet /norestart".

    Please try this and see if it makes the copied installation work."

    Regards,
    Ryan