CC2652R: Unable to open Device Control Panel SmartRF Studio 7

Part Number: CC2652R

Hello,

In SmartRF Studio 7 my XDS110 is found in the List of Connected Devices.
My controller CC2652R is found.
When I try to open the Device Control Panel the following error occurs:

It seems that the XDS110 is trying to upload some firmware but this is not happening for some reason.
My previous program with a LED is still running but is getting reset a few (2x?) times.
When I upload through "Flash Programmer 2" in 4-pin JTAG everything goes correctly.
Is SmartRF Studio trying to upload through 2-pin JTAG?

Looking forward to some reactions.

  • Hello,

    Please try updating to the latest version and let me know if the issue persists. 

    Thanks,

    Alexis

  • Updated SmartRF Studio to version 2.21.0 (version of 29-april).
    It also updated the XDS110.

    The error still occur but now there is some information about the error shown in the message. See the picture.


    What does these errors mean?

  • Hello,

    Please try performing a forced Mass Erase using Flash Programmer 2 

    This can be done by selecting the device from the panel on the left, clicking on the wrench in the top right corner, and selecting "CC13xx/CC26xx Forced Mass Erase"

    Thanks,

    Alexis

  • The Forced Mass Erase can successfully be done.

    I believe the problem is that the DC/DC converter is not working on my custom board. (This is an other issue I'm still working on, read on other topics that the inductance can be too small)
    When I try to debug with Code Composer Studio when the "Enable DCDC" is active it won't succeed.
    When I set the "Enable DCDC" to non-active the debugger can do its thing.

    I think the firmware of "studio_fw_cc13x2_cc26x2_rev2_sram.bin" has "Enable DCDC" to active.
    Can this be confirmed?

  • Hello,

    Smart RF Studio does enable DC/DC by default, but I don't believe that is what is causing your issue. I tested on my end by removing the DC/DC circuit and the device panel still opened and functioned for me. 

    My colleague informed me that we've seen this issue before caused by not enough current. Make sure that your power supply is reliable (or try turning up the current limit). If you have one, try testing the same setup with a LaunchPad and see if you observe the same issue.

    Thanks,

    Alexis