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.

  • Resolved

CCS/CC2650STK: Can't start the System Analyzer despite the README.md saying so

Expert 1885 points

Replies: 16

Views: 380

Part Number: CC2650STK

Tool/software: Code Composer Studio

I use CCC 9.1, the Sensor Tag CC2650STK and the XDS110 Debugger.

I build and debug the example uartecho_CC2650STK_TI from tirex and halt the execution in the Debugger.

I open Tools -> System Analyzer -> Duration Analysis and get an error:

The README says:

  • This example also demonstrates System Analyzer in CCS. This is accomplished via stop-mode reading of the logs on the target. Halt the target and open System Analyzer as described in the TI-RTOS User Guide's Viewing the Logs.

Do I still need to configure something ?

Thanks

Peter

  • In reply to janet:

    Hi Janet

    Great, thanks !

    What would be a reasonable logger size on the CC2650STK ?

    Thanks

    Peter

  • In reply to Peter Vittali:

    Hi Peter,

    Each Log_writeUC3() puts 32 bytes into the Log buffer (assuming 64-bit timestamp).  So for each function enter/exit, that's 64 bytes.  It would depend on how many function calls you are making, and how often you halt the target so System Analyzer can upload the logs.

    Best regards,

    Janet

  • In reply to janet:

    Hi Janet

    This is weird , I had only on start/stop call , so only 64 bytes were logged ...

    In the meantime if have lost access:

    [Start: Texas Instruments XDS110 USB Debug Probe]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    /home/p/.ti/ccs910/0/0/BrdDat/testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'libjioxds110.so'.
    The library build date was 'Jun  3 2019'.
    The library build time was '15:03:57'.
    The library package version is '8.2.0.00004'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '5' (0x00000005).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the XDS110 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for XDS110 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-230' (0xffffff1a).
    The title is 'SC_ERR_PATH_MEASURE'.

    The explanation is:
    The measured lengths of the JTAG IR and DR scan-paths are invalid.
    This indicates that an error exists in the link-delay or scan-path.

    [End: Texas Instruments XDS110 USB Debug Probe]

    From what I have learned by browsing the forum , I might have bricked my device, whatever that means.

    I am on Linux, what flash erase procedure would you recommend ?

    Thanks

    Peter

  • In reply to Peter Vittali:

    Hi Peter,

    I'm not sure about the emulator error you are getting.  You could try turning off profiling (you can still do benchmarking with UIABenchmark), by setting in your .cfg file:

    LoggingSetup.enableContextAwareFunctionProfiler = false;

    Best regards,

    Janet

  • In reply to janet:

    Hi Janet

    I currently have several issues with the Sensor Tags when debugging under Linux, I purchased a couple of CC1352 LaunchPads where I will test the SA.

    I'll be back ....

    Kind regards

    Peter

  • In reply to janet:

    Hi Janet

    I have now received the SensorTag DevPack and the log configuration works as expected. There seems to be an issue when using the XDS110 standalone probe with the Sensor Tags.

    Kind regards

    Peter

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.