View Full Version : Dcu Peek Error!!!!
ebang
12-12-2005, 01:33 AM
HELP. I added a vidmod to my 301-13 and now I can't get rid of the dcu peek error...I have tried everything...can anyone help?
Fordkiller
12-12-2005, 01:50 AM
ground r79 left side pad with reciver front to you
Did you ground R79 before you went to Flash Program?
ebang
12-12-2005, 04:57 PM
I grounded R79 to the case and still same error
ebang
12-12-2005, 05:15 PM
Hi Guys along with this issue I have a 2700 with a lock installed that I can't program, any suggestions on this?
cricketball
12-12-2005, 10:21 PM
Hi Guys along with this issue I have a 2700 with a lock installed that I can't program, any suggestions on this?
What error are you getting trying to program it?
driveclean
12-12-2005, 10:26 PM
HELP. I added a vidmod to my 301-13 and now I can't get rid of the dcu peek error...I have tried everything...can anyone help?
Make sure the vid mod is active during jtagging. Make sure vid mod circuit is complete as in no opens.
skinerd
12-13-2005, 01:04 AM
Vid mod has nothing to do with dcu peek errors, it's a link mode issue, grounding R79 usually fixes it.
ebang, are you using the same jtag on the 2700 that you used on the 301.013?? If you are , then that jtag has issues. Check all the wiring connections on the jtag ,especially the ground. your either getting bad conection, when connecting to the ird or a bad ground. just do a good continuity check on the jtag. I have had that dcu peek issue a few times and alot other people have to. do those checks and get back to us on the results..
ebang
12-13-2005, 05:44 AM
ok..I am using the same buffered Jtag with both receivers, I grounded R79 and I am still getting the DCU error on the 301-13 with the 2700 I just can get to programming, I will get back to post the exact error for that issue, Skinerd what do you mean by a "link mode issue"? oh...by the way I have used the jtag fine on a 301-10 4900 and 3900, as well before I added the Vidmod I did not get the DCU Peek error I just couldn't write to the protected sector of the TSOP.
#40Fan
12-13-2005, 05:52 AM
Try grounding R79 to someplace on the mother board. Usually there is a place with a white circle that has two spots in it. One will have a + next to it, the other is a good place to ground.
skinerd
12-13-2005, 08:12 AM
Much as I hate to admit it........I actually found Wall2 to help with DCU peek errors....
If jkeys continually errors with DCU peek, close jkeys, open wall2, DON'T do anything in wall2, just open it, then close it after it gives you some wrong info error, then reopen jkeys.....DCU peek should not happen if you are in link mode, ie R79 grounded or OJ1 jumped which ever is the case.
Try it and post your results......
It has to do with how each one initializes the DCU, wall2 does it differently than jkeys, it sets it up then jkeys can take over.
ebang
12-13-2005, 04:32 PM
I tried that with no luck, what is OJ1 jumped?
with the 2700 getting error jkeys does not rocognize info
Texas Trophy
12-14-2005, 06:49 AM
This problem drove me nuts on 1 of my 301s. What I noticed different was that the 1 I was having the DCU Peak errors on didn't have a 3 wire power cord ie...power, ground, neutral. You think that the R79 is grounded, but it really isn't because there is nothing actually grounding the case. I got a 3 wire power cord and attached it to the receiver and I have never had the DCU Peak error since. If you want, I can post some pictures.
ebang
12-15-2005, 12:23 AM
sure, some pis would be good
dakazman
12-15-2005, 06:58 AM
Again ground like this.
Texas Trophy
12-15-2005, 09:52 AM
sure, some pis would be good
Here ya go.
ebang
12-16-2005, 02:12 AM
I will try the three wire thing and post the results
You need to ground R79 to the board ground. I just erased and programmed 3 --301.013's today and one of them gave me that DCU peek error while programming. I just closed out jkeys checked the r79 to gnd. to make sure it was a good connection which it was. Unplugged the ird and plugged it back in , fired up jkeys and erased 3 times and reprogrammed the new tsop. no problem this time..
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.