Am I the only who have missing caracters while capturing of ! (ASCII caracter 33, 21HEX)? While performing SPI analysis I have spotted the weird behaviour. On the main screen all is good and correctly there are the captured !, while into SPI analyser's panel ! are missing. My client version is Jawis-OLS-client ols-0308 but I see also other more recent clients have the same behaviour.
Hi there, playing around with Bus Pirate and SLE4442 smart cards I have found macro (1) only works in firmware 4.2, upper revisions suffer of MSB/LSB inverted order. I could be wrong because I'm not tried all the firmware between 4.2 and last 6.3beta. Surely 5.10 which was the stock firmware in my unit it doesn't work as well like almost all else I have tried, but pretty sure. So I downgrade my Bus Pirate v3.6 to 4.2 firmware release and start to play with 4442 smart cards. Now macro (1) works like a charm:
RAW2WIRE>(1) ISO 7816-3 ATR (RESET on CS) RESET HIGH, CLOCK TICK, RESET LOW ISO 7816-3 reply (uses current LSB setting): 0xA2 0x13 0x10 0x91 Protocol: 2 wire Read type: to end Data units: 256 Data unit length (bits): 8
I know it's the ATR (ISO 7816-3 “answer to reset” response).
Performing macro (2) I get:
RAW2WIRE>(2) ISO 7816-3 reply (uses current LSB setting): 0xFF 0xFF 0xFF 0xFF Protocol: RFU Read type: variable length Data units: RFU Data unit length (bits): 128
which is the same I get with latest firmware's release v6.3-r2151. The problem is I don't understand clearly what the command does mean so I can't understand if what I get is right or no. Hence the question is what does it mean "ISO7816-3 parse only"? Last but not least, I found source code for the old v4.2 firmware release but sadly finally I can't find the v6.3-r2151 which I suppose to be the last one. It seems to me there aren't anything more new. Is in here anybody who know anything about that? Thanks in advance.
I guess the word "REÿ" in the beginning should in reality be "RESET" like for previous versions.
Both cases it's a trunk/corrupted message. I know it's need to use less space as possible in the inside memory of the Bus Pirate, so I guess would be better remove or shorten messages in order to improve the device. Those don't be annoying but remove them would be better IHMO.
Hi, there, as I read elsewhere in order to improve 1.8V support why not use a 74LVCH16245 input buffer instead of the current MC74LCX16245DTG? The LVCH version works from 1.65V, while the LCX needs at least 2.3V and it's pin to pin compatible too. Sadly the LVCH's absolute maximum voltage rating is 6.5V instead of 7V and this is the reverse of the coin but I don't think it would be a big problem. You will could make the replacement only on the buffer wing without affecting the OWLS that maybe it would be dangerous. What do you think? Another question is, is OWLS 1.8V support so bad as it's now? And there would be real and tangible benefits rather than disadvantages in making the change? Thanks in advance.
