Re: [Globalplatform-users] JCOP 31 : "Wrong CLA Byte" with GPShell

[Michael S. <mst...@co...>]

At 11:57 AM 12/16/2008, Sébastien HASCOAT wrote:
>Somebody told me to try that :
> 
>" 
>Honestly, no clue. It works on my side (also tried it with JCOP 31/72 v2.2). The only reason I can think of for SW_CLA_NOT_SUPPORTED at INSTALL[for install&make selectable] is due to wrong security level. But your log doesn't show that (unless GPShell sends something different).
>
>As you seem to have an unfused card, try booting it and repeat the pre-personalization. If you don't know how, contact your distributor to do so or write NXP customer support. "
> 
>(<http://forums.sun.com/thread.jspa?threadID=5355071>http://forums.sun.com/thread.jspa?threadID=5355071)
> 
>So i emailed NXP to ask them how to do. And this evening i'll have a look at all these ideas, maybe i'll find a way to do it !! I thought JavaCard was easier than that :)
>Sébastien


Try sending an identify command:  "00h A4h 04h 00h 09h A0h 00h 00h 01h 67h 41h 30h 00h FFh 00h"

Should return an 6A82h as status plus an array of data.  Fuse state should be offset 14 - 1 byte.  00h is unfused, 01h is fused.

If this is unfused, I'd suggest not using it and get a pre-personalized card from somewhere like USASmartcard.  That should already be set up for normal Javacard usage.  The cards in the unfused state are ready for a bulk manufacturing process (write a memory image) rather than loading an applet.

Mike