If you're willing to go under the constraints of the NDA and various business practices to get access, some of the secure ICs are quite well documented and even have decent tooling. But outside NDAs and approved paths for access, info is limited.
-
If one needed a pedantic workaround for this, you could merely have comments like "NDA Derived Details: See Private Doc X page/section Y" as the real comment in the real source code tree.
That's a very good solution if the NDA allows it. Some NDAs are crazy, may even prevent you from disclosing that Private Doc X exists.
-
-
Well, I wonder what
@MicrochipTech has to say about this and their ECC608. I will be re-reading my NDA soon. It would be a shame to not allow sharing. -
I'm really curious what their response would be. Honestly, I was looking at their public site and they seem to publish more details on that chip than most do without an NDA. It's possible for them to grant specific permission to document some things as part of your product.
End of conversation
New conversation -
-
-
Few NDAs would permit you to reference their documents directly in public materials. What I meant was to have the comment reference an internal document of your own / your organization's, which would include the explanations and/or further references required.
-
Ah, okay. Yes, that should work.
- Show replies
New conversation -
-
-
A number of NDAs I've dealt with don't even permit the disclosure of the existence of the NDA itself except to own legal advisors or by court order.
-
That is true. But that doesn't prevent you from leaving a comment if your code saying that ...something... has caused you to document this matter outside the code and hold that as proprietary. Nor is it necessary to specify which or whose NDA.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.