Unfortunately addresses may vary from model to model, so if you don't have access to documentation, it may be hard to do this properly for the first time. I made full memory dump of my card some time ago. You can find it here: -ws.pl/2017/09/importunderstanding-jcop-memory-dump/ This could be used to verify if your offsets matches mine, or guess valid ones. I have also written more detailed description of JCOP pre-personalization, which can be found here: -ws.pl/2017/09/importunderstanding-jcop-pre-personalization/
I'm new to Java card development. I use jcop tools as development kit. When I run simple applet in Eclipse it gives this error. In the run configurations I choose the Java card simulation mode. After successfully installed in simulation mode i want to install app in java card.
In the Getting started doc it only says that "the entry point for ordering is docstore" and gives an old URL. However docstore has been replaced by secure files, so you go there and you are back to square one downloading the unlicensed copy of jcop tools. However if you keep reading way down in Section 5.5.3 it finally says that you have to send your "serial number from the installation" to tools...@nxp.com. Just above section 5.5.3 there is a image of the dialog you get in eclipse when you try and start a new card project with the JCOP tools installed. IN that dialog box you find the serial number.
6. On the dialog box that appears get the serial number and send it along with your PGP public key to tools.jcop.nxp.com and they will send you an encrypted activation code which you can unencrypt with your PGP private key and then restarting eclipse put that key in the 'Verify Activation Code' dialog box.
In one of the older versions of the JCOP tools there is a Sample project included with the tools package. I think it was one of the toolsets for JCOP2.4.x, but I can't be sure - the files are circa 2008 so that's probably correct. In any event, unpack that (JCOPExamples) to a directory, and use that directory as a valid eclipse/jcop workspace for activating your toolset. Otherwise, go the password route mentioned elsewhere.