Jtag 2100 problem. Old software 3_1L . Cannot find bk byte

[zeroprobe]

Hi guys. I've jtagged a few 2100s in the past on versions 3.3b and 3.5b so I know my set up is working ok.

I'm having trouble with a box with software version 3_1L . I have found the IRD which I think was at byte 0x20040004 but the BK which I thought would be right next to it does not work when trying to change the netid via funcard.

Is there anyway to set the netid via jtag so I can upgrade the version. Thanks for your help.

[zeroprobe]

I think I solved it. I've changed the netid via jtag with the samsung tool so hopefully i'll get the right byte with the updated software.

It could be the netid funcard method didn't work with the older version and maybe my boxkey is right after all.

[spikebaby]

NEW J-TAG 3.6 BYTES please read before the questions are asked

check this post for new bk byte

[wirraljim]

hi can anybody tell me where i can see the bk on a chipped funcard, i'm trying to update a previously chipped box and i keep getting blank screens, i read in these forums its because the callback not been cut (i cut it now) but i read vm can change the bk which would cause this so i would like to try find the bk off my funcard to edit (i think the 10th number yeah, any help would be much appreciated
cheers
jimmy

[Mucker666]

read your FUNcard
save your external EEP file as a .HEX
then open in Notepad goto these lines
and your IRD is where yyyyyyyy
and your BK is xxxxxxxxxxxxxxxxx

:1010000007270154010001000000000000yyyyyyC7
:10101000yy000000000000000000000000000000A8
:1010200000XXXXXXXXXXXXXXXX0738065400003000

[spikebaby]

they cannot change the bk on a funcard, only a mosc