• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 51 subscribers
  • Views 213 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.

CC2642R: cc2642 pairing problem

wang jiwei
Prodigy 240 points

Part Number: CC2642R
Other Parts Discussed in Thread: UNIFLASH

hi:

After the mobile phone was connected to the cc2642, it was paired. The cc642 was also successfully paired and saved. After walking away with the phone and disconnecting it, I approached the cc2642 device again. The mobile phone initiated a connection but found that the pairing was lost, so it was paired again. Currently, it appears on a single device and is bound to appear on this device. 

The following is the program source code 

image.png

This is the paired log

image.png

At present, all other devices are functioning normally. This phenomenon only occurs on one cc2642 device, which still shows abnormal conditions. We are concerned that similar problems may occur in other devices and it is necessary to urgently analyze the cause  .I don't know how to analyze this problem and need your support. 

My problem is very urgent and I need your assistance.

 Thank you.

 

  • 0
    TI__Mastermind 44400 points

    Hi,

    Thank you for reaching out. This may be happening if the phone has old pairing information from a previous version of the firmware that ran in that specific CC2642. Can you try erasing all bonds on the phone, reflashing the CC2642, and then retrying the test?

    Best Regards,

    Jan

  • 0
    Prodigy 240 points

    Hi,

          I haven't updated the firmware of cc2642 from normal to abnormal. I tried several different phones, but the same problem occurred. The pairing was successful, but when I connected again, the pairing was lost and I needed to pair it again. I suspect that the NV write failed after pairing. Is this possible? Right now, I'm not trying to restore it, but to analyze the cause of the problem .

  • 0 in reply to wang jiwei
    TI__Mastermind 44400 points

    Hi,

    It is possible there may be an issue with the NV saving. Are you only seeing this on a single CC2642? All of the other devices you have do not show this issue?

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 240 points

    Hi,

    There are many CC2642 devices available on the market here, but currently only one has this issue.

    I read the flash of cc2642 and found that this abnormal device was paired twice and generated 4 NV records. Currently, even after being powered on again, it has not been restored. I need your help to analyze the specific problem and figure out how to optimize and solve it in the future.

    I can't upload the pictures. I can only upload some of the original data of nv to you.

    FF FF FF FF FF FF FF FF FF FF FF FF FF 10 24 00 00 42 10 96 46 05 59 0C 71 F8 00 09 10 20 00 00 21 A0 96 69 3D 32 55 C4 EC C3 D5 4F 5C FB 7C B0 D7 E6 0E 10 23 00 00 42 E0 96 DE 98 41 B9 16 54 B2 6F F5 EF 65 3A BB 8A 53 9E 00 00 00 00 00 00 00 00 00 00 10 CA 10 21 00 00 73 CC 96 AA 21 4A C3 F2 BB 81 ED D5 62 A6 B4 2E F2 D2 20 10 24 00 00 41 C8 96 FF FF FF FF FF FF FF FF 10 20 00 00 21 A0 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 21 00 00 73 24 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 23 00 00 41 F0 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 24 00 00 42 10 96 46 05 59 0C 71 F8 00 09 10 20 00 00 21 A0 96 69 3D 32 55 C4 EC C3 D5 4F 5C FB 7C B0 D7 E6 0E 10 23 00 00 42 E0 96 A1 58 B7 A9 8B 3C 57 30 8F B9 84 1B 0D 5D 9D A5 00 00 00 00 00 00 00 00 00 00 10 F0 10 21 00 00 73 04 96 1D 4C B8 B0 8E 94 8E 1C F4 4E 3D AE 81 E6 CC 08 10 24 00 00 42 E4 96 FF FF FF FF FF FF FF FF 10 20 00 00 21 A0 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 21 00 00 73 24 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 23 00 00 41 F0 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 24 00 00 42 10 96 46 05 59 0C 71 F8 00 09 10 20 00 00 21 A0 96 69 3D 32 55 C4 EC C3 D5 4F 5C FB 7C B0 D7 E6 0E 10 23 00 00 42 E0 96 B7 79 D6 47 18 19 49 1B A9 33 3C 07 AC 9B CE EF 00 00 00 00 00 00 00 00 00 00 10 13 10 21 00 00 71 34 96 9B FA 98 02 BE 02 FC E0 25 7D 6E 9E BC 24 31 23 10 24 00 00 43 38 96 FF FF FF FF FF FF FF FF 10 20 00 00 21 A0 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 21 00 00 73 24 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 23 00 00 41 F0 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 24 00 00 42 10 96 46 05 59 0C 71 F8 00 09 10 20 00 00 21 A0 96 69 3D 32 55 C4 EC C3 D5 4F 5C FB 7C B0 D7 E6 0E 10 23 00 00 42 E0 96 C0 D2 54 DA E5 59 90 A7 2A 41 F0 95 A1 26 BE 69 00 00 00 00 00 00 00 00 00 00 10 A5 10 21 00 00 72 38 96 F5 05 BF 92 65 EB C3 F1 A2 7E 83 64 7B 09 11 4A 10 24 00 00 43 54 96 FF FF FF FF FF FF FF FF 10 20 00 00 21 A0 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 21 00 00 73 24 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 23 00 00 41 F0 96 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 24 00 00 42 10 96 46 05 59 0C 71 F8 00 09 10 20 00 00 21 A0 96 69 3D 32 55 C4 EC C3 D5 4F 5C FB 7C B0 D7 E6 0E 10 23 00 00 42 E0 96 3C 34 45 C6 DA 9D 93 2B 0D F9 06 27 72 51 D8 F1 00 00 00 00 00 00 00 00 00 00 10 70 10 21 00 00 70 BC 96 51 5F E2 C1 E1 DA 71 76 04 DB 54 55 A7 8A 51 71 10 24 00 00 40 08 96 FF FF FF FF FF FF FF FF 10 20 00 00 21 A2 96 FF FF FF FF FF FF FF FF FF FF FF FF

  • 0 in reply to wang jiwei
    TI__Mastermind 44400 points

    Hi,

    Understood. Can you try mass erasing the device through Uniflash, reflashing, and re-testing? I would like to see if the behavior persist if we start from a blank NV region.

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 240 points

    Hi,

    I have compiled the issue into a document and need your assistance. Currently, there have been multiple cases of this problem. 

    Thank you. 

    Analysis of CC2642 Pairing Loss Problem.docx

  • 0 in reply to wang jiwei
    TI__Mastermind 44400 points

    Hi,

    Thank you for running these test! They are very helpful. Given that the demo code works well on the custom board, then this must be an issue on the custom SW running on the custom board. When pairing you need to have a non-zero value for the maximum number of characteristic in your syscfg for it to work properly. Changing the bond manager, will only impact the page of flash dedicated to the SNV. It should not alter your flash layout and addresses ranges so it should be able to succesfully OTA. 

    The notification behavior you are describing sounds like something strange is happening in the application code, can you check which areas you are prepping and sending the notification in your code?

    Best Regards,

    Jan