Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Luisa (acptsysgmail.com)
Date: Tue Jul 06 2010 - 12:03:30 CDT
Hi Drasko and Sebastien,
Drasko, my fault. I meant 9600 Hz on my last email, rather than 96Khz.
And, Sebastien, that comment was unvaluable! I couldn't get to a point
where that would had shown up from trial and error. So thanks both!.
Well, I'm not still getting it. I'd say my card is definetely not
answering me each 372uS. Though I've got yet some tests to be done.
Will keep on trying, but the situation is being the same, whatever I
do, the card asnwers me with just the TS at a fixed speed, above the
372uS between bits.
Also, just to know I'm not wrong with this as well, I'm supossed to
toggle the clock line each etu, don't I? or does the card expects a
high and just next to it, a low on the clock line? I'm using the
former, though have also tried with the latter with no success.
In fact, I noticed the card is giving me that TS byte alone even when
I don't toggle the clock at all during the reset sequence.
For the record, I'm expecting data from the card after I toggle the clock line.
And about the hardware, is within the allowed tollerances. My guess is
that the problem is either in my firmware, or in my spanish id card
not allowing a cold reset at 5 volts (perhaps the majority of chips
have already gone down to 3.3 or so, I don't know).
That's all by now. I did setup a google code account, though I've only
uploaded the schematics:
On 7/5/10, Sébastien Lorquet <squalylgmail.com> wrote:
> You're overclocking your card and the hardware overclock detector inside the
> card stops the card. Only TS is sent because this is automatic and hardware
> driven, but as soon as software starts, HW detectors are enabled, the faulty
> condition is detected and the card is muted in a while(1); loop.
> At reset, a card MUST be clocked a 372 etu (default params) and the clock
> must be kept within limits, ie at a max of ~4 MHz
> Are you sure the voltages are in the mandated range? 5V +- 5%, or 10% don't
> remember which tolerance must be met. Card also have over / under voltage
> On Sun, Jul 4, 2010 at 11:26 PM, Drasko DRASKOVIC <
> drasko.draskovicgmail.com> wrote:
>> On Sun, Jul 4, 2010 at 10:48 PM, Luisa <acptsysgmail.com> wrote:
>> > Hi,
>> > Thanks for your answers.
>> > I've got a bit further with this, though not much more either.
>> > I found out the card, albeit being initalized as the iso says, and
>> > having the clock line toggling 96000 Hz, is answering me with a bit
>> > each +/- 20 microseconds.
>> Why are you clocking your card with 96kHz ? Should not it be clocked
>> What is "bit" in your case ? Is it value during one ETU, as it should
>> be, or you are looking your clock (which is wrong) ?
>> Clock your card with 1Mhz, and have in mind ETU value while decoding
>> characters, because it defines your baud rate. Inital ETU for ATR will
>> be 372/1Mhz = 372uS. "Bit" is a value taken during this period.
>> Character duration will accordingly be 1(start bit) + 8 + 1(parity
>> bit) + 2(guard bits) = 12 ETUs, i.e. 12*372uS.
>> Muscle mailing list
Muscle mailing list