3_7 funcard fix here

[Tesla]

The IFS is a very simple command so the fun card does process it correctly, infact the 3.7 problem is nothing to do with any failure of the funcard to process a command. Its very simple and fundamental it has nothing to do with stuntguys FAQ or commands or failure to respond to commands. Repeated IFS means what? knowing that a IFS always follows immedialy after the ATR.

[PaddyBhoy]

Originally Posted by timetrex

With the repeated IFS you could say that the IRD has asked the smartcard to change its IFS, the cards being hardcoded with responses etc but I would think if it keeps asking to change it then the card was unable to change the ITS to the requested value.

From reading,that is about the crux of it.

NagraVision cards are coded to reset to the default $20, so it would seem that the 3.7 update has changed the response that the box excepts to something greater than the $20

As a result, any commands whose response is > $20 bytes either have deal with a response that is chained (which i would imagine would be harder), or the IFS has to be adjusted upwards.

The logs for the first IFS in 3.6 shows the following

21 40 08 ; A0 CA 00 00 02 12 00 06 15
12 00 08 ; 92 04 1B 34 56 78 90 00 1D

which as we know worked

whereas straightaway you see that the IFS for the 3.7 has issues

21 C1 01 ; FE 1F
12 E1 01 ; FE 0C

it would seem that it cannot get past the second set of bytes

Am i on the right tracks?

[PaddyBhoy]

Originally Posted by Tesla

The IFS is a very simple command so the fun card does process it correctly, infact the 3.7 problem is nothing to do with any failure of the funcard to process a command. Its very simple and fundamental it has nothing to do with stuntguys FAQ or commands or failure to respond to commands. Repeated IFS means what? knowing that a IFS always follows immedialy after the ATR.

lol i think that has blown my thoery out of the water

[Tesla]

One thing to know about logs is unless you log it yourself you dont know when the logger started logging data so you may not see the IFS command at the beginning of the log beacause the logger missed it but it was there immediatly after the ATR. A word of caution with this its a common mistake to dive into commands and technical stuff and jump to conclusions. As said previously you need to know what is hapenning to the fun card to repeatedly log IFS, nothing to do with commands?

[666]

@Tesla are you from data, and you went down the icp way. but the easyer way is timer/counter1 instead of the Timer0

[Tesla]

I do tend to go for 'sexy' coding lol. Any fix is a good fix and if you get into this in any detail you will find there is always more than one way to end up with the same result.

[dannyt0812]

Originally Posted by Tesla

The IFS is a very simple command so the fun card does process it correctly, infact the 3.7 problem is nothing to do with any failure of the funcard to process a command. Its very simple and fundamental it has nothing to do with stuntguys FAQ or commands or failure to respond to commands. Repeated IFS means what? knowing that a IFS always follows immedialy after the ATR.

This is all way out of my league at the moment but im really interested so want to dive straight in lol

This may sound stupid but it seems as if the card keeps resetting itself because in the 3.7 it is looking for an IFS above $20, where as the IFS on the card is only upto $20.

[G77]

if the logs you have got are the ones i did, logging is from boot for 100 packets. with a au card with no keys in it. (a freshly progged card)

oh, and there from c+w

[PaddyBhoy]

i believe they are your logs G77, thanks for taking the time to upload them

[Tesla]

Quote - the card keeps resetting itself

Take a team point that man. Correct the card is repeatedly reset, the funcard was always struggling with its comms. The firmware version 3.6 ignored these failures and kept going. Unfortunately the 3.7 firmware was less tolerant of these failings and so repeatedly reset the card. Sunrise, the giver of light' realised the fun card failings a while ago and engineered a fix for it, so he had a fix already for different reasons, before 3.7 came into being, he is a very clever bloke.

So you now no what is happening its the end of the logs and stuntguys for the time being. Now the next bit what else do you know about 3.7 and what works and what does not work?