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 detectors. Sebastien On Sun, Jul 4, 2010 at 11:26 PM, Drasko DRASKOVIC < [email protected]> wrote: > On Sun, Jul 4, 2010 at 10:48 PM, Luisa <[email protected]> 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 1-5Mhz > ? > > 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. > > BR, > Drasko > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.drizzle.com/mailman/listinfo/muscle >
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
