flshdct problem help please

Include DCT cable boxes and Starchoice boxes.

Moderator: justsomeguy

Locked
aw2walker
Junior Member
Posts: 27
Joined: Sat Jul 17, 2010 8:06 am

flshdct problem help please

Post by aw2walker »

Okay, I understand much more of how this thing works, but here is my problem. I have three dct2224 boxes one was sposed tobe settup for full channle already but put nvram into nvtool shows nonthing on out put tab. Used second nvram from second box and put that one into nvtool still no channels listed under out but mem has alot of different numbers insted of all zeros. The nvram flie from the third box looks just like the supposedly working box under nvtools.

My question is, I know the first box was working when I got it. Why don't I see the number of channels listed in nvtool.

That is the least of my problems right now though as I'm trying to get the flash code on the three box. Here my scenario of what happen when hooking up the third box it had an 0 on it when switch power on. I remove the watch dog c105 from the board did a:

ldram nvram (fist box nvram)
setram nvram
ldram code (first box code.bin file)
flshdct code
(can't remember exact what it said "got code 400000 mbm(something)
program code

I think the steps is right but it took about 20 seconds to erase and when it said "program started or something like that it never move on from there. And when I tried to close USBBDM it ask me to unplug USB device. I did what it ask and power cycled the box. Now the box is stuck on all 8's display and will not power on, I know it's because of the flshdct code was not successfully programed to the box because now when I do a

flschdct code

I get the message about reporting some small hex to usbjat.com.

I have tried several times to get the box back alive. I have use the automatic script function to debrick the box and it says everything is ok for normal programing, so I exited the script and did thing manually.

ldram nvram (the backup from this box this time)
setram nvram (went in just fine)
ldram code (same box backup as above)
flshdct code
firm ware unknow
please report these value.....

I went back into the automated script and ran the type detect script and it says my board is a "Type II", but no firmware testing work on the box as I have tried both.

I think I went wrong when I tried to put nvram and code from a ph7 board which is similar to type I onto a type II board sorry didn't know that much at the time.

How can I fix this box back and how can I clone the ph7 to the type II board.

Sorry, sorry, sorry for the lengthy post just had to get it all out.
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

You need to report which version of software you are using. Last night when I try to help one guy remotely and we spent almost one hour try to setup logmein and failed then use teamviewer and (5 min max for me since I have used too many). Turns out he is using 0.26 which make things very hard to work on.
I assume you are not but just one idea.
You must use the proper command and the flash should work.

"reset 1
"init"

Then flash detect should work. If your RPC is not 468 or 400 then you need to use the script to set them properly.
aw2walker
Junior Member
Posts: 27
Joined: Sat Jul 17, 2010 8:06 am

Sorry, I forgot to mention that

Post by aw2walker »

I'm using USBBDM NT 0.40c.

I know that:

reset 1
init

initialize BDM to turn on at the bottom right coner and is usually on when I stare the restore of nvram, but I think it goes off when I try to set code to he cable box. Will try agin and let you know shortly about the success.

Thanks usbbdm for the help.
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

aw2walker wrote:I'm using USBBDM NT 0.40c.

I know that:

reset 1
init

initialize BDM to turn on at the bottom right coner and is usually on when I stare the restore of nvram, but I think it goes off when I try to set code to he cable box. Will try agin and let you know shortly about the success.

Thanks usbbdm for the help.
DEBUG OFF when doing "prograM" is right.
You can try to use "erase" and "sprogram" and there is not a lot of speed difference but this works when box is bricked. No need to set RPC and A7.
aw2walker
Junior Member
Posts: 27
Joined: Sat Jul 17, 2010 8:06 am

Okay, BDM is off durin the programming

Post by aw2walker »

Okay, USBBDM here is what I put into the BDM NT software:

reset 1
init
ldram nvram
setram nvram
ldram code
flshdct code
program code

and this what I got back from the program.

-reset 1
-R
-init
-ldram nvram
-setram nvram
-ldram code
-flshdct code
Found Address= 00400000 MBM29LV800B
-program code
Erase starts...
Erase time 00:00:32 (.501)
Program Starts...

"Program starts..." is where it just hangs at, it never move on from there. At least flshdct worked this time thank you for direction.
aw2walker
Junior Member
Posts: 27
Joined: Sat Jul 17, 2010 8:06 am

what is the proper code for this step

Post by aw2walker »

usbbdm wrote:DEBUG OFF when doing "prograM" is right.
You can try to use "erase" and "sprogram" and there is not a lot of speed difference but this works when box is bricked. No need to set RPC and A7.
I'm trying it right now and here what I'm doing:

reset 1
init
flshdct code
erase code
sprogram code

this is the output:

-reset 1
-R
-init
-flshdct code
Found Address= 00400000 MBM29LV800B
-erase code
Erase starts...
Erase time 00:00:31 (.243)
-sprogram code
Program Starts...
Program speed 16.12 KB/s
Program time 00:02:10 (.189)
Program pass, if no further programming needed, power off/on the target
-R

Did I do this right?
CAPONE
Junior Member
Posts: 5011
Joined: Sat Dec 27, 2008 3:25 pm

Post by CAPONE »

aw2walker wrote:I'm trying it right now and here what I'm doing:

reset 1
init
flshdct code
erase code
sprogram code

this is the output:

-reset 1
-R
-init
-flshdct code
Found Address= 00400000 MBM29LV800B
-erase code
Erase starts...
Erase time 00:00:31 (.243)
-sprogram code
Program Starts...
Program speed 16.12 KB/s
Program time 00:02:10 (.189)
Program pass, if no further programming needed, power off/on the target
-R

Did I do this right?
For the looks of the output screen Everything seams to be OK. ;)
"If you give a man a fish you feed him for a day. If you teach a man to fish you feed him for a lifetime."
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

aw2walker wrote:I'm trying it right now and here what I'm doing:

reset 1
init
flshdct code
erase code
sprogram code

this is the output:

-reset 1
-R
-init
-flshdct code
Found Address= 00400000 MBM29LV800B
-erase code
Erase starts...
Erase time 00:00:31 (.243)
-sprogram code
Program Starts...
Program speed 16.12 KB/s
Program time 00:02:10 (.189)
Program pass, if no further programming needed, power off/on the target
-R

Did I do this right?
This looks right now.
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

aw2walker wrote:I'm using USBBDM NT 0.40c.

I know that:

reset 1
init

initialize BDM to turn on at the bottom right coner and is usually on when I stare the restore of nvram, but I think it goes off when I try to set code to he cable box. Will try agin and let you know shortly about the success.

Thanks usbbdm for the help.
Your issue was fixed in 0.40d.
Check this in download
0.40d hot patch for BDM programming on old board.
aw2walker
Junior Member
Posts: 27
Joined: Sat Jul 17, 2010 8:06 am

No firm or flipfirm in 0.40d BDM software

Post by aw2walker »

I typed "help" in the USBBDM NT 0.40d software only to find the terms "firm" and "flipfirm" are no longer listed is anyone els have this probrlem.

Also "flshdct" does not seem to work and more for this (type II) board any help on that as well would be appreciated.
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

aw2walker wrote:I typed "help" in the USBBDM NT 0.40d software only to find the terms "firm" and "flipfirm" are no longer listed is anyone els have this probrlem.

Also "flshdct" does not seem to work and more for this (type II) board any help on that as well would be appreciated.
The firm is in dll not the NT software. So make sure you copy the 0.40d to the same directory. Should be c:\Program Files\usbjtag\usbjtagnt

Someone copy to Desktop and THAT WILL NOT WORK. The desktop only holds the shortcut.
Locked

Who is online

Users browsing this forum: No registered users and 7 guests