OK, I was successful when using instParam parameter in GPShell script. I have put "install_for_install -AID A00000000101 -pkgAID A000000001 -instAID A00000000101 -instParam 0x00". The APDU sent was:
80E60C001C05A00000000106A0000000010106A00000000101010004C90200000000 So this worked but I still want to know why the install parameters were "C9020000" and not "C900" as in Eclipse? thanks, dejan > -----Original Message----- > From: Gambin Dejan > Sent: Wednesday, September 13, 2006 9:23 AM > To: 'Karsten Ohme' > Cc: 'MUSCLE' > Subject: Problem with install_for_install in GPShell 1.3.1 > > Hi, > > After successfully executing the "install_for_load" and > "load" commands I get an error trying to instantiate the > Muscle applet using "install_for_install". I have enabled > APDU tracing and compared this APDU with the one sent by > Eclipse (that was succcessful). Here are the notes: > > 1. GPShell install_for_install - the parameters used in > script file are: > > install_for_install -AID A00000000101 -pkgAID A000000001 > -instAID A00000000101 > > APDU -> 80E60C001805A00000000106A0000000010106A000000001010100000000 > > 2. Eclipse - the command was "install -i A00000000101 > A000000001 A00000000101" (successful) > > APDU -> > 80E60C001A05A00000000106A0000000010106A00000000101010002C9000000 > > Obviously, the difference is that Eclipse sent the "install > parameters" data and GPShell did not. As I can see in > GlobalPlatform standard, it says that "install parameters > field" is mandatory and must have 2-n bytes. What am I missing? > > regards, dejan > _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
