Yes, I can imagine ... That would leave no way at all for a person to get any picture at all of what sort of code the compiler produces, though, wouldn't it? How, then would one get a notion of how good a product the KEIL people have to offer? If they want to demonstrate their product's superiority over their competitors, wouldn't they have to do that in some way, i.e. let the potential purchaser see how good their code is? As an alternative, they could make it possible to run their code on the desired target. They've chosen not to do the latter, haven't they?


Wouldn't the rest of the software still prevent the practical use in a commercial sense? After all, who wants to generate two linkable objects of each module, run them through his own linker, and only then load them into the target. Further, that would still leave the miscreant without the ability to use the simulator and some of the other "features", would it not?


Is the demo linker the only "protection" that KEIL has built into their demo package? I had the impression that there were other features that also didn't work on larger code bodies and limited the location in the memory map.

As I said before, I suspect that those who are smart, skilled, and diligent enough to do what I suggested have already thought of it themselves, or, much more likely, those bent on stealing someone else's work product are too lazy to do all that work just to be able to load a small code snipped into their target. After all, there are other KEIL features that don't work outside the demo range. I suspect there are other things that KEIL could do if they really wanted to (a) enable people evaluating their product for a specific purpose or use in a chip not presently supported by their linker, but that they have simply chosen not to do that. The result is that all one in that situation can evaluate is their GUI.

RE