LAUNCHXL-CC1310: After Firmware upgrade via RF Studio 7 2.12.0: debugger fails - A router subpath could not be accessed.

Jan Cumps

Guru 15740 points

Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310, , UNIFLASH

I installed RF Studio 7 latest version, 2.12.0

When I connected a LAUNCHXL-CC1310 LaunchPad, it recognised it as a CC1310 but required a firmware update.

The firmware update went successful, but now RFStudio lists the device as : XDS Device - Unknown,

and in CCS, when I test the XSD connection:

Error connecting to the target:
(Error -242 @ 0x0)
A router subpath could not be accessed.
The board configuration file is probably incorrect.
(Emulation package 8.0.903.4)

I tried to run ccsv8\ccs_base\common\bin>fsclean , as indicated in a few support request.

It reports:

Removing temporary files...
boost::filesystem::remove: De map is niet leeg: "C:\Users\jancu\AppData\Local\Texas Instruments\CCS\ti\10\0"

The issue is not resolved after that.

over 6 years ago

0 YiKai Chen over 6 years ago

Guru 735685 points

Do you try if Flash Programmer 2 can recognize your LAUNCHXL-CC1310? Sometimes you need to restart your desktop to fix this trouble.

0 Jan Cumps over 6 years ago in reply to YiKai Chen

Guru 15740 points

Yes, I checked with all TI programs I have that can talk XDS. Also after a reboot.

Smart RF,
Uniflash
Flash Programmer 2
Code Composer Studio

They report it as XDS110, USB JTAG ID = XDS Firmware, Target Device name = UNKNOWN.

0 YiKai Chen over 6 years ago in reply to Jan Cumps

Guru 735685 points

Try to use xdsdfu to see if it can fix the problem.

0 Jan Cumps over 6 years ago in reply to YiKai Chen

Guru 15740 points

I have done that too. Setting it to update mode, then reloading the standard firmware ti\ccsv8\ccs_base\common\uscif\xds110\firmware.bin

0 YiKai Chen over 6 years ago in reply to Jan Cumps

Guru 735685 points

Do you have another desktop to test this LAUNCHXL-CC1310 to see if it works on another desktop?

0 Jan Cumps over 6 years ago in reply to YiKai Chen

Guru 15740 points

No, but I have another identical CC1310 LaunchPad that I did not open in SmartRF Studio.

0 YiKai Chen over 6 years ago in reply to Jan Cumps

Guru 735685 points

Oops...Run out of idea. @TER do you have any suggestion?

0 TIABO over 6 years ago

TI__Genius 12900 points

Jan,

How does your LAUNCHXL-CC1310 show up in the Windows Device Manager? The expected result is something like this:
What result do you get by running this command? "xdsdfu.exe -e"
(xdsdfu.exe is located in <ccs_installation>/ccsv8/ccs_base/common/uscif/xds110/)
You can try running the following commands (make sure only your CC1310 LaunchPad is connected to your PC):
1. xdsdfu.exe -m
2. xdsdfu.exe -f firmware.bin -r

Let me know how it goes!

Br,
TIABO

0 Jan Cumps over 6 years ago in reply to TIABO

Guru 15740 points

1: yes

D:\ti\ccsv8\ccs_base\common\uscif\xds110>xdsdfu.exe -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2018 Texas Instruments Incorporated.  All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x0451    PID: 0xbef3
Device Name:   XDS110 Embed with CMSIS-DAP
Version:       2.3.0.17
Manufacturer:  Texas Instruments
Serial Num:    firmware
Mode:          Runtime
Configuration: Standard

Found 1 device.

D:\ti\ccsv8\ccs_base\common\uscif\xds110>xdsdfu.exe -m

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2018 Texas Instruments Incorporated.  All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x0451    PID: 0xbef3
Device Name:   XDS110 Embed with CMSIS-DAP
Version:       2.3.0.17
Manufacturer:  Texas Instruments
Serial Num:    firmware
Mode:          Runtime
Configuration: Standard

Switching device into DFU mode.

D:\ti\ccsv8\ccs_base\common\uscif\xds110>xdsdfu.exe -f firmware.bin -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2018 Texas Instruments Incorporated.  All rights reserved.

Scanning USB buses for supported XDS110 devices...

Downloading firmware.bin to device...

The result is the same in SmartRF studio 7 and other applications. Below how it looks in Smart RF Studio.

0 TIABO over 6 years ago in reply to Jan Cumps

TI__Genius 12900 points

Hi,

Still not sure what's going on. Does the problem get resolved if you do the steps in 3 with the attached image?https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/156/firmware_5F00_ccs_5F00_8_5F00_2_5F00_0.bin

Br,
TIABO

0 Jan Cumps over 6 years ago in reply to TIABO

Guru 15740 points

I tried this.

D:\ti\ccsv8\ccs_base\common\uscif\xds110>xdsdfu.exe -m

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2018 Texas Instruments Incorporated.  All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x0451    PID: 0xbef3
Device Name:   XDS110 Embed with CMSIS-DAP
Version:       2.3.0.16
Manufacturer:  Texas Instruments
Serial Num:    firmware
Mode:          Runtime
Configuration: Standard

Switching device into DFU mode.

D:\ti\ccsv8\ccs_base\common\uscif\xds110>xdsdfu.exe -f firmware_ccs_8_2_0.bin -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2018 Texas Instruments Incorporated.  All rights reserved.

Scanning USB buses for supported XDS110 devices...

Downloading firmware_ccs_8_2_0.bin to device...

The result is the same. It registers as an unknown launchpad in the tools.

0 Jan Cumps over 6 years ago in reply to Jan Cumps

Guru 15740 points

When I do a connection test from CCS V8.2, I get this error:

[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)]------------------------------------

C:\Users\jancu\AppData\Local\TEXASI~1\CCS\
    ti\10\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 'Nov 27 2018'.
The library build time was '13:02:43'.
The library package version is '8.0.903.4'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
Updating the XDS110 firmware ... complete.
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 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 '-242' (0xffffff0e).
The title is 'SC_ERR_ROUTER_ACCESS_SUBPATH'.

The explanation is:
A router subpath could not be accessed.
The board configuration file is probably incorrect.

[End: Texas Instruments XDS110 USB Debug Probe]

The content of that testBoard.dat file:

C:\Users\jancu\AppData\Local\TEXASI~1\CCS\ti\10\0\BrdDat>type testboard.dat
# config version=3.5
$ sepk
  pod_drvr=jioxds110.dll
  pod_port=0
  pod_supply=0
  pod_voltage_selection=0
  pod_voltage=0
$ /
$ product
  title="Texas Instruments XDS110 USB"
  alias=TI_XDS110_USB
  name=XDS110
$ /
$ uscif
  tdoedge=FALL
  tclk_program=DEFAULT
  tclk_frequency=2.5MHz
  jtag_isolate=enable
$ /
$ dot7
  dts_usage=enable
  dts_type=xds110
  dts_program=emulator
  dts_frequency=1.0MHz
  ts_format=oscan2
  ts_pin_width=only_two
$ /
$ swd
  swd_debug=disabled
  swo_data=tdo_pin
$ /
@ icepick_c family=icepick_c irbits=6 drbits=1 subpaths=1
  & subpath_0 address=16 default=no custom=yes force=yes pseudo=no cancelreset=0x0
    @ cs_dap_0 family=cs_dap irbits=4 drbits=1 subpaths=1 identify=0x4BA00477 revision=Legacy systemresetwhileconnected=1
      & subpath_1 type=debug address=0 default=no custom=yes force=yes pseudo=no
        @ cortex_m3_0 family=cortex_mxx irbits=0 drbits=0 identify=0x02000000 traceid=0x0
      & /
  & /
# /

0 YiKai Chen over 6 years ago in reply to Jan Cumps

Guru 735685 points

Try to use xdsdfu.exe to assign a serial number (ID) to your XDS110 and see if it works

0 TIABO over 6 years ago in reply to Jan Cumps

TI__Genius 12900 points

Ok, try the following in CCS 8.2 or earlier:

Mass erase device with CPU inaccessible:

The default target configuration files for CC13xx/CC26xx devices enable
"custom configuration" for all subpaths to enable debugging in low power
modes. If the CPU DAP is inaccessible (e.g. locked in CCFG), CCS will not be
able to connect to Icepick to issue Mass Erase. To get around this, modify the
target configuration file (.ccxml) and disable "custom configuration" on
*all* subpaths.
Steps to issue mass erase:
1. Launch target configuration file.
2. In Debug view, select Scripts > CC26xx > MassErase().

TIABO

0 Jan Cumps over 6 years ago in reply to TIABO

Guru 15740 points

I disabled the setting for all subpaths, launched the target,

In the Debug window, it shows as Disconnected.

When I run the MassErase() script, I get this error:

Error connecting to the target:
(Error -2131 @ 0x0)
Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 8.0.903.4)

I also get that error when I right-click on the session and say connect.

0 TIABO over 6 years ago in reply to Jan Cumps

TI__Genius 12900 points

Using the CCXML where you have disabled the "Custom Configuration" in all subpaths, please try the following:
1. Open View > Target Configurations
2. Right click your CCXML and select "Launch Selected Configuration"
3. In the Debug View, right click "Texas Instruments XDS110 ..." and select "Show all cores"
4. Expand "Non Debuggable Devices"
5. Right click Icepick_C and select "Connect Target"

Are you able to connect to the device?

0 Jan Cumps over 6 years ago in reply to TIABO

Guru 15740 points

I see two non debuggable devices, the Icepick_C entry and CS_DAP_0.

When I perform the Connect Target on entry Icepick_C, I get the exact same error as above.

0 TER over 6 years ago in reply to Jan Cumps

TI__Guru**** 317180 points

I discussed this with TIABO. It looks like the CC1310 has been locked fully down caused by the firmware update which should not happen. Due to this, please go to store.ti.com and ask for a refund/ new launchpad and refer to this thread.

0 Jan Cumps over 6 years ago in reply to TER

Guru 15740 points

I tried to do that, but there's no option I can find in the store where you can do such action.

0 TER over 6 years ago in reply to Jan Cumps

TI__Guru**** 317180 points

Try to use the TI store option on ti.com/supportform

Sub-1 GHz

Sub-1 GHz forum

LAUNCHXL-CC1310: After Firmware upgrade via RF Studio 7 2.12.0: debugger fails - A router subpath could not be accessed.