??? 10/06/06 02:40 Read: times |
#125870 - Lets not get confused! Responding to: ???'s previous message |
The mcu clock does not have to be a multiple of 3.58MHz in order to communicate at 9600baud. However, it it is, you can use the mcu oscillator as the source for the smartcard clock. 9600 baud * 372 = 3.58MHz thus the *magic* 372 So if you use a different clock frequency for the smartcard, then use this magic number to calculate the baudrate the smartcard will expect. baud rate = Clk freq/372 It seems you can run a separate oscillator for the smartcard. As for wiring the TX & RX together depends on the actual mcu you're using. When the smartcard is sending data, you don't the the TX pin to be driving, on some mcus you can disable the transmitter thus solving your problem or use a mux as you suggest or at a pinch use a resistor in series with the TX pin. Something like 1k might be a start - read the smartcard specs to see how much current it can sink. I think it might be worth your while to purchase the article I referred to. I dare say it will answer a lot of your questions and maybe save some time. |
Topic | Author | Date |
Emulating ISO7816 smart card interface with generi | 01/01/70 00:00 | |
See here | 01/01/70 00:00 | |
Interesting read | 01/01/70 00:00 | |
Can;t find the article | 01/01/70 00:00 | |
Here it is | 01/01/70 00:00 | |
ISO7816 transmission speed | 01/01/70 00:00 | |
ISO7816 transmission speed | 01/01/70 00:00 | |
Lets not get confused! | 01/01/70 00:00 | |
A little confused | 01/01/70 00:00 | |
2 stop bits? | 01/01/70 00:00 | |
Read up on async communications | 01/01/70 00:00 | |
Parity detection | 01/01/70 00:00 | |
use UART mode 3 - that's 9 bits! | 01/01/70 00:00 | |
Same question on AVRfreaks? | 01/01/70 00:00 | |
GSM Only? | 01/01/70 00:00 | |
not exactly GSM only.... | 01/01/70 00:00 | |
All types![]() | 01/01/70 00:00 |