CCS/LAUNCHXL-CC1352R1: CC1352R1 - Error -242 while trying to flash Launchxl-CC1352R1

Jorge Herrera Santos1

Intellectual 320 points

Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Hello everyone,

I had a problem while I was trying a program based on ADCSINGLECHANNEL example. I attach the program

adcsinglechannel_CC1352R1_LAUNCHXL_tirtos_ccs (1).zip

CCS Cloud and Code Composer Studio show Error -242.

Trying to isolate the problem between debugger and microcontroller, I checked devides on Device Manager and it is recogniced:

Also tryed to scan devide using console:

So I think it is not a question of Debbuger. Trying to find the problem I made a connection test using CCS and got this message:

[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\Sara\AppData\Local\TEXASI~1\CCS\
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 'jioxds110.dll'.
The library build date was 'Aug 26 2019'.
The library build time was '13:34:49'.
The library package version is '8.3.0.00003'.
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 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]

I tryed to Reset the microcontroller using Uniflash but Error -2131 occurred:

Also tryed to flash the microcontroller using other LaunchXL-CC1352R board and it is the same result

Also tryed to Force Mass Erase (using both 2-pin and 4-pin cJTAG) from SmartRF Flash Programmer 2 and I have this result:

Does anyone can help me to fix this error?

Thank you very much,

Jorge

over 5 years ago

0 Jorge Herrera Santos1 over 5 years ago

Intellectual 320 points

Hello again,

I've been reading about configuring a Target Configuration File to try to access to the Flash Memory but I dont know how to create it propperly:

Also I read here (section "A router subpath cannot be accesed") that I can run a script to MassErase but in my menu Script there no scrit available...

It is this the path I need to follow? How could I create the Target Configuration File to try to recovery the microcontroller?

Thank you in advance,

Jorge

0 desouza over 5 years ago in reply to Jorge Herrera Santos1

TI__Guru**** 171034 points

Jorge,

Where you able to connect to this board before? If not, the issue may be due to the board itself - a common issue on Launchpads is to have issues with absent or misplaced jumpers, for example.

One of the issues that throw this error is a misconfiguration between the JTAG configuration on the .ccxml file and the jumpers. In your last screenshot, highlight the branch Texas Instruments XDS110 Debug Probe_0 and in the drop down near the option JTAG / SWD / cJTAG Mode select the cJTAG (1149.7) 2-pin advanced modes.

Hope this helps,

Rafael

0 Jorge Herrera Santos1 over 5 years ago in reply to desouza

Intellectual 320 points

Hello Raphael,

Thank you for your answer. Yes, I was able to connect and flash the board before and it worked fine...

I'm think something in the code caused a continuous reboot of the microcontroller or something like that but the problem is that we can't Reset the CC1352 either reflash... It is impossible to recognize it.

Thank a lot,

Jorge

0 Jorge Herrera Santos1 over 5 years ago in reply to desouza

Intellectual 320 points

Hello Raphael,

That option was the option that was marked:

0 Jorge Herrera Santos1 over 5 years ago in reply to Jorge Herrera Santos1

Intellectual 320 points

Hello,

Is there any update? It has to be a way to reset the microcontroller's memory...

Thanks,

Jorge

0 desouza over 5 years ago in reply to Jorge Herrera Santos1

TI__Guru**** 171034 points

Jorge,

Please apologize for the delay; I missed your reply.

Thanks for sending the screenshot. Can you reduce the speed of the option "The JTAG TCLK Frequency (MHz)" to 5.5MHz. It was observed that the default 8.5MHz speed is not very stable in several boards (this will be reduced back when CCSv9.3 is released later this year).

That is also reported at the following sticky post:

https://e2e.ti.com/support/tools/ccs/f/81/t/821584

Hope this helps,

Rafael

0 Jorge Herrera Santos1 over 5 years ago in reply to desouza

Intellectual 320 points

Hello Rafael,

Thank you very much for the support you are providing me. I tried to reduce the JTAG TCLK Frequency to 5.5MHz but the router subpath can't be accessed yet. I attach picture:

Any other idea or should I change the microcontroller of the board?

Thank you very much,

Jorge

0 desouza over 5 years ago in reply to Jorge Herrera Santos1

TI__Guru**** 171034 points

Jorge,

I am afraid this is the last recourse. I found a few threads that mention a fatal condition for the JTAG connectivity if the code writes invalid code to specific registers (CCFG). I reported this in step 9 of the section Troubleshooting the connect phase of the Debugging JTAG page below:

https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html

Regards,

Rafael

Code Composer Studio™︎

Code Composer Studio forum

CCS/LAUNCHXL-CC1352R1: CC1352R1 - Error -242 while trying to flash Launchxl-CC1352R1