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.

CCS/LAUNCHXL-F28379D: Cloud dev tools does not detect Launchpad

Part Number: LAUNCHXL-F28379D

Tool/software: Code Composer Studio

Hello,

After installing TICloudAgent Bridge chrome extension and TI Cloud Agent application, when I attach the LAUNCHXL-F28379D via USB, the device is not properly detected (screenshot attached). Also, when I try to run an example project (Blinky), I don't see anything under "Target" in the CCS Cloud IDE - both options are grayed out. 

  • Dhrubo,

    Unfortunately we can only identify and detect LaunchPads that have an onboard XDS110 that uses a serial number to identify which LaunchPad it is.  This one uses the older XDS100v2.

    For me when I import the blinky example I get the options to run and debug in CCS Cloud:

    Note that CCS Cloud only supports working with a single core so I imported the example from under the CPU1 category.

    For F28379D (which has multiple cores) I think you will quickly outgrow what CCS Cloud is capable of and will want to download and install CCS Desktop.

    Regards,

    John

  • Hello John,

    I imported the blinky.c example from Resource Explorer under CPU1, so I'm hoping that should work as a single core operation. My "Debug" option is also grayed out (screenshot attached).

    Am I missing any intermediary step?

    Thank you.

  • Interesting.  If I import that example I see the same as you.  Can you try importing the led_ex1_blinky from under the driverlib examples instead of under bitfield?

    john

  • Hello John,

    If I import "led_ex1_blinky" under driverlib, the program runs properly. 

    Is this becausy "blinky_cpu01" does not contain the "device" folder?

  • It looks like the blinky_cpu01 has its project settings as Generic C28x device instead of a specific device.  CCS Cloud does not like that.  I will follow up with the C2000 team as it looks like we should do some clean up to make these work better with CCS Cloud.

    Note that you will to move to CCS Desktop when starting real development.  CCS Cloud is great for evaluation on a single core but with this device you have two 28x cores and to take advantage of them both you will need to use CCS Desktop.

    Regards,

    John

  • John,

    Thanks for the help and for clearing things out. We do all our actual code dev work in CCS Desktop, but we are trying to utilize the CCS Cloud for training purposes (so limitation w/ single core is not a very big issue).