• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 239 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.

Original question:

CC2640R2F: Generating New Security Keys problem.

CC2640R2F: RE: Problem Generating / Using New OAD Security Keys

Nick Sears
Prodigy 230 points

Part Number: CC2640R2F

I was having the same issue as the poster in this post from a few months back. Their issue was never really noticed or addressed in the response it seems, but if you look closely you can see that the key X and Y portions aren't presented correctly. They appear to be shifted and truncated by one hex digit. I tried to fix it based on the full key that seemed to be presented correctly, but could never get it to work.

However, I just realized the issue. The previous poster (I presume) and I were running the script in Python 2 (2.7.10 on OSX for me). Running it with Python 3, everything works as expected. Just wanted to post so that hopefully the previous post can be updated with this information, since it could have saved me a few hours of debugging attempts.

Thanks!

  • 0
    TI__Intellectual 1670 points

    Hi Nick,

    Thank you for posting this!

    I'll have a look at your proposed fix and get back to you.

    Best regards,

    Vetle

  • 0
    TI__Intellectual 1670 points

    Hi Nick,

    I tested this out, and noticed that the issue is caused due to a difference in how Python 2.7.x and 3.7.x prints the formatted string. In Python 3.7.X an additional " b'xxxx' " is used to identify the intermediate formatting used, and so the extra character is cropped in the tool. This implementation will therefore cause the string represented in Python 2.7 to be cropped one character too much.

    I have opened an internal bug issue, and the documentation will be updated for the next release.

    Best regards,

    Vetle