samhammer
12-13-2005, 05:22 AM
I thought I had posted this before, but it never showed up so i appologize if it shows up twice.
I have a model 6000. Have had it for a long time. Have flashed the eeprom and tsop's many times, so I know that the jtag has always worked.
Last weekend I flashed the IRD with the modded tsop (CNAA). I first flashed a virgin eeprom and let it take the latest update from BEV. When I rounded up a Rom 10 card and set it up with the 102 to rom10 software, I tried the plastic in the IRD. I got the 020 error, so I thought I would re flash the tsops.
Well I cannot get into the memory to flash. When I start fashedit it will always recognize the 6000 and the chip, but will only sometimes get the other information. And everytime when I select the flash programing or eeprom programing button I get the error: "Error reading from the DCUControl register".
I now seems stuck. Does anyone know if BEV has locked the firmware as has been rumored with Dave? Does anyone know how I can get back into my system to reflash?
Thanks
Sam.
I have a model 6000. Have had it for a long time. Have flashed the eeprom and tsop's many times, so I know that the jtag has always worked.
Last weekend I flashed the IRD with the modded tsop (CNAA). I first flashed a virgin eeprom and let it take the latest update from BEV. When I rounded up a Rom 10 card and set it up with the 102 to rom10 software, I tried the plastic in the IRD. I got the 020 error, so I thought I would re flash the tsops.
Well I cannot get into the memory to flash. When I start fashedit it will always recognize the 6000 and the chip, but will only sometimes get the other information. And everytime when I select the flash programing or eeprom programing button I get the error: "Error reading from the DCUControl register".
I now seems stuck. Does anyone know if BEV has locked the firmware as has been rumored with Dave? Does anyone know how I can get back into my system to reflash?
Thanks
Sam.