I will play with it and let you know.
Tuner doesn't work for me but I can play with other aspects.
Posts by lutz diagram
-
-
the -- error is a hardware check error and has nothing to do with the userdata
-
the receiver never gets to that stage before the --
if you look at threads on other sites you will see the -- is a fault in the boot process before the receiver even checks the tuner.Code
Display More00000000 414C 6920 436F 7270 0000 0000 4D33 3630 ALi Corp....M360 00000010 3220 4844 2053 5442 0000 0000 4150 5020 2 HD STB....APP 00000020 2069 6E69 7420 6F6B 0D0A 0000 626F 6F74 init ok....boot 00000030 0000 0000 2020 2D2D 2000 0000 4F53 445F .... -- ...OSD_ 00000040 5333 365F 3100 0000 4F53 445F 5333 365F S36_1...OSD_S36_ 00000050 3000 0000 4445 4356 5F53 3336 3031 5F30 0...DECV_S3601_0 00000060 0000 0000 4552 524F 523A 2072 6573 6574 ....ERROR: reset 00000070 206E 696D 2066 6169 6C65 6421 2121 0A00 nim failed!!!.. 00000080 5265 7365 7420 7475 6E65 7220 2564 2074 Reset tuner %d t 00000090 696D 6521 2121 0A00 4641 494C 2121 2072 ime!!!..FAIL!! r 000000A0 6567 6973 7465 7220 6361 6C6C 6261 636B egister callback 000000B0 2061 7420 7369 6D20 2564 0A00 6661 7461 at sim %d..fata 000000C0 6C20 6572 726F 7221
notice the two -- before OSDS36_1 -
did anybody ever verify the security chip is really one or just an eeprom with a house number on it?
-
problem has nothing to do with the varistor on the tuner,but thank you for playing.
-
I may try ponyprogrammer to see if it reads the chip.I have to make an interface to the parallel port on the pc with a circuit I built years ago for other sat receivers.A simple design with only 2 diodes and 2 resistors.Much better than the circuits I have seen elsewhere.
-
I now have 2 different versions of s10 and neither work with that firmware,like dr.zin says.
The tuner doesn't work on either s10 and the tv output is pal only,I need not the same color (ntsc) output.
Why the tuner works on some s10 and not others I don't know. -
it must be a partial corruption of the prot ic,with anonymousx firmware all the data on the sys info screen is correct.
With legit firmware popping the tuner out fools the receiver into passing the hardware check of the chip itself,so it
must be looking for either 00 or FF from the prot ic. -
the prot ic has MHD1167 as a chip number.
There are zero ohm resistors going to pins 5 and 6,which can be removed to isolate the chip from the i2c bus. -
supposed to be an old s9 eeprom dump of the section that can be dumped
may be from another brand of receiver and mislabeled as s9 -
searching for the s9 eeprom dump once on the net early this year and a program the will program it.
-
actually that was the reason he made the clone safe firmware,his genuine receiver had a corrupt protection ic and would only boot to --
The device id he talks about is the device id of the protection ic,not the receiver itself.
All the info that shows on the sys info screen is correct,so it must be just the prot ic device id that is corrupt. -
yes u right dear. which s/w has riuned ur tuner. plz seek falshing s/w on net and tried to re-live ur tuner
thanxprog_delcopi_at88sc0204.rar
but I can't download it in my country -
actually it corrupted the protection ic,so now I have to load clone safe firmware for the receiver to work.
-
a quote from anonymousx feb 2012
"my receiver it's a original openbox s10 with a corrupted eeprom so no firmware work old or new .i can see boot and -- on LED display there the receiver hang "
which is what happens after the august beta file. -
try loading old firmware again
-
security chip on the s10
small chip next to the flash chip and processor -
changing the tuner made no difference,so it must be the protection ic corrupt.
The protection chip in my "new" receiver is different.The new receiver is actually an old v1 model (seperate ethernet board instead of on mainboard)
We will have to wait for a fix from anonymousx. -
Having the chip id on the tuner makes no sense,since the tuner is in a socket and can be bought separately from china.
-
the original anonymousx firmware readme said id detection fixed,and when you do the 8888 in sys info it then says m3501id and the id