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/AM5728: An error occurred while hard opening the controller.

Part Number: AM5728

Tool/software: Code Composer Studio

I used an emulator to connect boards on CCS.

When I click Test Connection in .ccxml, CCS prints the following messages:

[Start: SEED XDS560V2 STM USB Emulator_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -F inform,logfile=yes -S pathlength -S integrity

[Result]


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

/root/.ti/ti/0/0/BrdDat/testBoard.dat

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

This utility has selected a 560/2xx-class product.
This utility will load the program 'seed560v2u.out'.
Loaded FPGA Image: /root/ti/ccsv7/ccs_base/common/uscif/./././././dtc_top.jbc
The library build date was 'Nov  6 2017'.
The library build time was '09:31:00'.
The library package version is '7.0.100.0'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '6' (0x00000006).
The controller has an insertion length of '0' (0x00000000).
The cable+pod has a version number of '8' (0x00000008).
The cable+pod has a capability number of '7423' (0x00001cff).
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 Nano-TBC VHDL.
The link is a 560-class second-generation-560 cable.
The software is configured for Nano-TBC VHDL features.
The controller will be software reset via its registers.
The controller has a logic ONE on its EMU[0] input pin.
The controller has a logic ONE on its EMU[1] input pin.
The controller will use falling-edge timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '2' (0x0002).
The utility logic has not previously detected a power-loss.
The utility logic is not currently detecting a power-loss.
Loaded FPGA Image: /root/ti/ccsv7/ccs_base/common/uscif/./././././dtc_top.jbc

An error occurred while hard opening the controller.

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

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

The value is '-283' (0xfffffee5).
The title is 'SC_ERR_CLK_MEASURE_OOR'.

The explanation is:
The measured TCLK frequency value is out of the supported range.
The utility or debugger has requested the JTAG clock
frequency to be measured. This has failed because the
actual value is too high or too low for the hardware
that measures the JTAG clock - its `out of range'.

[End: SEED XDS560V2 STM USB Emulator_0]

Evaluation Modules&Board: MINI 5728

Emulator: SEED-XDS560v2PLUS

CCS Version: 7.4.0.00015

  • Hi,

    Can you check if the device is set for adaptive clocking? If so, it is unsupported by the device and should be set to fixed.

    The default setting is used to be a common isuse with Spectrum digital and Blackhawk Debug Probes, but I am unsure if it is still present on Seed probes.

    This configuration is set on the Advanced target configuration options of the Debug User's Guide below (search the page for "Advanced target configuration"):
    software-dl.ti.com/.../ccs_debug-main.html

    Hope this helps,
    Rafael
  • Thanks!

    This problem has been solved. I changed the DIP switch so that the board's boot order is SD-EMMC-USB. Then I deleted the content on the EMMC and removed the SD card. Now click on test connection, CCS can print the following correctly:

    [Start: SEED XDS560V2 USB Emulator_0]
    
    Execute the command:
    
    %ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -F inform,logfile=yes -S pathlength -S integrity
    
    [Result]
    
    
    -----[Print the board config pathname(s)]------------------------------------
    
    C:\Users\willzoe\AppData\Local\TEXASI~1\
        CCS\ti\0\0\BrdDat\testBoard.dat
    
    -----[Print the reset-command software log-file]-----------------------------
    
    This utility has selected a 560/2xx-class product.
    This utility will load the program 'seed560v2u.out'.
    The library build date was 'Jan 24 2019'.
    The library build time was '13:27:55'.
    The library package version is '8.0.903.6'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '6' (0x00000006).
    The controller has an insertion length of '0' (0x00000000).
    The cable+pod has a version number of '8' (0x00000008).
    The cable+pod has a capability number of '7423' (0x00001cff).
    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 Nano-TBC VHDL.
    The link is a 560-class second-generation-560 cable.
    The software is configured for Nano-TBC VHDL features.
    The controller will be software reset via its registers.
    The controller has a logic ONE on its EMU[0] input pin.
    The controller has a logic ONE on its EMU[1] input pin.
    The controller will use falling-edge timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '2' (0x0002).
    The utility logic has not previously detected a power-loss.
    The utility logic is not currently detecting a power-loss.
    
    -----[The log-file for the JTAG TCLK output generated from the PLL]----------
    
      Test  Size   Coord      MHz    Flag  Result       Description
      ~~~~  ~~~~  ~~~~~~~  ~~~~~~~~  ~~~~  ~~~~~~~~~~~  ~~~~~~~~~~~~~~~~~~~
        1   none  - 01 00  500.0kHz   -    similar      isit internal clock
        2   none  - 01 09  570.3kHz   -    similar      isit internal clock
        3     64  - 01 00  500.0kHz   O    good value   measure path length
        4     16  - 01 00  500.0kHz   O    good value   auto step initial
        5     16  - 01 0D  601.6kHz   O    good value   auto step delta
        6     16  - 01 1C  718.8kHz   O    good value   auto step delta
        7     16  - 01 2E  859.4kHz   O    good value   auto step delta
        8     16  + 00 02  1.031MHz   O    good value   auto step delta
        9     16  + 00 0F  1.234MHz   O    good value   auto step delta
       10     16  + 00 1F  1.484MHz   O    good value   auto step delta
       11     16  + 00 32  1.781MHz   O    good value   auto step delta
       12     16  + 01 04  2.125MHz   O    good value   auto step delta
       13     16  + 01 11  2.531MHz   O    good value   auto step delta
       14     16  + 01 21  3.031MHz   O    good value   auto step delta
       15     16  + 01 34  3.625MHz   O    good value   auto step delta
       16     16  + 02 05  4.313MHz   O    good value   auto step delta
       17     16  + 02 13  5.188MHz   O    good value   auto step delta
       18     16  + 02 23  6.188MHz   O    good value   auto step delta
       19     16  + 02 37  7.438MHz   O    good value   auto step delta
       20     16  + 03 07  8.875MHz   O    good value   auto step delta
       21     16  + 03 15  10.63MHz   O    good value   auto step delta
       22     16  + 03 26  12.75MHz   O    good value   auto step delta
       23     16  + 03 3A  15.25MHz   O    good value   auto step delta
       24     16  + 04 09  18.25MHz  {?}   bad value    auto step delta
       25     64  + 03 29  13.13MHz   O    good value   auto power initial
       26     64  + 03 39  15.13MHz   O    good value   auto power delta
       27     64  + 04 01  16.25MHz   i    stuck ir     auto power delta
       28     64  + 03 3D  15.63MHz   O    good value   auto power delta
       29     64  + 03 3F  15.88MHz   O    good value   auto power delta
       30     64  + 04 00  16.00MHz   O    good value   auto power delta
       31     64  + 04 00  16.00MHz   O    good value   auto power delta
       32     64  + 03 32  14.25MHz  {O}   good value   auto margin initial
    
    The first internal/external clock test resuts are:
    The expect frequency was 500000Hz.
    The actual frequency was 499872Hz.
    The delta frequency was 128Hz.
    
    The second internal/external clock test resuts are:
    The expect frequency was 570312Hz.
    The actual frequency was 569976Hz.
    The delta frequency was 336Hz.
    
    In the scan-path tests:
    The test length was 2048 bits.
    The JTAG IR length was 6 bits.
    The JTAG DR length was 1 bits.
    
    The IR/DR scan-path tests used 32 frequencies.
    The IR/DR scan-path tests used 500.0kHz as the initial frequency.
    The IR/DR scan-path tests used 18.25MHz as the highest frequency.
    The IR/DR scan-path tests used 14.25MHz as the final frequency.
    
    -----[Measure the source and frequency of the final JTAG TCLKR input]--------
    
    The frequency of the JTAG TCLKR input is measured as 14.24MHz.
    
    The frequency of the JTAG TCLKR input and TCLKO output signals are similar.
    The target system likely uses the TCLKO output from the emulator PLL.
    
    -----[Perform the standard path-length test on the JTAG IR and DR]-----------
    
    This path-length test uses blocks of 64 32-bit words.
    
     || // -- \\  The test for the JTAG IR instruction path-length succeeded.
    The JTAG IR instruction path-length is 6 bits.
    
    The test for the JTAG DR bypass path-length succeeded.
    The JTAG DR bypass path-length is 1 bits.
    
    -----[Perform the Integrity scan-test on the JTAG IR]------------------------
    
    This test will use blocks of 64 32-bit words.
    This test will be applied just once.
    
    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.
    
    The JTAG IR Integrity scan-test has succeeded.
    
    -----[Perform the Integrity scan-test on the JTAG DR]------------------------
    
    This test will use blocks of 64 32-bit words.
    This test will be applied just once.
    
    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.
    
    The JTAG DR Integrity scan-test has succeeded.
    
    [End: SEED XDS560V2 USB Emulator_0]