nokia awaria

Question

dibox ciagle sie restartuje prubuje wgrac nowe image ifa i to samo w czasie wgrywania czy cos padlo?

byk · Accepted Answer

nie piszesz nic jak doszło do awarii.
część softu ładuje ci się poprawnie, czyli połączenie, sieciówka w dbox i procek jest OK

Quote:
debug: Sending TFTP-request for file C/PROGRAM FILES/DBOXBOOT/ppcboot_writeflash

will verify ELF image, start= 0x800000, size= 201596
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000

" boot file has no valid signature"
tu masz przyczynę problemów.
co bym zrobił na twoim miejscu:
-wymienił plik ppcboot_writeflash,
-sprawdził lub wybrał inne image do wgrania
-sprawdził ustawienia programu -czy nie próbujesz wgrać "image z bootem" -(complete flash) a plik masz bez boota -(flash without bootloader) lub też odwrotnie
-spróbował wgrać nowego boota do dbox2
jeżeli to nie pomoże to pozostaje tylko wymiana pamięci flash (możesz zastukać na PW)

byk · Answer

rozumiem że chodzi ci o dbox2.
opisz jak do tego doszło.
spróbuj wgrac inne image- to co próbujesz wgrac może być uszkodzone,
spróbuj wgrać image bootmenagerem (ifa jest graficzna nakładka na bootmenagera i czasami są z nia problemy) pamiętraj że musisz zmienic nazwę pliku na 13.img
jak dalej będą problemy ,podaj komunikaty z okna bootmenagera -może byc uszkodzona pamięć flash! a tu już tylko wymiana pamięci

belzebiusz 1 · Answer

Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-50-9c-13-a9-50
FLASH: 8 MB
LCD driver (KS0713) initialized
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
done
LCD logo at: 0x130000 (0x1F9FFC0 bytes)
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/logo-fb'.
Load address: 0x120000
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-debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-92.bb.02.07.00.00-a0
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 16/16/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.1.100, My IP 192.168.1.101
debug: Sending TFTP-request for file C/PROGRAM FILES/DBOXBOOT/ppcboot_writeflash

will verify ELF image, start= 0x800000, size= 201596
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000

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

Initializing...
CPU: PPC823ZTnnA at 67 MHz: 2 kB I-Cache 1 kB D-Cache
*** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-50-9c-13-a9-50
FLASH: 8 MB
LCD driver (KS0713) initialized
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
done
LCD logo at: 0x130000 (0x1F9FFC0 bytes)
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/logo-fb'.
Load address: 0x120000
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
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/kernel-cdk'.
Load address: 0x100000
Loading: T T T T T T T T T
Retry count exceeded; starting again
debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: WATCHDOG RESET
debug: BMon V1.0 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-92.bb.02.07.00.00-a0
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 16/16/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.1.100, My IP 192.168.1.101
debug: Sending TFTP-request for file C/PROGRAM FILES/DBOXBOOT/ppcboot_writeflash

will verify ELF image, start= 0x800000, size= 201596
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000

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

Initializing...
CPU: PPC823ZTnnA at 67 MHz: 2 kB I-Cache 1 kB D-Cache
*** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-50-9c-13-a9-50
FLASH: 8 MB
LCD driver (KS0713) initialized
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
done
LCD logo at: 0x130000 (0x1F9FFC0 bytes)
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/logo-fb'.
Load address: 0x120000
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
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/kernel-cdk'.
Load address: 0x100000
Loading: T T debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: WATCHDOG RESET
debug: BMon V1.0 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-92.bb.02.07.00.00-a0
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 16/16/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.1.100, My IP 192.168.1.101
debug: Sending TFTP-request for file C/PROGRAM FILES/DBOXBOOT/ppcboot_writeflash

will verify ELF image, start= 0x800000, size= 201596
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000

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

Initializing...
CPU: PPC823ZTnnA at 67 MHz: 2 kB I-Cache 1 kB D-Cache
*** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-50-9c-13-a9-50
FLASH: 8 MB
LCD driver (KS0713) initialized
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
done
LCD logo at: 0x130000 (0x1F9FFC0 bytes)
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/logo-fb'.
Load address: 0x120000
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
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/kernel-cdk'.
Load address: 0x100000
Loading: debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: WATCHDOG RESET
debug: BMon V1.0 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-92.bb.02.07.00.00-a0
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 16/16/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.1.100, My IP 192.168.1.101
debug: Sending TFTP-request for file C/PROGRAM FILES/DBOXBOOT/ppcboot_writeflash

will verify ELF image, start= 0x800000, size= 201596
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000

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

Initializing...
CPU: PPC823ZTnnA at 67 MHz: 2 kB I-Cache 1 kB D-Cache
*** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-50-9c-13-a9-50
FLASH: 8 MB
LCD driver (KS0713) initialized
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
done
LCD logo at: 0x130000 (0x1F9FFC0 bytes)
BOOTP broadcast 1
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'C/PROGRAM FILES/tftpboot/logo-fb'.
Load address: 0x120000
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: 1 debug: DDF: Calibrating delay loop
... debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS

debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: WATCHDOG RESET
debug: BMon V1.0 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-92.bb.02.07.00.00-a0
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 16/16/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.1.100, My IP 192.168.1.101
debug: Sending TFTP-request for file C/PROGRAM FILES/DBOXBOOT/ppcboot_writeflash

will verify ELF image, start= 0x800000, size= 201596
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000

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

Initializing...
CPU: PPC823ZTnnA at 67 MHz: 2 kB I-Cache 1 kB D-Cache
**
debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-92.bb.02.07.00.00-a0
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 16/16/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.1.100, My IP 192.168.1.101
debug: Sending TFTP-request for file C/PROGRAM FILES/DBOXBOOT/ppcboot_writeflash

debug: Got Block #0050 byla wlaczona i nagle restart i zawias

kecaj60 · Answer

Jak wgrać boota do Dbox2 i?Proszę o instrukcję i pkliki.

belkow · Answer

@kecaj60,też mieszkam w Lublinie, jeżeli masz nadal problem z dboxem to proponuję kontakt osobisty. Może potrafię Ci pomóc.Belkow