• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1817 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2650 Sensor Controller Studio: Target connection failed

Kummi
Mastermind 6220 points

Hi,

We are getting "target connection failed" error with Sensor controller's
Task testing example.

We are using IAR EWARMv7.40 and SRF06EB＋CC2650EM-7ID to test sample programs
as mentioned in the Sensor Controller Studio Quick Start Guide.

Currently we are able to download and run projects(Analog Light Sensor) through IAR
without problem. But with "Task Testing" on Sensor controller Studio we always
get "target connection failed" error.

Please let us know what are the settings necessary to run Task testing on SCS?

Best Regards

  • 0
    TI__Mastermind 29650 points
    Hi Kummi,

    You first need to disconnect the debugger from IAR and then go to the "Task testing" tab in Sensor Controller Studio.
    Press "Generate and output task testing driver source" and then flash the device with the "Task testing" project in IAR.

    Then you need to go back to Sensor Controller Studio and then connect from there to perform debugging.

    Regards,
    Svend
  • 0 in reply to svendbt
    TI__Guru 56590 points

    Also note that every time you do significant changes to the projects such as change IO mapping, alter RAM variables (cfg.x, state.x, input.x, output.x), etc. you will need to generate task testing drivers again and download the "Task Testing" project from IAR/CCS to your device before you start a new debug session from Sensor Controller Studio (SCS) (You can then see changes in the content of scifTestDriverSetup in the generated files). If you do small logic changes to the execution code (simple changes to pAuxRamImage) you do not need to download the "Task Testing" project again. Then you can simply start a new debug session from SCS (the new pAuxRamImage will be loaded).

  • 0 in reply to Eirik V
    Mastermind 6220 points

    Hi Svend and Eirik,

    Thank you!!
    It works after disconnecting IAR.

    Meanwhile we are eagerly waiting for the Sensor Controller projects on CCSv6....
    currenly using free(30 days) version of IAR and it may expire in few days.
    Please let us know if there is any updates on CCS support..

    Best Regards
    Kummi

  • 0 in reply to Kummi
    TI__Guru 56590 points
    The bug fix release (Version 1.0.1) should come out before the end of next week. That version has CCS examples included as well.
  • 0 in reply to Eirik V
    Intellectual 540 points
    I just downloaded this version - how do I go about testing this on CCS, where are these examples?
  • 0 in reply to Shaba Abhiram
    TI__Guru 56590 points
    After you start up sensor controller studio, the examples will be populated within your documents folder:
    C:\Users\<Your User>\Documents\Texas Instruments\Sensor Controller Studio\examples
    Then within CCS go to [Project->Import CCS Project] and select the wanted .projectspec file. If you select just the examples folder you can import all examples at once.
  • 0 in reply to Eirik V
    Intellectual 540 points

    Thanks for that Eriik - When the SCS raises a fwGenAlertInterrupt() - how would I go about trapping that in the sample test project as mentioned above?

    To clarify - when I pull in the task_testing project as you outlined, it seems to be running the while(1) loop in main.c. Is the expectation that the task_testing project is able to put the main MCU to sleep and have the sensor controller wake the main app task? I do not see the call to fwGenAlertInterrupt() causing any change in the main task. 

  • 0 in reply to Shaba Abhiram
    TI__Guru 56590 points
    Hello Shaba,
    The task_testing project is only used for debugging purposes. It will power the AUX domain and keep the MCU domain awake so that the sensor controller studio (SCS) can use the M3 TAP to debug the sensor controller.

    If you instead look at the analog light sensor ti-rtos example you can see how this is implemented. The scTaskAlertCallback is called from a HWI which is triggered when you issue the fwGenAlertInterrupt() call in the sensor controller execution code:
    Hwi_construct(&hwiTaskAlert, INT_SCIF_TASK_ALERT, osalTaskAlertIsr, &hwiParams, NULL);

    Then you can also use the RAM variables in the sensor controller to set flags/events to indicate any kind of user defined status. The application processor (CM3) can read these (locate these variables in the SCIF_TASK_DATA_T struct define).
  • 0 in reply to Eirik V
    Intellectual 540 points

    This works well - I am able to get the SCE to generate interrupts on the main MCU.

    However, I was wondering if it is possible for the SCE to get a pin interrupt from an external sensor / device, which then tells it to do some checking and then potentially alert the main MCU. This is relevant to us because our sensor takes N number of milliseconds to do a measurement once it has been instructed to do so. It would be nice if the SCE got an interrupt on a data ready line, processed the data and then issued the alert to the main MCU. Hope that makes sense :)

    Thanks for all the help Eirik - your insight is very much appreciated :)

  • 0 in reply to Shaba Abhiram
    TI__Guru 56590 points
    Just browsing some old threads. The current version of SCS on web (1.1.0) support this feature now (GPIO Event Trigger). Version 1.2.0 will be released soon.