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.

CC3220S: Problem with new SysConfig ImageCreator with SDK4.4 examples

Part Number: CC3220S
Other Parts Discussed in Thread: SYSCONFIG

I'm currently migrating projects to use the new v4.4 SDK with CCS v10.

Having problems generating the necessary output files (in order to FLASH).

To get familiar I'm using the 'local_ota_cc3220s_launchxl_tirtos_ccs' example as per the accompanying documentation with the SDK.

  1. MCU+Image configuration mode has been selected
  2. I then Build Project

however the necessary files aren't generated (no sl_image output files, see pic below). It's as though the 'image.sysconfig' script didn't run. Same for other examples.

I guess I missed something ?

Stuart

  • Hi Stuart,

    Did you import a clean version of the local_ota example from SDK 4.40, or did you change the linked SDK in an existing project?

    Also, can you check what version of SysConfig your project is using? You can do that by going to project properties->General->Products.

    Best regards,

    Sarah

  • Hi Sarah,

    Thanks for the prompt support.

    I installed both CCS v10.1.1.00004 and SDK 4_40_00_07 on a virgin PC so there won't have been any 'legacy' issue I don't think.

    In any case I cleaned the 'local_ota' project but had the same result again.

    Strangely when I checked the version of SysConfig there wasn't one! So I proceeded to click on preferences to discover what was available and installed (or so I thought) v1.6. It still didn't generate the Sl_image files. See the screenshot below for where I'm at now. Restarted CCS and then restarted PC but same result. I also have it installed on another PC but with same result. Did I perhaps miss a step on installation or is SysConfig installed automatically ?

    Stuart

  • Hi Stuart,

    When you go to the Steps tab in the Build menu, what post-build steps do you see?

    Best regards,

    Sarah

  • Hi Sarah,

    I get the following:

    ${CG_TOOL_ROOT}/bin/armobjcopy -O binary --only-section .text --only-section .const --only-section .cinit --only-section .resetVecs ${BuildArtifactFileName} ${BuildArtifactFileBaseName}.bin
    ${COM_TI_SIMPLELINK_CC32XX_SDK_INSTALL_DIR}/source/ti/drivers/net/imagecreator/bin/SLImageCreator.exe syscfg create_image --sdk_path ${COM_TI_SIMPLELINK_CC32XX_SDK_INSTALL_DIR} --json ${CWD}/syscfg/ti_drivers_net_wifi_config.json --file ${CWD}/syscfg/${BuildArtifactFileBaseName}.sli --mcu ${CWD}/${BuildArtifactFileBaseName}.bin

    b rgds,

    Stuart

  • Hi Stuart,

    That all looks correct, and my setup is working as expected. Can you verify the ImageCreator executable exists in your SDK? (source/ti/drivers/net/imagecreator/bin/SLImageCreator.exe)

    Best regards,

    Sarah

  • Hi Sarah,

    Yes, it was there.

    I decided to completely uninstall and re-install 4.4. Same result however I'll detail below (all) the messages I get on importing the 'local_ota' example which I believe provide clues as to what's going on:

    1. After importing I get the following XDC msg:

     2. Upon building there is this first msg:

    3. Then it looks like maybe some errors with SLImageCreator.exe:

    First below is 'makefile:181: recipe for target 'post build' failed'

    Second is 'SLImageCreator.exe:error: unrecognized arguments:'

    b rgds,

    Stuart

  • Hi Stuart,

    I have the same XDCtools warning, but unfortunately I'm not able to replicate that unrecognized arguments error. Have you tried another SDK example, like network_terminal?

    Can you attach the ti_drivers_net_config_wifi.json from your project? 

    Best regards,

    Sarah

  • Hi Sarah,

    I installed SDK 4.4 on my laptop and ran Network Terminal where I received similar messages (see below). Please also find attached the json file you requested (this is for network terminal). Actually having trouble attaching this without an error msg.

    By the way I note the SDK was validated with CCS10.2.0. My CCS is at 10.1 and when I check for updates it only offers 'TI Emulators' (do I need to install this ?).

     

  • Hi Sarah,

    For some reason having trouble attaching the json file using the paper clip ???

    Just gives me a generic error msg

  • Hi Stuart,

    "XDS not detected" is actually a good error, it means ImageCreator got past your arguments error and is trying to build the SLI image. Now you just need to plug in your LaunchPad so the application can detect its MAC address (required to build the image in development mode).

    Best regards,

    Sarah

  • Hi Sarah,

    Thanks Sarah, my oversight! Yes, I am now able to FLASH the device on 2 out of 3 PCs. I had read it but (immediately!) forgotten that the MAC address was needed to generate the output FLASH file. Still got one PC (the original one) giving me trouble (with CCS 10.1.1) however I've updated CCS to 10.2 on two PCs and they're working flawlessly. I expect a similar result with the third troublesome one shortly. 

    Will get back to my project where I have a further question but that belongs in a separate thread. You can close this one out.

    best regards,

    Stuart