Is there a way to encrypt design under Quartus?

you can use .qxp files as a work around:

http://www.altera.com/support/kdb/solutions/rd06242008_7.html

or try requesting the encryption tools from Altera, though that's going to be a bit more work

I had this very same problem a few years a go.

Unless you want the IP released as part of alteras load of IP, you're not going to get it encrypted.

QXP is your only option.

Probably off-topic here, but if you just want others to *test* your design, why not just give them your bitstream/programming file?

Unless they're also co-designers working on other portions of the project, they probably wouldn't need your source files (or encrypted source files).

If you want to encrypt your bitstream file, that's another story.

-daniel

Hi Daniel,

Thank you for your reply. But, I am wondering what is the extension of the bitstream file?

Hi,

Thank you for your reply. But, I am wondering does there exist QXP file for project under Quartus II 7.2 web edition?I didnt find that file in my project folder.

Hi,

Thank you for your reply. But, I am wondering does there exist QXP file for project under Quartus II 7.2 web edition? I didnt find that file in my project folder.

"what is the extension of the bitstream file?"

It's .sof, .pof, .jam, etc... depending on what tool you're using and how you want to configure the device. It's what Altera calls Programming File (generated by the Assembler by default).

"...I am wondering does there exist QXP file..."

This is how Altera does design partitioning. Refer to Altera's resources on design partitioning and floorplanning. For a start, you can use your whole entire design as a single partition and export it as a QXP partition. Later, you may want to try exporting only part of your project as a QXP partition. Check out "Project > Export Design Partition..." from the menu bar. The default is a QXP extension.

Have fun...

Hi daniel,

Thank you for your reply. But, I have one more question. How to do testing on QXP file?Thanks.

You don't really test a QXP file. Before you even export your design as QXP, you first synthesise, place, route, and assemble your design. Then test it (usually a .sof file) on a board. You do this independently from your partner or co-designers.

When you think your design is good enough for integrating into your co-designers design, you export it as a partition (QXP) and tell your co-worker to import it into their Quartus. He will then integrate the partition into his full Quartus design, and perform the full synthesis, place & route, and design assembly flow. His final .sof file will be the integrated design that he can test on his board.

-daniel

If your intent is just for your customer to *try* your IP, then you can just provide them the bitstream file (.sof), and you don't even have to give them your design files (source HDL, and even QXP partition).

Your customer can just work with your .sof file if he has the right board to play with.

I'm not sure what you really want to achieve here. Do you want your customer (or who you're dealing with) to compile your design, or just test / try your solution on a board? If compile is necessary, then QXP or full HDL sources need to be given, otherwise, just the bitstream file will do.