Dead 3100

[flipster69]

I have a BEV 3100-10 Build Config EAED Software Version E430 with a TSOP Lock and it was working fine until it got ECM'd with Location ID0001. I was wondering why it got hit by the ECM so I opened the Box and found one of the 6 wires on the TSOP Lock had come off, so I soldered it back on. I didn't have a JTag Cable then so I tried the "Junkyard Fix" - Short Pin 16 to Ground on IC23 to try and erase the TSOP. Ever since then I haven't been able to power up the receiver. I now have a JTag Cable, so I uninstalled the TSOP Lock, repaired the cut trace, got a supposedly good TSOP Dump from somebody, put my Boxkeys and IRD No. in via FlashEdit 2 and flashed with Wall 2 and it said successful but it still won't power up. I tried JKeys 2.9.9 But it keeps giving me the same error "The flash codes returned are not recognized By JKeys. Mfg/Device codes returned are 0/1000 (JEDEC) & 408/1000 (Flash File)". IRD and Box Keys are reading a bunch of 0s. Is my 3100 Toast? I got a Quad Mode Universal JTAG and I am connecting the 7 Pins starting from Pad 0. Could this be my problem? It almost looks like I am not writing to the TSOP! Does anybody have a picture of how to hook up the above JTag to this Receiver. Although the source of the saved TSOP flashes swears that they are for Build Config EAED like mine, FlashEdit reads it as EAEA! Could this be the problem as well? Any help would be really appreciated.

[OneHwyMan]

My success with the Wall is limited,I prefer to use jkeys and a simple jtag.Solder the baby on,plug in the ird and program the tsop,do flash 2 first then flash 1,then eeprom,erase that one and put on a new one.
After all that check your boxkeys,all should be well
then plug it in and wait,light should flash a few times then go out and blink some more
After this you should be in business..
Good luck
OHM

[flipster69]

OneHwyMan

Where do I find the EEPROM file for this receiver? Also, when I solder, do I solder all seven pins on the one side and should I start at Pad 0 like I was doing without soldering it? Is there a diagram that shows exactly how to attach a JTag to a 3100-10?
Thanks for your help!

[OneHwyMan]

Try this.The ird shown is that of a 2700 so the pads are diff.Will try to find a pic of a 3100

[OneHwyMan]

Can't find a pic so see what I did for Parity in the JTag Problem post.

Desperate times call for desparate measures....lmao


OHM:D

[flipster69]

OneHwyMan

I soldered Pogo Pin Extensions to the my JTag Pads then plugged my Universal Quad JTag Cable to it and successfully read and saved both flashes (U22-U23). I then read them in FlashEdit 2.0 and they both showed my BoxKeys and IRD Nos. and Build Configs properly. All of these I did through Wall 2.0. What I don't understand is why JKeys won't work at all! It keeps saying no device detected! Still the IRD won't power up. I even did the first 60000 bytes of U23. No matter what I do, when I plug in the IRD I don't get a green light even momentarily. My JTag Pad has 16 connections. My JTag Cable has 7 Pins and 3 Pins for Ground. What I did was attach the 1st Pin to Pad ) then the rest of the Pins are 1 to 6 consecutively. It almost looks like the IRD is not booting up!

[OneHwyMan]

your boot sequences are in the U23 part of the tsop,if it did not do a good write then ird won't boot up and it will also give you that warning that you are getting in Jkeys.
When writing to the tsop,you have to write U23 first,then U22.
Try using the Wall program to erase both tsops (a couple of times) and then Using Jkeys to write U23,thenU22,if you can read keys now,then we will assume your jtag is connected correctly.
If you think that your tsops are bad then download a good one and edit in your info onto it.

let me know the results.

OHM

p.s. Not to mention that the jtag you are using is not buffered,now i'm not saying that this is bad,but sometimes the write is not that good and you have to do it again,where as a buffered jtag always gives a good write.I use a non-buffered simple jtag and it will work 9 times out of 10.But it also has given me bad writes too.
I also have a quad-mode but i use that only for 2700(don't have a steady hand to hold on a 3100 for that long of time):)

[DTVismybitch]

I am having this very same problem with my DP-301.005. J-keys sais that the JEDEC and FLASH are FFFF,Box Keys are all 000's and so is receiver ID. I have tried WALL but it is erasing flashes in not even a second, I imagine that it is not working properly because all the info i have been reading sais that it takes a minute or 2. It will write to TSOP but itstill doe snot work. what i mean by not working is that the LED does not come on ever and no picture at all. Any help is appreciated, I have almost given up. Thanks.

[OneHwyMan]

When you go to the flash programming and select your model does it identify you chip at least.If your flash is erased,it won't be able to read anything.Go to flash programming and try selecting your model of ird and it should at least acknowledge the tsop.If it does.Go staight to programming U22 and U23.

Hope it works out for you. Let us know what happens (warnings,errors etc) and if it worked out.



OHM

[DTVismybitch]

When i go to flash programming it sais "The flash codes returned are not recognized by J-Keys. MFG device codes returned are FFFF/FFFF (JEDEC) and FFFF/FFFF (Flash file)". J-keys doesdetect it as a 301/3100 but I get this message when i click on "fash programming". I was able to save the 2 flashes with J-keys, but they were automaicaly named R 000000000 1 and 2, meaning they are saved but blank, I think. I cannot access the "chip/sector programming" at all. When I use WALL I try to erase the flashes and it tells me it will take a couple of minutes to do so but it takes less than a second to do it. WALL will let me program to it but that doesn't work either. I do not have the original TSOP, but I have som replacments that have edited. This receiver had a TSOP lock on it that was faulty and it was hit by an ECM, which is why it got put into this state. I am lost as to wat to do next. Any idea why it won't let me pogram to it or erase form it, but it will let me save. Weird.

[OneHwyMan]

Well first,repair the lock or remove it all together my guess woukd be you got a bad read because of it,and the problem now most likely.It may have not even been installed correctly(as it did fail).
Lets eliminate that problem and work our way up.

Repair or remove lock and repair trace then try to program ird again.Let me know what happens.

OHM:D

[DTVismybitch]

Just wondering where teh trace was that you are asking me to repair? This receive is not mine it is a friends, he told me to play with it and see if i can fix it. So that is what i am doing. I asked about doing exactly what you told me to do,repair the TSOP lock, but 2 other sites said not to because it will make it harder andscrew it up even more. However, i was thinking exactly what you said, wouldn't repairing the trace bridge the gap type idea to the TSOP. Let me know where to repair the trace please. Thanks.