• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 55 subscribers
  • Views 425 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.

CC2652P7: Application issue.

Reed
Expert 1950 points
Part Number: CC2652P7
Other Parts Discussed in Thread: SIMPLELINK-CC13XX-CC26XX-SDK, Z-STACK, CC1352P7

Hi，

Project: door lock 

Problem: Sometimes the CC2652 crashes, and the phenomenon is that the power supply to the chip is normal at 3.3V,

the IO is interrupted without response, and the chip cannot be reset when Reset_n forcibly pulls down. It is confirmed

that the internal watchdog of the chip is enabled. If an exception occurs, the door lock can be restored only after being

powered on.

Here is the initialization code.

The message for hanging up is as follows.

  • 0
    TI__Guru**** 218567 points

    Hi Reed,

    Are you referring to Z-Stack door_lock?  What is the node being evaluated (ZC, ZR, ZED)?  Which version of the SIMPLELINK-CC13XX-CC26XX-SDK are you evaluating?  Can this behavior be replicated with the default door_lock project or with a CC1352P7_4 LaunchPad?  Have you submitted your custom hardware design to SIMPLELINK-2-4GHZ-DESIGN-REVIEWS for further review?  Being unable to perform a reset line recovery could indicate a hardware issue rather than firmware problems.  Please provide more details about the nature of the device crash and what specific environment/network procedures must take place for it to occur.

    Regards,
    Ryan