• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 51 subscribers
  • Views 1247 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.

cc2650: ROM bootloader does not communicate after baud detection

Dennis Page
Intellectual 635 points

Part Number: CC2650
Other Parts Discussed in Thread: CC2640, CC2538

I have a CC2640 on a custom board that does not communicate after baud detection. The CC2640 is fresh from the factory and has not been flashed. I am using the UART serial bootloader (SBL). The code that I am using to flash the CC2640 successfully erases and flashes a BOOSTXL-CC2650 via the UART SBL and UART Rx and Tx pins (not JTAG).

After reset, the 2-byte baud rate automatic detection command 0x55 0x55 is issued and acknowledged with 0x00 0xCC, as it should. Next, COMMAND_PING is issued, and is "not acknowledged" with 0x00 0x33. From then on, there is no response from the CC2640 to any commands. This sequence can be repeated any number of times. I have also tried COMMAND_GET_STATUS, COMMAND_BANK_ERASE. I have tried issuing a dummy command 0x03 0x00 0x00 before and after the baud rate command; the dummy command is never acknowledged. There is no response after the initial baud rate command is acknowledged and the subsequent command is "not acknowledged" by the CC2640. Subsequent baud rate  commands are ignored until reset, as it should be. I have confirmed that the command packets are properly formatted. These exact same commands work properly with the BOOSTXL-CC2650 UART SBL.

On my CC2640 RSM package, the DIO3 SPI CS pin is driven high, DIO0 SPI DO pin is driven high and NRESET pin is driven high. All the VDDS pins have power and all VSS pins are grounded. There is no connection to the JTAG_TCKC and JTAG_TMSC pins. UART0 RX is connected to DIO1 and UART0 TX is connected to DIO2, as required for the RSM package. Communication seems to be established and the bootloader seems to be active.

I have tried various baud rates from 115,200 to 9600 without success after the initial ACK and NACK sequence.

I have carefully read the following literature and am complying with all requirements;

  • CC13x0, CC26x0 SimpleLink™ Wireless MCU Technical Reference Manual swcu117h.pdf
  • CC2538 ROM User's Guide swru333a.pdf
  • CC2538CC26xx Serial Bootloader Interface swra466a.pdf
  • CC2640 SimpleLink™ Bluetooth® Wireless MCU swrs176b.pdf

Please advise a course of action to resolve this issue. I am hoping this is a symptom of a known issue.

  • 0
    TI__Mastermind 25045 points
    Hi Dennis,

    Do you have a log or a logic analyzer trace that you can share with us (successfully and failure sequence)?

    Probably you did this already, but could you please also monitor the reset line on your custom board and verify that you are not getting a reset between the BAUD and PING commands.

    I'm trying to locate a board with the RSM package so I can run a few tests on my side, I'll keep you posted with my results.

    Best regards,

    David
  • 0 in reply to DavidL
    Intellectual 635 points

    Hi David,

    Yes, monitoring the reset line is a good idea. I monitored the reset line and I have not been able to detect the slightest change in voltage. The reset line stays solid at 3.2V.

    Here is a log. Commands sent and received are verified by a protocol sniffer.

    Where:

    • ">" identifies a packet sent to CC2640
    • "~" identifies bytes received
    • "-1" identifies when no response is received within 1ms
    • There is at least 25ms between powering on and reset
    • The reset pulse is 25ms
    • The symptoms are the same if there is no reset after power on
    Powering on CC2650
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00
 ~FC ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~00 ~33 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
5-Sending COMMAND_PING >03 20 20 ~00 ~33 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
COMMAND_PING timeout
Press any key to continue
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~-1 ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
COMMAND_PING timeout
Press any key to continue
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~-1 ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
COMMAND_PING timeout
Press any key to continue
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~-1 ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
COMMAND_PING timeout
Press any key to continue
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~-1 ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
COMMAND_PING timeout
Press any key to continue
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~-1 ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
COMMAND_PING timeout
Press any key to continue
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~-1 ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
COMMAND_PING timeout
Press any key to continue
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~-1 ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
COMMAND_PING timeout
Press any key to continue
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~-1 ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
COMMAND_PING timeout
Press any key to continue
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~-1 ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Not acknowledged
COMMAND_PING timeout
Press any key to continue

  • 0 in reply to Dennis Page
    Intellectual 635 points

    Hi David,

    I removed the reset command between successive groups of pings. Here is the log:

    Powering on CC2650
Reseting CC2650 - Reset
Detecting baud rate >55 55 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00 ~00
 ~00 ~CC Acknowledged
1-Sending COMMAND_PING >03 20 20 ~00 ~33 Not acknowledged
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
5-Sending COMMAND_PING >03 20 20 ~00 ~33 Not acknowledged
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
COMMAND_PING timeout
Press any key to continue
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
6-Sending COMMAND_PING >03 20 20 ~00 ~33 Not acknowledged
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
COMMAND_PING timeout
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
7-Sending COMMAND_PING >03 20 20 ~00 ~33 Not acknowledged
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
COMMAND_PING timeout
1-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
2-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
3-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
4-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
5-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
6-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
7-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
8-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
9-Sending COMMAND_PING >03 20 20 ~-1 ~-1 ~-1 ~-1 ~-1 ~-1 Timeout
COMMAND_PING timeout
Press any key to continue

  • 0 in reply to Dennis Page
    TI__Mastermind 25045 points

    Hi Dennis,

     Unfortunately I have not had any luck reproducing this behavior. I capture the following screenshot from my logic analyzer.

    So at this time I have more questions:

    1. Is it possible for you to take a similar screenshot with your HW?

    2. Also, would it be possible to get a copy of your schematics? Please send me a private message with your contact information (you can click on my profile and send me a private message that way), and I will contact you offline.

    3. Do you have access to the JTAG pins? I do not think this the case, but I just want to confirm this. I'm trying to confirm that your HW is functioning properly. Have you followed the tips from this HW Troubleshooting: http://processors.wiki.ti.com/index.php/CC26xx_HW_Troubleshooting

    Best regards,

      David

  • 0 in reply to DavidL
    Intellectual 635 points

    Hi David,

    Unfortunately, I am not able to provide a logic analyzer screenshot.

    We tapped into the JTAG pins, and this was reported by ccsv7 when testing the connection:

    [Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

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

[Result]


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

C:\Users\Pavilion\AppData\Local\TEXASI~1\
    CCS\ti\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 'jioxds110.dll'.
The library build date was 'Dec 11 2017'.
The library build time was '12:04:14'.
The library package version is '7.0.100.1'.
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: Texas Instruments XDS110 USB Debug Probe_0]

    I will contact you offline to provide the schematic.

    Dennis

  • 0 in reply to Dennis Page
    TI__Mastermind 25045 points
    After we reviewed the Schematic, recommendation were made and the CC2640 bootloader works perfectly.

    Best regards,

    David