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: AESECB_startOperation hangs in zed example

Part Number: CC2652P7
Other Parts Discussed in Thread: CC2652R7, SYSCONFIG

A customer is enabling the installcode generated TCLK in the zed_doorlock example by calling Zstackapi_bdbSetActiveCentralizedLinkKeyReq at the end of zclSampleDoorLock_Init:

However the program hangs after the call and never returns. Using the ROV tool, the problem has been loacated at the call of HwiP_setFunc inside AESECB_startOperation in AESECBCC26XX.c. When step into this function, an exception occurs:

Using the assembly step into button, it can be found that the program was stuck in an infinite loop between 0x1002de0e and 0x1002de10. The exception view of the ROV Hwi looks as below:

And the two PC addresses point to HwiP_setFunc and AESECB_oneStepEncrypt:

   

The customer has done a few modifications to the example, such as the memory map, but I'm not sure which part caused this issue. Please help to locate the root cause of this, thanks!

  

BR,

Shuyang

  • Hi Shuyang,

    I'm not observing this issue with a CC26X2R or CC2652R7 project.  What is the value of the installCode?  Please make sure that it is 18 bytes long and includes the install code and CRC, as demonstrated in the Zigbee Security Features SLA.

    Regards,
    Ryan

  • Hi Ryan,

    This issue only appears in customer's code. The customer was able to run the SDK example modified by following the SLA on their hardware, so the install code and MAC address can be confirmed to be OK. But when they tried to use the API in their own project, the program hangs.

    The customer's project is based on zed_doorlock example and BIM on-chip example, the most significant change is they implement a custom bootloader, which just jumps to the application address. I first thought it has something to do with their TI drivers implementation, so I tried comment out all the peripheral initialization code (such as GPIO_init, I2C_init, Uart...) but the issue remains. I also have tried create a similar project based on the LaunchPad examples with the exactly same memory map and app.cfg, but could not reproduce the issue. So I'm out of ideas right now...

    Are you able to find any clues according to the ROV exception? Or any suggestion for the next step to debug?

    Best regards,

    Shuyang

  • Thank you for providing this additional information.  Based on their debug information, perhaps there should also be a focus on HW/SW priorities and stack resource allocations instead of just the TI Driver implementations.  What version of the SimpleLink SDK are they evaluating?  Please have them monitor their heap and stack usage, increasing if necessary.  Has the customer added any tasks to their project or changed SysConfig settings?  You could try implementing their changes in increments until the issue appears.

    Regards,
    Ryan

  • Hi Ryan,

    The issue has been resolved. The initialization code has been commented out by customer, it runs normal after adding it back, thanks for support.

    BR,

    Shuyang