[detroit_diesel]

There isn't much special about using the digital signature built-in protection. This by itself will prevent modifications to any of the specified code blocks. It will also prevent pulling the file with engineering tools. 

There are other ways to prevent pulling the file. For example, you could change the byte size of "footprint" space to a smaller size. This will cause engineering tools to fail during pulling a file.

However, the best way is to just use the built-in digital signature protection. The table sets the signature itself for the private key along with the code blocks that are protected. You can set ALL code blocks protected which will prevent any tool from connecting or modifying.

i try change footprint, and no working, i try set key in digital_signature_table and same no working, calterm still reading ecu. you can show how do correctly?