CC2652R7: CC2652R7 Will not work.

Hello Corey Ross,

I hope you are well. To better understand your issue and situation could you include the following: Your SDK version, CCS version, and example code tested (from SDK). Was the first launchpad that did not work also a CC2652R7? Our latest SDK for the CC2652R7 is the "7.10.01.24" sdk (link here). Could you also briefly explain your goals with the CC2652R7? 

Thanks,
Alex F

My SDK is v7.10.10.24, my CCS is v12.04.0 and the example code I have is from the TI github, connectedhomeip. My first launchpad was CC3235MOD. But it didn't work with it either.

Hi Corey,

Are you able to supply links from your previous Google inquiries for more details?  Please answer the following questions so that I may know more about your current situation:

• Have you read through and followed the instructions on the Matter SimpleLink Academy Labs?
• Are all Linux prerequisites installed according to the build instructions?  Either the matter or connectedhomeip github repositories are sufficient.
• Does the build environment complete successfully?
• What Matter device example project are you attempting to make and are you able to build a default example without errors? SysConfig v1.15 or v1.16.2 are confirmed to work as expected.
• Are you attempting to make any changes to the default project that I should be aware of?
• How are you programming the CC2652R7 once you have created an output image?  My recommendation is Uniflash v8.4.

Screenshots or logs of the exact issue would be quite beneficial to further identifying the problem.

Regards,
Ryan

I was trying to build the lock up. It says it compiles but it always stops here. I am using Uniflash to program it. I have compiled from connectedhomeip and the matter git but neither work. I have tried to do the lighting app as well, but it wont compile from either of the sources. I believe all of the prereqs are there. I have also tried to use sysconfig 1.15 and 1.16. I have made no changes to any of the code provided.

Can you please try using the attached chip-LP_CC2652R7-lighting-example-bim.hex image?  This would determine whether the hardware is sufficient.  You should be able to observe BTN-1 turning on the red LED and BTN-2 turning it off on the LP-CC2652R7 without needing to connect to a Matter fabric.  The UART output should look as such:

OpenThread started: OK
Setting OpenThread device type to MINIMAL END DEVICE
Initialize Server
Server initializing...
Initializing FabricTable from persistent storage
Last Known Good Time: 2023-10-04T14:30:07
AccessControl: initializing
Examples::AccessControlDelegate::Init
AccessControl: setting
DefaultAclStorage: initializing
DefaultAclStorage: 0 entries loaded
UDP::Init bind&listen port=5540
UDP::Init bound to port=5540
BLEBase::Init - setting/overriding transport
TransportMgr initialized
Using Thread extended MAC for hostname.
Using ZAP configuration...
Failed to read stored attribute (0, 0x0000_0028, 0x0000_0005: a0
Failed to read stored attribute (0, 0x0000_0028, 0x0000_0010: a0
Failed to read stored attribute (0, 0x0000_002C, 0x0000_0000: a0
Failed to read stored attribute (0, 0x0000_002C, 0x0000_0001: a0
Failed to read stored attribute (1, 0x0000_0006, 0x0000_0000: a0
Failed to read stored attribute (1, 0x0000_0006, 0x0000_4003: a0
Failed to read stored attribute (1, 0x0000_0008, 0x0000_0000: a0
Failed to read stored attribute (1, 0x0000_0008, 0x0000_4000: a0
AccessControlCluster: initializing
Initiating Admin Commissioning cluster.
Endpoint 0, Cluster 0x0000_0030 update version to 769273d6
Cluster callback: 0x0000_0030
GeneralDiagnostics: OnDeviceReboot
Endpoint 0, Cluster 0x0000_0033 update version to 8bc6c8aa
LogEvent event number: 0x0000000000010000 priority: 2, endpoint id:  0x0 cluster id: 0x0000_0033 event id: 0x3 Sys timestamp: 0x00000000000001FA
Endpoint 0, Cluster 0x0000_0004 update version to b3e767c0
Cluster callback: 0x0000_0004
Groups attribute ID: 0x0000_0000 Type: 24 Value: 128, length 1
Endpoint 0, Cluster 0x0000_0004 update version to b3e767c1
Cluster callback: 0x0000_0004
Groups attribute ID: 0x0000_FFFC Type: 27 Value: 1, length 4
Endpoint 0, Cluster 0x0000_002B update version to 57c4ed9c
Cluster callback: 0x0000_002B
Endpoint 1, Cluster 0x0000_0003 update version to 75662499
Cluster callback: 0x0000_0003
Identify attribute ID: 0x0000_0001 Type: 48 Value: 2, length 1
Endpoint 1, Cluster 0x0000_0004 update version to d823708a
Cluster callback: 0x0000_0004
Groups attribute ID: 0x0000_0000 Type: 24 Value: 128, length 1
Endpoint 1, Cluster 0x0000_0004 update version to d823708b
Cluster callback: 0x0000_0004
Groups attribute ID: 0x0000_FFFC Type: 27 Value: 1, length 4
On/Off set value: 1 0
On/off already set to new value
Endpoint 1, Cluster 0x0000_0008 update version to 57424444
Cluster callback: 0x0000_0008
Endpoint 1, Cluster 0x0000_0300 update version to 47b2bb2f
Cluster callback: 0x0000_0300
Endpoint 1, Cluster 0x0000_0300 update version to 47b2bb30
Cluster callback: 0x0000_0300
Endpoint 1, Cluster 0x0000_0300 update version to 47b2bb31
Cluster callback: 0x0000_0300
Endpoint 1, Cluster 0x0000_0406 update version to e2500a6c
Cluster callback: 0x0000_0406
Endpoint 1, Cluster 0x0000_0406 update version to e2500a6d
Cluster callback: 0x0000_0406
Updating services using commissioning mode 0
Using Thread extended MAC for hostname.
Using Thread extended MAC for hostname.
Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
Failed to advertise extended commissionable node: 3
Scheduling extended discovery timeout in 900s
Failed to finalize service update: 1c
Delaying proxy of operational discovery: missing delegate
CASE Server enabling CASE session setups
SecureSession[0x20010ca8]: Allocated Type:2 LSID:39304
Allocated SecureSession (0x20010ca8) - waiting for Sigma1 msg
Joining Multicast groups
Emitting StartUp event
LogEvent event number: 0x0000000000010001 priority: 2, endpoint id:  0x0 cluster id: 0x0000_0028 event id: 0x0 Sys timestamp: 0x00000000000002D2
Server Listening...
Initialize LEDs
Initialize buttons
On/Off ep1 value: 0
Device Configuration:
  Serial Number: TEST_SN
  Vendor Id: 65521 (0xFFF1)
  Product Id: 32773 (0x8005)
  Hardware Version: 0
  Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
  Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
  Manufacturing Date: (not set)
  Device Type: 65535 (0xFFFF)
Stopping the watchdog timer
Starting the periodic query timer, timeout: 86400 seconds
SetupQRCode: [MT:6FCJ142C00KA0648G00]
Copy/paste the below URL in a browser to see the QR Code:
https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A6FCJ142C00KA0648G00
Manual pairing code: [34970112332]

Differences in the log outputs are due to example types and the github repo used, however your UART log does appear to end prematurely as it should be displaying device configurations and pairing codes afterwards.  This would indicate that the device is in a locked/frozen state.  What operating system are you using and are any errors or warnings generated during the build process?

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/538/chip_2D00_LP_5F00_CC2652R7_2D00_lighting_2D00_example_2D00_bim.hex

Regards,
Ryan

I am on ubuntu 22.04.3. I will compile it again, but I believe there were no warnings generated.

Also, be sure to erase all device memory before re-programming (under the Uniflash Settings & Utilities tab).  Previous NV memory contents could be interpreted as corrupt and may be affecting the device behavior.

Regards,
Ryan

I do that every time. The file your provided worked.

I setting a that extends the UART readout. I listed out the QR code and everything. I tried to pair it to my nest and it says its not verified.

Sorry i went to hit reply and hit resolved. There was a setting in the debug that they set to limit what the uart was out putting. I got the lock app to work. I still cant get the lighting app to work. The device that I am trying to program is to take an input from an external source and notify you on your phone/nest. This was just step one to get it to work.

Are you unable to get the lighting app you built to work, the one I provided, or either?  And are the devices freezing/locked up or simply not connecting to the Google Nest Home?  Nevertheless, if you have a working lock-app which you are able to build independently then I recommend that you begin your project development from there.

Regards,
Ryan

Its connected and working. I am trying to find the pin layout to be able to take an input from an external source. The file that i had to edit was args.gni in ~/connectedhomeip/examples/lock-app/cc13x2x7_26xx2x7/out/debug. It had chip_progress_logging set to true. It was preset to false. When I changed that I was able to get the QR code and once I had that it connected no problem. I have it set up to turn a light on and off and play a song. But, my end game is to have a device that I have send a high to one of the pins and when that happens it triggers a notification on the phone and allows the home nest to make a sound.