• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 616 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.

CCS/LAUNCHXL-CC1352R1: - Running the Sensor Controller Studio LED Blinker example

James Whitney
Intellectual 490 points

Part Number: LAUNCHXL-CC1352R1

Tool/software: Code Composer Studio

Greetings,

I have just obtained a LaunchXL-CC1352R1 board. My project will require several I2C and SPI sensors and I decided to try to get these going using the Sensor Controller Studio. To get started I decided to try/run the 'LED Blinker' project. The board is fresh out of the box and just connected to a USB port. I am running the appropriate SDK, i.e. SimpleLink CC13x2 CC26x2 SDK 4.20.00.35 and chip cc1352R1F3.

I went through, or examined, all of the entries in the left-side panel, i.e., 'LED Blinker for Launchpad', 'Constants and Data Structures', .... When I get to 'Task Testing' and try to 'Connect', I repeatedly get a 'No Targets Found' error even though the LaunchXL board is plugged in.

Is it correct that I should be able to run - at least this example - without CCS intervention *until* I am ready to incorporate the SCIF into CCS ? I.e., following the steps above, I should have been able to run the 'LED Blinker' example solely in SCS ?

Need help.

Thanks,

Jim

  • 0
    TI__Guru** 101490 points

    Hi Jim,

    Yes you are correct, CCS is not required to debug the sensor controller examples.

    In you case, the issue you are experiencing (repeatedly get a 'No Targets Found' error), make me think to a problem in the connection between the board and the PC. Verify if all the jumpers are set on the board. Verify if no other application (e.g. CCS) is already connected to the board.
    To finish, you could verify if the board is properly detected by CCS (e.g. try to flash the "empty" example from examples\rtos\CC1352R1_LAUNCHXL\drivers\empty on the board).

    I hope this will help,

    Best regards,

  • 0 in reply to Clément
    Intellectual 490 points

    Good evening, Clement,

    As you mention, I also considered that there may have been a connection issue. Earlier as a check I tried the 'Out-of-the-Box' demo. I was able to see 'Project Zero', the RSSI data stream, toggle the LED's, .... I guess that doesn't necessarily confirm the USB connection but at least we know the board isn't dead. I tried two different USB ports, and two different USB cables.

    I then tried the PWM LED project - same issue - 'No Targets Found'. It is going beyond being frustrating.

    I will try the CCS project you mention. Thanks.

    Jim

  • 0 in reply to James Whitney
    Intellectual 490 points

    Good afternoon, Clement,

    The update is this:

    I tried the 'empty' example. Initially, I got the CCS equivalent of 'No Targets Found' (don't have CCS open currently so don't recall the exact wording). I went to 'View' --> 'Target Configuration', then 'Test Connection'. There I received essentially the same type message, and error code, and a 'SC_ERR_XDS110_OPEN' error.

    Eventually, I obtained a solution, which was deceptively simple, but elusive at the same time. Along the route to the solution - even before I contacted the Forum - I had tried two USB ports and two different USB cables - No joy. Not being too motivated + having things plugged into the USB ports on the 'other side' of the laptop, I had only tried the USB ports on the right side of the laptop. After your suggestion and the failed results from the connection test I tried one of the ports on the 'left' side of the laptop. Viola !!! *Everything* worked, i.e., the 'Test Connection' passed, I was able to download and run the 'Empty' project, and when I went back to Sensor Controller Studio the 'LED Blinker' project ran.

    So, it turns out that on my Laptop - an HP 8560W running Windows 7 Professional (older, I know, but dead stable) - the ports on the 'right', which *didn't* work are USB 3.0. The ports on the left, which did work, are USB 2.0.

    Not sure if the 2.0/3.0 issue would be the same for later versions of Windows but that apparently that was my issue.

    Thanks, for your help and suggestion.

    Jim