• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 744 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.

TMS320C6748: Applications on C6748 Secure device NOT work after binding process

zhongfan yang
Prodigy 235 points

Part Number: TMS320C6748

I've searched through the posts and found many users of C6748 secure device have the same problem but didn't get a single useful (publicly available) answer. It's really frustrating that we users have to repeat this questions over and over again to get problems sorted out on an individual bases and I can't see whatever compromise to your device security it'll pose if TI just put more clarity into their documents !

I have developed an application on C6748, which works fine before binding process. After binding process by calling secure kernel  API in setUserKey(), and after power cycling the board nothing happens. Every thing looks fine in binding process, even return value from encryption API. And I have followed every detail, every fine print in the official pdf document. What am I missing here??

regards

zfyoung 

  

  • 0
    TI__Guru 65405 points
    The team is notified. They will post their feedback directly here.

    BR
    Tsvetolin Shulev
  • 0 in reply to Cvetolin Shulev-XID
    Prodigy 235 points

               So 3 days passed, and NOT a single word of feedback from your TI team. This is a known implementation issue with the C6748 secure device ('-E').  I'm baffled by why TI would deliberately withhold the necessary information to a very legitimate, reasonable design request. WITHOUT PROPER BINDING FUNCTION, C6748-E IS USELESS FOR IP PROTECTION. ARE THEY REALLY THINKING OBSCURITY WILL BE ALL THAT IT TAKES TO PROTECT SECURITY IN THE LONG TERM?

    BR

    zfyoung

  • 0 in reply to zhongfan yang
    TI__Guru** 116960 points
    Zfyoung,

    Sorry for the delayed response on this feature on the device. I was tied up with some priority tasks due to which I was not able to get to this earlier.

    While the security feature is broadly supported, the details of the Secure ROM functions and firewalls needs additional precautions for sharing broadly. Also, the licensing for the additional examples we have developed prevent us from sharing this on public E2E forums. The additonal material was developed to shared with customers through a local contact but on the E2E, we are required to share on one on one basis.

    Please accept the connect request and I can send you the additional examples for reference. The most likely reason for the binding process failing is that encrypted value from the setUserKey() API is not being written back to the correct memory location in the header as expected by the ROM.

    Regards,
    Rahul
  • 0 in reply to Rahul Prabhu
    Prodigy 235 points
    Thanks, Pahul. I've accepted your connect request and sent you a private message. Hope to receive your advice on this issue.

    Regards
    zfyoung
  • 0 in reply to zhongfan yang
    Prodigy 235 points
    Thanks for the help from Rahul Prabhu that I was able to nail down the cause of the binding failure.

    The reason is that I forgot the signature requirement of AIS binary image which is mentioned briefly in user document. After patching the binding image with the correct signature, the application runs fine. If the TI doc could merge all the engineering related issues into one succinct chapter rather than scatter it all over the places, it would make a much clearer reading. And thanks again for the support from TI team.

    Best Regards
    zfyoung