• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 32 subscribers
  • Views 906 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/IWR6843: lab21- area scanner problem with debug mode

gil albo
Intellectual 725 points
Part Number: IWR6843


Tool/software: Code Composer Studio

Hi,

I want to deal with the area scanner (lab 21) with evm 6843 at debug mode.

I've flashed the board with the debug_bin 6843 and after removing the sop2 i wanted to verify connection to the board from the lab project at the ccs.

I get this message:

[Start]

Execute the command:

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

[Result]


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

C:\Users\GIL~1.ALB\AppData\Local\TEXASI~1\
CCS\ti\1\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 'jioxds110.dll'.
The library build date was 'Sep 28 2018'.
The library build time was '17:26:33'.
The library package version is '8.0.803.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 '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 '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

[End]

I've been at debug mode at other labs at the mmwave toolbox. although i've followed the instruction of the build configuration as appear at:

TI/mmwave_industrial_toolbox_3_0_0/labs/lab0021_area_scanner_68xx/docs/area_scanner_68xx_user_guide.html

i get the error.

Please assist

Gil

  • 0
    TI__Mastermind 23725 points

    Hi Gil,

    Seems like you have trouble connecting to the debugger to the device and not necessarily any issue with the lab you have mentioned in the title.

    A few things to check:

    Are you connecting to the correct usb port that brings the devic's JTAG via  XDS110 device.

    Is the Board set to SOP mode = Functional.

    Please take a look at the   MMWAVEICBOOST and Antenna Module User's Guide  for board level checks and the right switch setting for default mode.

    If after this the debug connection continues to show the connection issue. Please let us know.

    Thank you,

    Vaibhav

  • 0 in reply to Vaibhav Mahimkar
    Intellectual 725 points

    Hi again,

    I want to clarify again.

    It isn't the first time that i debug the evm.

    I succeeded at the other labs.

    Also i followed exact what appears at the user guide for this lab.

    Please look at the output message i provided and try to locate the err cause.also i tried the procedure twice.

    Thank you

    Gil

  • 0 in reply to gil albo
    TI__Mastermind 30405 points

    Hi Gil,

    While you're getting the above error in context of the Area scanner lab, it is not related to the Area scanner lab as you've not yet loaded the lab binary up to this point. As Vaibhav indicated, the error message you've shared indicates a general emulator connection problem. You can  also verify this by running the "Test Connection" feature in the CCS Target configuration. (Double click on the CCS Target configuration->Select Basic Tab-> Press Test Connection as shown below). Could you please run this test and share the output?

    Regards

    -Nitin

  • 0 in reply to Nitin Sakhuja
    TI__Mastermind 30405 points
    Hi Gil,

    Sorry, I missed the point in your message that you've already run the Test connection feature and shared the above output from that. However, the previous response still holds in that the issue appears to be an emulator connection problem and not related to the Area scanner lab.

    Few things to check:
    1. Did you modify any switch settings on the Carrier board? Please make sure that it is set to standalone mode as shown on this page under Physical Setup.

    dev.ti.com/.../

    2. When you connect the XDS110 USB port to your PC, do you see the two COM ports enumerated in Windows Device XDS110 Class Application/User UART and XDS110 Class Auxiliary Data ports?

    3. Are you using the same CCS target configuration which you had working earlier or did you make a new one? In case you made a new CCS target config, could you please check that you have the Texas Instruments XDS110 USB Debug Probe selected in the Connection drop down as shown in the image above?

    -Nitin