recover a Dreambox dm500
-
- Junior Member
- Posts: 12
- Joined: Sun Jul 25, 2010 1:58 am
recover a Dreambox dm500
i have a dm500(dreambox) and my bootloader is corrupted.
i want to restore it and i hooked up usbjtag.
when i press detect i get the following.
-detect
IDCODE 12955049
Manufacturer not found 024
The flash chip is.
E28F640J3
i want to restore it and i hooked up usbjtag.
when i press detect i get the following.
-detect
IDCODE 12955049
Manufacturer not found 024
The flash chip is.
E28F640J3
-
- Junior Member
- Posts: 8974
- Joined: Mon Jul 18, 2005 9:33 pm
Please do not do anything yet. I will add DM500 supprt soon. Hope on 0.52. However, like the conexant support your hardware ID has to be 4000 and higher. Once DM500 is supported I will upload the youtube like recently I did for Sonicview, Nano 2, Viewsat and XV3300.alcatel wrote:i have a dm500(dreambox) and my bootloader is corrupted.
i want to restore it and i hooked up usbjtag.
when i press detect i get the following.
-detect
IDCODE 12955049
Manufacturer not found 024
The flash chip is.
E28F640J3
DM500 uses Power PC and new development needs to be done. Keep watching the news forum.
-
- Junior Member
- Posts: 8974
- Joined: Mon Jul 18, 2005 9:33 pm
DM500 almost ready.
I can read and program DM500 and soon will release 0.53. There are some questions.
1. Where is the boot? The current flash map is from 0xff800000 and size 0x800000. I do not see the 0xff800000 is the start of the boot.
2. Other program's backup seems to have the byte swapped. Which means when you load the backup from other program you need to swap the byte (hilo). I only see 132KB of the boot. Should I add the hilo byte swap in the software?
Only slow programming is implemented, the read speed is about 53KB/s. The programming speed is about 24-25KB/s (Intel J28F640). Program entire 8M needs about 5-6 minutes. I could add another programming method which can at least double the programming speed. But I think this is going to be good enough to start.
1. Where is the boot? The current flash map is from 0xff800000 and size 0x800000. I do not see the 0xff800000 is the start of the boot.
2. Other program's backup seems to have the byte swapped. Which means when you load the backup from other program you need to swap the byte (hilo). I only see 132KB of the boot. Should I add the hilo byte swap in the software?
Only slow programming is implemented, the read speed is about 53KB/s. The programming speed is about 24-25KB/s (Intel J28F640). Program entire 8M needs about 5-6 minutes. I could add another programming method which can at least double the programming speed. But I think this is going to be good enough to start.
-
- Junior Member
- Posts: 12
- Joined: Sun Jul 25, 2010 1:58 am
Hi.
I don't have this info,i did find this.
root@dreambox:~> cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "DreamBOX cramfs+squashfs"
mtd1: 002c0000 00020000 "DreamBOX jffs2"
mtd2: 00040000 00020000 "DreamBOX OpenBIOS"
mtd3: 007c0000 00020000 "DreamBOX (w/o bootloader)"
mtd4: 00800000 00020000 "DreamBOX (w/ bootloader)"
mtd5: 003e0000 00020000 "DreamBOX SquashedFS"
mtd6: 00120000 00020000 "DreamBOX Cramfs"
I don't know if this is what you need.
I also found these files,this is the way you can recover using a lpt-jtag method.
it also included files like a bootloader and a working image.
maybe usefull to compare.
http://www.mediafire.com/?i7b0vcm2mjde48o
I don't have this info,i did find this.
root@dreambox:~> cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "DreamBOX cramfs+squashfs"
mtd1: 002c0000 00020000 "DreamBOX jffs2"
mtd2: 00040000 00020000 "DreamBOX OpenBIOS"
mtd3: 007c0000 00020000 "DreamBOX (w/o bootloader)"
mtd4: 00800000 00020000 "DreamBOX (w/ bootloader)"
mtd5: 003e0000 00020000 "DreamBOX SquashedFS"
mtd6: 00120000 00020000 "DreamBOX Cramfs"
I don't know if this is what you need.
I also found these files,this is the way you can recover using a lpt-jtag method.
it also included files like a bootloader and a working image.
maybe usefull to compare.
http://www.mediafire.com/?i7b0vcm2mjde48o
-
- Junior Member
- Posts: 8974
- Joined: Mon Jul 18, 2005 9:33 pm
-
- Junior Member
- Posts: 5011
- Joined: Sat Dec 27, 2008 3:25 pm
Awsome Boss. Great News Like Always.....usbbdm wrote:OK. I got the point I can kill the box (erase entire flash) then program the boot ( a few seconds) then revive it with DreamUp (That is quite long about 8 minutes).
The box then is up and running.
I will release 0.53 latter. Also fix the side by side issue.
"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."
-
- Junior Member
- Posts: 8974
- Joined: Mon Jul 18, 2005 9:33 pm
If you want to test before I post the pages and video.
Here is some tips.
1. Connect reset pin on NT (pin 11) to Halt pin (pin 11) on the pad. This is important to halt the CPU.
2. The boot is from fffe0000. Size 20000. Just load the right boot
ldram fffe0000
erase fffe0000 20000
sprogram fffe0000 20000
After about 4 seconds. You are ready to use the serial app to revive the DM500. I will most likely upload pages and video tomorrow.
Here is some tips.
1. Connect reset pin on NT (pin 11) to Halt pin (pin 11) on the pad. This is important to halt the CPU.
2. The boot is from fffe0000. Size 20000. Just load the right boot
ldram fffe0000
erase fffe0000 20000
sprogram fffe0000 20000
After about 4 seconds. You are ready to use the serial app to revive the DM500. I will most likely upload pages and video tomorrow.
Who is online
Users browsing this forum: No registered users and 5 guests