Smartreader+ driveri i upute

[labud]

Linux:
Most distro's have FTDI drivers included.
If not check: http://ftdi-usb-sio.sourceforge.net

Windows:
Refer to /Drivers_Windows

DM7020:
Refer to /Drivers_DM7020

DM7025:
Refer to /Drivers_DM7025

DM7000:
No drivers package available as of yet.
Feel free to compile the kernel modules yourself.



Smartreader+ integraters manual

* Smartreader modes

  The Smartreader+ had two modes, command mode and data mode.
  Till the CMD mode is entered the smartreader+ is working as a phoenix device at 3,57Mhz.
  After entering CMD mode and returning to DATA mode the reader is configured as Smartreader+
  and will probably not work as a phoenix till the next time it's cold started by removing the device from the USB port.
  In the CMD mode it's possible to program the settings like frequency, protocol, etu, N and inversion.

* Mode selection

  To enter the CMD mode set the reader to 5 databits.
 
  example:

   /* set smartreader in CMD mode */
   struct termios term;
   tcgetattr(deviceFd, &term);
   term.c_cflag &= ~CSIZE;
   term.c_cflag |= CS5;
   tcsetattr(deviceFd, TCSANOW, &term);

  To enter the DATA mode set the reader to 8 databits.

  example:

   /* set smartreader in DATA mode */
   struct termios term;
   tcgetattr(deviceFd, &term);
   term.c_cflag &= ~CSIZE;
   term.c_cflag |= CS8;
   tcsetattr(deviceFd, TCSANOW, &term);

  The Smartreader+ doesn't switch by itself so it's to the user to make sure that setting all the right values
  you exit CMD mode and enter DATA mode for receiving/sending data to the smartcard.

  note: Settings are activated by leaving CMD mode!

* Settings

  setting nr   payload     response
  1     FF FF DD   sets Fi and Di factors
  2     FR EQ     sets the frequency
  3     NN     sets the N value
  4     PR     sets the protocol
  5     IN     sets inversion on(1)/off(0)

  there is no response from the Smartreader+ after accepting the settings.

  Example: Smartreader+ settings for ISO7816 t=0 smartcards:

   sr+ <-- CMD MODE
   sr+ <-- 01 01 74 01
   sr+ <-- 02 0D FB
   sr+ <-- 03 00
   sr+ <-- 04 00
   sr+ <-- 05 00
   sr+ <-- DATA MODE
   sr+ <-- toggle reset
   sr+ --> ATR

* Available frequencies

  3.20, 3.43, 3.69, 4.00, 4.36, 4.80, 5.34, 6.00, 6.86, 8.00, 9.61, 12.0 and 16.0 MHz

The user can selected any freqency. The Smartreader+ will selected the nearest available.



dreambox update example

check if the device has been recognized

root@dm7020 /tmp # dmesg
<...........>
usb 1-1.4: USB disconnect, address 4
FTDI 8U232AM Compatible ttyUSB0: FTDI 8U232AM Compatible converter now disconnected from ttyUSB0
ftdi_sio 1-1.4:1.0: device disconnected
usb 1-1.4: new full speed USB device using address 5
ftdi_sio 1-1.4:1.0: FTDI 8U232AM Compatible converter detected
usb 1-1.4: FTDI 8U232AM Compatible converter now attached to ttyUSB0

device has been recognized by the dreambox

root@dm7020 /tmp # ./srp_update_ppc -d /dev/usb/tts/0
smartreader+ version v1.1

ok so we found a reader version v1.1, time to update

root@dm7020 /tmp # ./srp_update_ppc -d /dev/usb/tts/0 -b
smartreader+ version v1.1
bootloader mode activated
Remove and reinsert SmartReader+ then restart application

remove the reader and reinsert then issue the flash command

root@dm7020 /tmp # ./srp_update_ppc -d /dev/usb/tts/0 -f
start flashing
########################################################## done
Please remove and reinsert SmartReader+

remove the reader and reinsert now we start the config tool

root@dm7020 /tmp # ./srp_tools_ppc -d /dev/usb/tts/0
smartreader+ version v1.3
MODE autoswitch
FREQ 3.69 Mhz
KERNEL normal
T_MODE t = 0
EGT 0

its recognized ok, now we set it for dreambox mode

root@dm7020 /tmp # ./srp_tools_ppc -d /dev/usb/tts/0 -p 1
smartreader+ version v1.3
MODE autoswitch
FREQ 3.69 Mhz
KERNEL dreambox
T_MODE t = 0
EGT 0
ok done.

Pc update example

check if the device has been recognized

tux@x-c2c559d7c6af4:~$ dmesg
<...........>
usb 5-1.4: new full speed USB device using ehci_hcd and address 9
usb 5-1.4: configuration #1 chosen from 1 choice
ftdi_sio 5-1.4:1.0: FTDI USB Serial Device converter detected
drivers/usb/serial/ftdi_sio.c: Detected FT232BM
usb 5-1.4: FTDI USB Serial Device converter now attached to ttyUSB0

ok device is recognized

tux@x-c2c559d7c6af4:~$ ./srp_update_x86
smartreader+ version v1.1

ok so we found a reader version v1.1, time to update

tux@x-c2c559d7c6af4:~$ ./srp_update_x86 -b
smartreader+ version v1.1
bootloader mode activated
Remove and reinsert SmartReader+ then restart application

remove the reader and reinsert then issue the flash command

tux@x-c2c559d7c6af4:~$ ./srp_update_x86 -f
start flashing
########################################################## done
Please remove and reinsert SmartReader+

remove the reader and reinsert now we start the config tool

tux@x-c2c559d7c6af4:~$ ./srp_tools_x86
smartreader+ version v1.3
MODE autoswitch
FREQ 3.69 Mhz
KERNEL normal
T_MODE t = 0
EGT 0
ok done.


Reader settings examples


check the options by issuing the help command

tux@x-c2c559d7c6af4:~$ ./srp_tools_x86 -h
Smartreader+ configtool v1.3
usage:
options:
-d (default comport = "/dev/ttyUSB0")
-p <0 = pc / 1 = dreambox>
-m <0 = autoswitch / 1 = fixed Mhz> mode
in fixed mode you can also apply:
-x
-t t = val
-e egt = val
Set the reader to 8 Mhz fixed
tux@x-c2c559d7c6af4:~$ ./srp_tools_x86 -m 1 -x 6
smartreader+ version v1.3
MODE fixed
FREQ 8.00 Mhz
KERNEL normal
T_MODE t = 0
EGT 0

Set the reader to 5.33 Mhz fixed

tux@x-c2c559d7c6af4:~$ ./srp_tools_x86 -m 1 -x 9
smartreader+ version v1.3
MODE fixed
FREQ 5.33 Mhz
KERNEL normal
T_MODE t = 0
EGT 0

Set the reader back to autoswitch mode

tux@x-c2c559d7c6af4:~$ ./srp_tools_x86 -m 0
smartreader+ version v1.3
MODE autoswitch
FREQ 5.33 Mhz
KERNEL normal
T_MODE t = 0
EGT 0

Ok set to autoswitch, even the frequency is still set to 5,33 Mhz the autoswitch will override this settings and
choose from either 3,57 Mhz or 6 Mhz (t=0 or t=1 card)


Possible reader frequencies


READER VALUES MHZ

3 16
4 12
5 9.61
6 8
7 6.86
8 6
9 5.34
10 4.80
11 4.36
12 4
13 3.69
14 3.43
15 3.20

[gemeosat]

So since there are no drivers for the Dm7000, it means it doesnt work on it?