• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 40 subscribers
  • Views 634 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.

Original question:

LAUNCHXL-CC3235SF: compilation and SLI image build section question

LAUNCHXL-CC3235SF: [CC3235SF] Why SLImageCreator.exe syscfg create_image command does not support --port option

Piotr Mis
Prodigy 170 points

Other Parts Discussed in Thread: CC3235SF

I'd like to ask why CLI tool SLImageCrestor.exe supports --port option only for some of its commands.

E.g. it is possible to provide it for 'SLImageCreator.exe device info' but it is not accepted in case of 'SLImageCreator.exe syscfg create_image'

Best regards

  • 0
    TI__Mastermind 31055 points

    Hi Piotr,

    Not all of the ImageCreator commands need to target the device in order to run, which is why they don't all take a COM port as an argument. The create_image command is designed to just create the .sli container file with the full device image based on an existing ImageCreator project. It does not need to interact with a device to run.

    Best Regards,

    Ben M

  • 0 in reply to Benjamin Moore
    Prodigy 170 points

    Unfortunately in case of Development image with Autodetect MAC it needs to connect to device.That is why I need --port option also for this 

  • 0 in reply to Piotr Mis
    TI__Mastermind 31055 points

    Hi Piotr,

    I don't believe create_image is what you are looking for then. This is really an operation for creating a final image which could be used to program multiple boards.

    What are you trying to do?

    Thanks,

    Ben M

  • 0 in reply to Benjamin Moore
    Prodigy 170 points

    As in original question (https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1001911/launchxl-cc3235sf-compilation-and-sli-image-build-section-question) we have custom board with CC3235SF.

    I need to build FW from sources and generate final image in development version. I need to have this procedure universal for different boards thus I need to keep option "Auto-Detect MAC" in project configuration.

    Command "SLImageCreator.exe syscfg create_image" is used by CodeComposerStudio.

    Is there any other way to generate SLI file from CommandLine?
    And what is very important - I want to do it without XDS110 - just with FTDI RS232 cable. As I wrote before - it looks that most of SLImageCreator.exe "subcommands" accept --port option and 'device info' subcommand works fine. That is why it's very strange for me why 'syscfg create_image' cannot.

  • 0 in reply to Piotr Mis
    TI__Mastermind 31055 points

    Hi Piotr,

    Why do you need to rebuild the .sli image in development mode many times vs. using production mode? And why is working with Code Composer not a viable option?

    The development mode is not intended to be a scalable approach for programming because it ties the image to the unique MAC address of the device. This is to prevent large scale deployment of a debug application or devices with unlocked JTAG.

    If you still believe you need to take your current approach, you may want to try the "project program" command with the -dev option. See section 7.1.3 of the ImageCreator guide: www.ti.com/lit/swru469

    Alternatively, you will have to create your own script using the existing ImageCreator commands.

    Best Regards,

    Ben M

  • 0 in reply to Benjamin Moore
    Prodigy 170 points

    In short.

    - we have few developers working on the project

    - each developer has own HW on desk

    - source code of FW + configuration files (cfg files with image.cfg and drivers config) along build environment are stored in version control system

    - not all developers have XDS110 probe, but all of us have FTDI USB2UART cables

    I want to achieve a state when each developer is able to build development version of image for HW which has has on his desk WITHOUT manual modification of source code and configuration files. And for sure I do not want to several different configs with different MACs stored in version controll.

    I believe that it was also TI intention to allow creation of dev image with automatic readout of MAC from connected HW wasn't it? What could be other purpose of  'AutoDetect' setting from image.cfg ?

    I am not saying that there is no workaroud (I will experiment with mentioned 'project' subcommand, if not this then maybe additional call to 'SLImageCreator device info' + parsing stdout + adjust cfg file in some temporary location). But that's a little bit like shooting from a cannon to a mosquito.

    I just want to say that it's very strange that SLImageCreator.exe tool is capable for some of its command to have COM provided and for others it cannot.

    Regards

    P.

  • 0 in reply to Piotr Mis
    TI__Mastermind 31055 points

    Hi Piotr,

    Thank you for the detailed explanation of your setup and development challenge. It definitely helps me understand what you are trying to achieve.

    I believe if all engineers are working with the same environment and simply need to update the json file that stores the project configuration then build the image and program it in development mode, the "project program -dev" approach is what you are looking for. This is outside of the scope of the "create_image" command which is why there is no --port option. Let me know if it does work for you.

    If it does not, you may need to create a custom script that uses the existing ImageCreator CLI commands to achieve your goal. I will take the feedback as a potential improvement for a future release of the tool.

    Best Regards,

    Ben M