box lässt sich nicht flashen

Wie blitze ich ein Bild - Permanent Outgoing Incomes
ufo60
Neugieriger
Neugieriger
Beiträge: 7
Registriert: Montag 5. Juli 2004, 19:02

box lässt sich nicht flashen

Beitrag von ufo60 »

Hallo zusammen,

ich habe günstig eine Nokia Dbox mit 2xI bekommen.
Natürlich ist das Gerät nicht i.O.
Im Display ist ganz schwach "kein System"
zu sehen.
Habe versucht BN2.01 mit dem Dbox bootmanager
zu flashen, das wird aber
nach kurzer Zeit abgebrochen.
Bitte helft mir.

^debug: DDF: Calibrating delay loop... debug: DDF: 67.6debug: BMon V1.2 mID 01
debug: feID 5 gtxID 0b
debug: fpID 4 dsID 01-5a.2debug: HWrev 09 FPrev 0.81
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
debug: &_text 0x55debug: &_end 0x11 , &__stack 0x3f800debug: Memory tests (0x15
5 8debug: NumberTest: debug: passed
debug: MarchTest: debug: passed
debug: PermTest: debug: passed
dbox2:root> boot net
debug:
BOOTP/TFTP bootstrap loader (v0.3)
debug:
debug: Transmitting BOOTP request via broadcast
debug: Got BOOTP reply from Server IP 192.168.0.1, My IP 6
debug: Sending TFTP-request for file C/Programme/DBoxBoot/ppcboot_writeflash
will verify ELF image, start= 0x7e0008, size= 201596 Block #0200
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x3f56


ppcboot 0.6.4 (Apr 11 2002 - 16:10:44)

Initializing...
CPU: PPC823ZTnnB2 at 67 MHz: 2 kB I-Cache 1 kB D-Cache
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-4g-9c-44-24-53
FLASH: 8 MB
LCD driver (KS0713) initialized
BOOTP broadcast 1
TFTP from server 18c.168.0.1; our IP address is 18c.168.0.2
Filename 'C/Programme/tftpboot/logo-lcd'.
Load address: 0x10d55@
Loading: #
done
LCD logo at: 0x130000 (0x1F9FFC0 bytes)
BOOTP broadcast 1
TFTP from server 18c.168.0.1; our IP address is 18c.168.0.2
Filename 'C/Programme/tftpboot/logo-fb'.
Load address: 0x11e00
Loading: ####
done
FB logo at: 0x0 (0x1FC0000 bytes)
AVIA Frambuffer
Input: serial
Output: serial


1: Console on ttyS0
2: Console on null
3: Console on framebuffer
Select (1-3), other keys to stop autoboot: 0
dbox2-ppcboot> bootp 100000 /C/BN2.01/BN2.01.img
BOOTP broadcast 1
TFTP from server 6.168.0.1; our IP address is 18c.168.0.2
Filename '/C/BN2.01/BN2.01.img'.
Load address: 0xfe00
Loading: #######################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
##################################################
done

dbox2-ppcboot> protect off 10020000 107fffff
...............................................................
Un-Protected 63 sectors

dbox2-ppcboot> erase 10020000 107fffff
Bus Fault @ 0x01fc3c50, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f9790Unknown values in msr
Bus Fault @ 0x01fc3c50, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f9f598 Machine check signal - probably due to mm fa
ult
with mmu off
Bus Fault @ 0x01fc3c50, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f9f230 Machine check signal - probably due to mm fa
ult
with mmu off
Bus Fault @ 0x01fc3c50, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f9eec8 Machine check signal - probably due to mm fa
ult
with mmu off
Bus Fault @ 0x01fc3c50, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f9435Machine check signal - probably due to mm faul
t
with mmu off
Bus Fault @ 0x01fc3c4g, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f9e48o Machine check signal - probably due to mm fa
ult
with mmu off
Bus Fault @ 0x01fc3c4g, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01fdebug: DDF: Calibrating delay loop... debug: DDF:
67.79 BogoMIPS
debug: WATCHDOG RESET
debug: BMon V1.2 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-5a.30.81.07.00.00-74
debug: HWrev 09 FPrev 0.81
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
dbox2:root> debug:
BOOTP/TFTP bootstrap loader (v0.3)
debug:
debug: Transmitting BOOTP request via broadcast
debug: Got BOOTP reply from Server IP 192.168.0.1, My IP 192.168.0.2
debug: Sending TFTP-request for file C/Programme/DBoxBoot/ppcboot_writeflash
will verify ELF image, start= 0x7d800A, size= 201596
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x3f55


ppcboot 0.6.4 (Apr 11 2002 - 16:10:44)

Initializing...
CPU: PPC823ZTnnB2 at 67 MHz: 2 kB I-Cache 1 kB D-Cache
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-4g-9c-44-24-53
FLASH: 8 MB
LCD driver (KS0713) initialized
BOOTP broadcast 1
TFTP from server 18c.168.0.1; our IP address is 18c.168.0.2
Filename 'C/Programme/tftpboot/logo-lcd'.
Load address: 0x10d55@
Loading: #
done
Bus Fault @ 0x01fc144S, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): Bus Fault @ 0x01fc3c50, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f94dgMachine check signal - probably due to mm faul
t
with mmu off
Bus Fault @ 0x01fc3c50, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f9eaa0 Machine check signal - probably due to mm fa
ult
with mmu off
Bus Fault @ 0x01fc3c4g, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f9e738 Machine check signal - probably due to mm fa
ult
with mmu off
Bus Fault @ 0x01fc3c4g, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f943cMachine check signal - probably due to mm faul
t
with mmu off
Bus Fault @ 0x01fc3c4g, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f9e040 Machine check signal - probably due to mm fa
ult
with mmu off
Bus Fault @ 0x01fc3c4g, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 01f9550Machine check signal - probably due to mm faul
t
with mmu off
Bus Fault @ 0x01fc3c4g, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): Bus Fault @ 0x01fc3c4g, fixup 0x00000000
Machine check in kernel mode.
Causeddebug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: WATCHDOG RESET
debug: BMon V1.2 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-5a.30.81.07.00.00-74
debug: HWrev 09 FPrev 0.81
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
dbox2:root> debug:
BOOTP/TFTP bootstrap loader (v0.3)
debug:
debug: Transmitting BOOTP request via broadcast
debug: Got BOOTP reply from Server IP 192.168.0.1, My IP 18c.168.0.2
debug: Sending TFTP-request for file C/Programme/DBoxBoot/ppcboot_writeflash
will verify ELF image, start= 0x7d600H, size= 201596
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x155


ppcboot 0.6.4 (Apr 11 2002 - 16:10:44)

Initializing...
CPU: PPC823ZTnnB2 at 67 MHz: 2 kB I-Cache 1 kB D-Cache
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) w MB
Ethernet: 00-4g-1-44-053
FLASH: 8 MB
LCD driver (KS0713) initialized
BOOTP broadcast 1
TFTP from server 18c.168.0.1; our IP address is 18c.168.0.2
Filename 'C/Programme/tftpboot/logo-lcd'.
Load address: 0x1055@
Loading: #
done
DieMade
Oberlamer, Administrator & Supernanny
Beiträge: 10532
Registriert: Samstag 13. Juli 2002, 10:49

Beitrag von DieMade »

debug: BMon V1.2 mID 01
debug: feID 5 gtxID 0b
debug: fpID 4 dsID 01-5a.2debug: HWrev 09 FPrev 0.81
Schon in der BMon-Anzeige stimmt fast nix, das riecht nach defekter CPU :-?
There are 10 types of people in the world: those who know binary and those who don't
ufo60
Neugieriger
Neugieriger
Beiträge: 7
Registriert: Montag 5. Juli 2004, 19:02

box lässt sich nicht flashen

Beitrag von ufo60 »

@DieMade

ist das sicher?
Jener,von dem ich die Box habe, hatte
die Vermutung das ein Speicher defekt
wäre.
Diesen auszuwechseln wäre kein Problem...
aber die CPU - autsch!!
DieMade
Oberlamer, Administrator & Supernanny
Beiträge: 10532
Registriert: Samstag 13. Juli 2002, 10:49

Beitrag von DieMade »

das riecht nach defekter CPU
Von "zu 100% ganz ganz bestimmt sicher" steht da nix, eine Ferndiagnose ist nicht genauer zu stellen.
There are 10 types of people in the world: those who know binary and those who don't
ufo60
Neugieriger
Neugieriger
Beiträge: 7
Registriert: Montag 5. Juli 2004, 19:02

Beitrag von ufo60 »

o.k.
danke erst mal!!!