I need to know how to use a object file "protect.o" buy from chip supplier (copy protection chip) into uVision to let the linker works. Supplier give me only object file and not C source code to protect the own key. 1) Where place the command to insert "protect.o" file into uVsion 4.20? 2) What is the command to add into uVsion? 3) HOw to generare "protect.d", "protect.crf", "protect.__i" from "protect.o"? 4) What are the step to follow?
Thank you for reply
Doesn't the supplier give instructions on how to do this??
Object files are not generally portable - you should not even assume that they will be portable between different versions of the same tools.
Therefore the first thing you need to be sure of is that this object file is specifically for use with the particular Keil version that you have.
"1) Where place the command to insert "protect.o" file into uVsion 4.20? "2) What is the command to add into uVsion?"
There is no "command"! uVision is a Graphical user interface; so you use the normal dialogues - same as for adding any other file to a project.
uVision "automatically" knows what to do with a file from its extension: www.keil.com/.../uv4_ca_file_extensions.htm
"3) HOw to generare 'protect.d', 'protect.crf', 'protect.__i' from 'protect.o'?"
Why would you want to do that? They are all outputs from the compiler; an object file is already compiled - so you don't need any of that stuff!
"4) What are the step to follow?"
Please read the manual: http://www.keil.com/support/man/docs/uv4/uv4_ca_sourcefiles.htm
OK, all sound be clear. Yes, my chip supplier know my compiler used and version. I have send to him I2C C code for R/W functions for data exchange with chip. So I hope all will works. Thank you
Either they want to protect their algorithms or their encryption keys.
If they think they can protect algorithms by just distributing object files they are fools. History has shown that the only devices that doesn't get cracked are the devices that people don't care to crack - and then they would probably have managed just fine without any protection in the first place.
If they want to protect a crypto key, it gets even more scary. Every customer should have their own crypto key, in which case it wouldn't have mattered if you - as customer - was allowed to see the crypto key. If they have just one single crypto key for all shipped security devices, then it doesn't matter which of their custoemrs who gets their product cracked. All other customers will also suffer the consequence of the security device having been generally cracked.
By the way - as already noted, object files are very much depending on tool versions. So you now have to make sure that you can always recreate a machine with that specific version of the development tools. Which also requires that Keil are alive and well when you need a new license file for installing on a new computer.