View Full Version : 301 problem: requires several hours to power up
billko
10-18-2004, 06:59 AM
301.013 single tsop - when plugged in, it won't power up, the green light intermittently flashes on and off. If left alone for several hours, it will finally come to life. What's wrong, and any fix?
billko
10-19-2004, 02:47 AM
Anyone have a thought?
Never jtagged this box before, but tried it today and did not get all info. It recognized the box as a 301, let me backup both tsops and the eeprom, and it did show most of the info, such as the device id, the model id (10E), the software version (P201), and the build cfg. (DAHA). BUT the box keys were just a series of FF FF FF, and the IRD # is R-0000000001-96, and boot strap is XXXX. When connected to the TV, on the menu the location id is not 0000001.
Does this tell you anything about what my problem may be?
Software out dated . you not got ground or have J-tag in wrong way 3 ground pin go to front . use jkeys 301-10C. JCK7
301 P2.29, 9/03/2004 updated
8/19/2004 P2.26,
billko
10-19-2004, 04:37 AM
Thanks, tried it again with jkeys 301-10C and it jtagged perfectly. Now how to fix the power on problem?
skinerd
10-19-2004, 06:37 AM
Thanks, tried it again with jkeys 301-10C and it jtagged perfectly. Now how to fix the power on problem?
The problem you described above sounds like a corrupted TSOP. Erase SA49 and let it stream a while, maybe 30 mins, if that don't get it you'll prolly need to reflash the tsop.
billko
10-19-2004, 07:01 AM
Thanks for the advice. On the 301.013, reflashing requires a vid mod, right?
IF hardware ID DAHA > DAHJ UP need vid mod and bootstrap 16xx or less don't need vid mod. > 17xx up need vid mod
billko
10-19-2004, 06:31 PM
Thank you, thank you! Mine is DAHA 16ab, so I can reflash with no vid mod, right? Well, it says DAHA in jkeys, but there is a stamp on the board that says DAHD. I suppose jkeys is correct?
301.013 single tsop - when plugged in, it won't power up, the green light intermittently flashes on and off. If left alone for several hours, it will finally come to life. What's wrong, and any fix?
Never jtagged this box before, but tried it today and did not get all info. It recognized the box as a 301, let me backup both tsops
Im confused is it a single or duel tstop? :)
skinerd
10-19-2004, 06:57 PM
IF hardware ID DAHA > DAHJ UP need vid mod and bootstrap 16xx or less don't need vid mod. > 17xx up need vid mod
For a complete reflash ALL -013 receivers require a vid mod.
Your comment only applies to the need to zero out 7FFFFFAC, on DAHA the vid mod is not neeeded as that is already 0000. But to completely reflash a vid mod will be needed.
skinerd
10-19-2004, 07:02 PM
Never jtagged this box before, but tried it today and did not get all info. It recognized the box as a 301, let me backup both tsops
Im confused is it a single or duel tstop? :)
DAHA will be a single tsop -013.
DAHD is the eeprom, DAHA is the tsop.
billko
10-19-2004, 07:07 PM
@skinerd - Thanks for the warning! Can any portion be safely flashed w/o a vid mod? What about the eeprom? And is there any way to test the tsop/eeprom before reflashing? Maybe they are OK.
@Rax - Make sure you use jkeys version 301-10C, I had the same problem with an older version. Some 301.013s have two 2 meg tsop chips and others (most?) have one 4 meg chip, you need to look inside your box. Search for 301 guide for helpful pictures.
skinerd
10-19-2004, 07:21 PM
@skinerd - Thanks for the warning! Can any portion be safely flashed w/o a vid mod? What about the eeprom? And is there any way to test the tsop/eeprom before reflashing? Maybe they are OK.
@Rax - Make sure you use jkeys version 301-10C, I had the same problem with an older version. Some 301.013s have two 2 meg tsop chips and others (most?) have one 4 meg chip, you need to look inside your box. Search for 301 guide for helpful pictures.
All but the last sector can be flashed without vid mod.
The eeprom does not need the vid mod, totally seperate chip.
Best way to test is to replace the tsop file with a known good one, it that works, you found the problem.
The eeprom can be replaced with a virgin one made with flashedit.
DAHA and up are single tsop versions.
The only dual tsops I have ever seem were all DACA(D) but I'm sure there must be others too.
billko
10-19-2004, 08:01 PM
Thanks, skinerd.
"Best way to test is to replace the tsop file with a known good one, it that works, you found the problem." But with a 301.013 you can't replace the tsop file without a vid mod, which requires a level of soldering ability I don't have. And we're not even sure that the current tsop file is bad.
I have back-ups, guess I'll try a new eeprom file and see if that helps. Can I erase all but the last sector of the tsop file and then flash the backup?
LOOK at bootstrap see what says 16XXOR 17XX. IF 16 xx you use blue card . can you use blue card.JCK7
billko
10-19-2004, 09:49 PM
I've always been able to use blue card. The problem is that the IRD won't power up (at least not unless it sits for several hours), see my original post in this thread.
Roy4450
10-20-2004, 01:05 AM
Thanks, tried it again with jkeys 301-10C and it jtagged perfectly. Now how to fix the power on problem?
Where did you fnd Jtag 301-10c. I did not see it in the files section. This may fix a problem I am having Jtagging a 301-010.
billko
10-20-2004, 04:16 AM
@Roy4450 - Echostar Files, no. 46
@skinerd, JCK7, anybody - Any other ideas? How about my idea of erasing all but the final section?
Roy4450
10-20-2004, 05:48 AM
Thanks a heap Billko
skinerd
10-20-2004, 06:54 AM
@Roy4450 - Echostar Files, no. 46
@skinerd, JCK7, anybody - Any other ideas? How about my idea of erasing all but the final section?
Try it and see......you will get an error trying to flash but ignore it......
billko
10-20-2004, 07:54 AM
Guess I've got nothing to lose, I'll try it. Does the software version need to be exact? P201 is on the box. My backup is a P200, and there's a P202 in the download section, but no P201.
skinerd
10-20-2004, 08:29 AM
either 200 or 202 should get it going, if that is the problem.
billko
10-20-2004, 09:07 AM
OK, I'll try and let you know.
And just to make certain, when you say that the "last sector" is the one that requires a vid mod for writing, you mean SA66 (7FFFC000-80000000)??? I erase everything except SA66, then program the backup and ignore the error message, right?
By the way, yesterday when I jtagged the 301 I saved a copy of the tsop file, and today I ran this copy through flashedit and the crc box was red. Does this indicate that the tsop is corrupt? My older backup of P200 and the P202 from the public dump read with green crc.
skinerd
10-20-2004, 10:16 AM
Just do a full erase, the last sector won't erase, then reflash, you'll get an error towards the end, just ignore, then try restreaming the receiver. You can always flash back to where you were.
billko
10-23-2004, 05:15 AM
OK, finally got the nerve to try it, but perhaps it was a mistake. I erased with no problem, then applied the new tsop file. As you said, near the end I got an error message (at 0x7ffef1f6). Now, the jtag won't show IRD#, box keys, build cfg, or boot strap. The box is now totally dead, won't power up, no lights at all. Restreaming had no effect.
What now?
skinerd
10-23-2004, 07:43 AM
Reflash it back with your backup , the flash file that came from the receiver before you started.
I think the problem is the fact you have a STM29W chip, with only 67 sectors(0-66), where the AMD chip has 71 (0-70), so the last sectors are different sizes. Looks like a vid mod will be required, unless you can find some one with a STM29W chip that has a firmware backup., there is no way to tell where the flash file came from either, so who ever you get it from will just have to know it's from a ST flash.
skinerd
10-23-2004, 07:54 AM
Feeling lucky??
I just checked and I have a virgin P055 DAHA file from a 301-013 with a M29W320DT flash chip............
PM me an e-mail addy I'll send it.
billko
10-23-2004, 05:00 PM
Thanks, you have pm. I may try the Bob11 vid mod, seems easier, only 2 wires to solder. Any thoughts on an alternative location for "the spot"? In the resurrection guide sticky, lexar suggested R62 and other locations that may be easier to solder. What about SW4 reset? It appears to have continuity to the original spot.
skinerd
10-23-2004, 06:12 PM
Thanks, you have pm. I may try the Bob11 vid mod, seems easier, only 2 wires to solder. Any thoughts on an alternative location for "the spot"? In the resurrection guide sticky, lexar suggested R62 and other locations that may be easier to solder. What about SW4 reset? It appears to have continuity to the original spot.
I have never traced the "spot" to see where else would be an easier location to solder to, I am sure there must be tho. I have no problem soldering to the spot, I use 30 ga wire and it just slips right into the tiny hole there. If I get some time later, I will trace the sopt to where it comes from and post any easier locations to solder to.
billko
10-23-2004, 11:20 PM
First the good news: Did the Bob11 vid mod and it worked like a charm the very first time (can't imagine why anyone would want to use the regulator, which requires drilling holes, the purchase of parts, and much more soldering). The P202 firmware loaded 100%.
Now the bad news: I'm back to where I started, with the green light intermittently flashing on and off. Guess it was not a software problem after all.
Any further thoughts?
billko
10-24-2004, 05:30 PM
I guess it must be some sort of hardware problem.
Skinerd, anybody, is there anything else to try, or id it time to give up?
skinerd
10-24-2004, 06:38 PM
Did you let it stream up to p204?
billko
10-25-2004, 02:51 AM
Can't take the update because it won't power up, green light flashes intermittently on and off, nothing on screen.
skinerd
10-25-2004, 03:21 AM
Could be a loose solder joint, don't know, I'll look at it for you if you want.
billko
10-25-2004, 04:07 AM
Thanks, u have pm.
billko
10-26-2004, 03:03 AM
I wanted to check the voltage at key points before sending it to you. Is there any list of what voltage should be at various points on the board? There's 3.2 volts at SB35, which I believe is normal. BUT at the sat input, I'm getting a constant 13.5 volts. In the past, it would bounce back and forth from 13.5 to 18.5 volts. Is this a clue to a possible problem?
billko
10-26-2004, 05:56 PM
Left it on all night and it's still a constant 13.5v at sat input, I've got to believe there is some connection between this and the failure to power up. Is 18v needed for anything other than the lnb?
billko
10-27-2004, 09:52 PM
Skinerd, you have a pm from me.
out14w
10-27-2004, 11:53 PM
bilko where is this bob11 vidmod ive been doing the drilling and the last 2 i attempted didnt make it lol?
billko
10-28-2004, 02:21 AM
Echostar Files section, http://www.dssftp.com/filedownload/generate_php/echostar__files.php
number 45.
skinerd
10-28-2004, 02:44 AM
Left it on all night and it's still a constant 13.5v at sat input, I've got to believe there is some connection between this and the failure to power up. Is 18v needed for anything other than the lnb?
Bouncing between 13 and 18 v is only going to happen when it is searching for a signal, once found it will stay at 13 or 18.
billko
10-28-2004, 03:10 AM
Yes, but no antenna is attached, so it could not find a signal.
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.