One bit of feedback on Beta 2.0.2.7 is that the simulators don't seem to work with T=1.
Steps to reproduce:
- Install JCKit Beta 2.0.2.7
- Create a new project/solution
- Select 'Standard', 'Default', 'A40CR', or 'eJava Token' simulator
- Select 'T=1'
- Enable PC/SC (for testing T=1 connections, it doesn't change the outcome)
- Start the debugger
The error result is:
Code: Select all
Disconnect apdu port with JCVM successfully
Protocol not Supported.
>> /card -a ""
Protocol not Supported.
IDE connect jcvm failedReason:No error.
>> set-key 255/1/DES-ECB/404142434445464748494A4B4C4D4E4F 255/2/DES-ECB/404142434445464748494A4B4C4D4E4F 255/3/DES-ECB/404142434445464748494A4B4C4D4E4F
>> init-update 255
>> 80 50 00 00 08 F1 14 69 18 89 EA 7E A7 1C
00 00
>> ext-auth
>> 80 50 00 00 08 69 49 0A 36 77 07 EA 1B 1C
00 00
>> upload "C:\workspace\HelloWorld\HelloWorld\bin\HelloWorldPackage\javacard\HelloWorldPackage.cap"
>> 80 E6 02 00 13 06 00 11 22 33 44 55 08 A0 00 00 00 03 00 00 00 00 00 00 01
<< 00 00 Jcvm is not connected
An operation was attempted on something that is not a socket.
Download cap failed...
If you select 'T=0 / T=1', it starts correctly, but if connect using pyApdutool you can only use T=0, not T=1 (protocol error).
Cheers,
ko