PDA

View Full Version : dead 510


ynot-try
08-26-2004, 01:44 AM
just got a 510 prv came with jtag installed no vid mod or OJ1 mod. Unit sold as not powering up, no lights, but i was getting some info so i installed the vid mod and OJ1 now when i try reading the unit with switch in normal use i get

error reading from ird(DCU peek)

When i switch it over and restart unit i get

Device ID 0x1d405041
Device STI5518mvb-x


no ird info any help on getting this unit working would be helpful hard drive has been resized to 80 gig

skinerd
08-26-2004, 02:07 AM
OJ1 is for sure connected?

If it is just try rebooting the receievr, and let it sit for a minute or so before opening jkeys.

If it continues to balk, maybe the guy that put the jtag smoked the flashes or DCU part of the CPU and dumped the receiver.

ynot-try
08-26-2004, 09:50 AM
I only get the dcu error if i do not flick the switch once the vid mod is turned on and OJ1 jumper is made i get the other information.

Would using flashedit to made a new flash 2 with boxkeys and idr info help me get this started? and if the DCU part of the cpu meeds reflashing how do i do it?

ynot-try
08-26-2004, 11:14 AM
update with jkey open i select 508 get r000000001 for ird number and FFFFFFFFFF for boxkeys so i go to flash programming erase both flashs 3 times made a dump file in flashedit and attemp to write to flash 2 but get this error at 20% error programming flash at offset 0x7cd0012 but i can flash a eeprom 100%

skinerd
08-26-2004, 01:37 PM
update with jkey open i select 508 get r000000001 for ird number and FFFFFFFFFF for boxkeys so i go to flash programming erase both flashs 3 times made a dump file in flashedit and attemp to write to flash 2 but get this error at 20% error programming flash at offset 0x7cd0012 but i can flash a eeprom 100%


Don't try to write to flash #1, erase both and write ONLY to flash #2, flash #1 is just a mirror of 2 and you will not be able, or need, to flash it.

ynot-try
08-26-2004, 04:04 PM
Cant seem to get past the 20% mark when programming U7 without getting the same error