Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed the week of November 23.

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.

CC2652P: Function "APSME_SearchTCLinkKeyEntry" in SDK 5.30 execute wrong result.

Part Number: CC2652P

I have set a API to execute "APSME_SearchTCLinkKeyEntry" in my coordinate application. When coordinate power on, executing APSME_SearchTCLinkKeyEntry can get a correct result. But after coordinate running for a moment, APSME_SearchTCLinkKeyEntry execute with a wrong result.

In my program, there are also API to access "ZCD_NV_EX_TCLK_TABLE", "ZCD_NV_EX_ADDRMGR" and AddrMgr. All of them can be executed with right result .

  • It is due to my adding Hot-NV-id for ZCD_NV_EX_TCLK_TABLE, when APSME_SearchTCLinkKeyEntry execute, the NVOCMP_readContItemApi will be called, which will read a lot of NV-items and compare them. Now I have another way to speed the APSME_SearchTCLinkKeyEntry executing. My ZCD_NV_EX_TCLK_TABLE is set 200, and NV-pages is 3. Before speed  APSME_SearchTCLinkKeyEntry, the latency of it is 20ms. After speed it, the latency is 3~5ms

  • Hi Aries,

    Thank you for following up with the detailed explanation and resolution to your issue!

    Regards,
    Ryan

  • Part Number: CC2652P

    In SDK 5.30,  APSME_SearchTCLinkKeyEntry is executing by lookup NV-item in all Flash, which is too slow. It can be processing like AddrMgr, which is pre-loading NV data into RAM. CC2652P has large Memory space.