Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Yes, encrypted Verilog files are ASCII. Unless the tool supports a standard encryption mechanism like IEEE P1735, the Verilog source must be specifically encrypted for each tool that will need to read it.
When I encrypt my code, I do it with some key-word. Should I give this key-word to someone who receive this encrypted code so that he/she would be able to simulate or synthesize it?
If I don't need to provide such key-word, how tools are able to understand the encrypted code?
It depends on the encryption mechanism used by the tools you have. Public Key Encryption is a one-way encryption meaning that you use one key (public) to encrypt, and another key (private) to decrypt. That private key is only known by the tool vendor.
The IEEE P1735 standard is tied to a licensing mechanism that controls what the tool is able to do with an encrypted model. You might be able to encrypt a model so that anyone can simulate it, but not synthesize it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
