#1374 closed defect (fixed)
USB Phoenix overclocking (custom baudrate) doesn't work
Reported by: | petr808 | Owned by: | |
---|---|---|---|
Priority: | critical | Component: | Reader |
Severity: | high | Keywords: | |
Cc: | Sensitive: | no |
Description
Revision
3955 and higher, Ubuntu 10.04.1 64-bit
Issue Description
When I try to overclock card in USB phoenix interface to 6 MHz, it doesn't work in revision about 3955 and higher. Working without any problem in revisions 3928 and lower. The problem seems to be in wrong effective baudrate calculation: in revision 3928, where everything is OK, the effective baudrate calculation looks like:
EB8AE700 r custom baudrate: cardmhz=357 mhz=600 custom_baud=16134 baud_base=24000000 divisor=1488 -> effective baudrate 16129
It sets correct baudrate and communication is OK
But in revision 3955 and higher the effective baudrate calculation doesn't work:
22DE4E00 r standard baudrate: cardmhz=357 mhz=600 -> effective baudrate 9600
So it sets incorrect baudrate and communication is KO
When the issue occurs
Everytime oscam starts and reads ATR from then card.
How the issue is reproducable
Revision: 3955 and higher
Using 6 MHz crystal on Phoenix interface.
Using any for example Cryptoworks card.
Setting in oscam.server:
[reader]
protocol = mouse
device = /dev/ttyUSBX
detect = cd
mhz = 600
cardmhz = 357
<Don't forget to ATTACH (not post here) a log file of oscam in debug mode (start oscam with -d255)!>
Attachments (1)
Change History (3)
by , 12 years ago
comment:1 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
The problem exists only when using compiled files from UMP FileCenter (http://www.ump2002.net/index.php?direction=0&order=mod&directory=OSCam&), when I compile it myself, everything is OK.