[DBOX-II] DBox2 voor Sat: kein system

Jan Ambers · 3 maart 2006

Zitten d'er settings in een image?

Ik heb nu nogmaals de flashing gedaan, en "Flashing done! " staat op de LCD debox-2

Dus ik mag aannemen dat alles ok is?

Ik start opnieuw op:

Mr Pano

U boot 1.1.4

autoboot;

Loading kernel;

Blijft staan...

Opnieuw reset: Betaresearch

Da's toch onlogisch of ie is geflashed of niet?

Welke flash is nu de "goeie" ( die die het bij mij doet natuurlijk maar welke???)?

Unetwork · 3 maart 2006

Er is denk ik toch wat mis gegaan met de debug!

Ik zou eens goed gaan lezen in het debug verhaal te vinden hier en op de Duitse boards.

Of de boot file vernieuwen ook is hier een sticly over.

Na het flashen kan je ook de netwerk kabel er uit doen om te kijken of de box dan wel doorstart.

ricow · 6 maart 2006

als ik alles zo lees zou ik toch maar eens proberen om met een serieele nulmodem kabel te flashen.

als ik het goed begrijp is er geen bootloader aanwezig.

als die er niet is kun je volgens mij ook niet met netwerk flashen alleen serieel(nulmodemkabel)

groeten,

Ricow

Unetwork · 6 maart 2006

Dus de bijlage gebruiken in de sticky hierboven PPCBOOT en dan gaan flashen met Dbox II boot manager.

Suc6

Jan Ambers · 6 maart 2006

Al meermaals gedaan no sukses!

Ik kan 'm soms flashen maar de fouten blijven en "flashing done" verschijnt, dan bij de volgende pwrup: blijft hangen "loading kernel"!

Boot: Bmon-v1.2

DRG · 6 maart 2006

ik mis in je hele verhaal, ook via pm of je nou de debug procedure al eens opnieuw uitgevoerd hebt

Jan Ambers · 7 maart 2006

Ik heb 'm 2x geflashed na elkaar, eens met UTPcross+Nulmodem, een keer met UTPcross, hier de comminucatie:

debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

'debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: BMon V1.2 mID 01

debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

&debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: BMon V1.2 mID 01

debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

&debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: BMon V1.2 mID 01

debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

&debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: BMon V1.2 mID 01

&debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: BMon V1.2 mID 01

&debug: DDF: Calibrating delay loop... &debug: DDF: Calibrating delay loop... de

bug: DDF: 4163.4294557775 BogoMIPS

debug: BMon V1.2 mID 01

&debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: BMon V1.2 mID 01

debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

debug: DDF: Calibrating delay loop... debug: DDF: 4163.4294557775 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

debug: DDF: Calibrating dela&debug: DDF: Calibrating delay loop... debug: DDF: 6

7.79 BogoMIPS

debug: BMon V1.2 mID 01

debug: 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-1a.f8.82.07.00.00-95

debug: HWrev 09 FPrev 0.81

debug: B/Ex/Fl(MB) 32/00/08

debug: 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-1a.f8.82.07.00.00-95

debug: HWrev 09 FPrev 0.81

debug: B/Ex/Fl(MB) 32/00/08

debug: 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-1a.f8.82.07.00.00-95

debug: HWrev 09 FPrev 0.81

debug: B/Ex/Fl(MB) 32/00/08

debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

debug: 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-1a.f8.82.07.00.00-95

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.168.1, My IP 192.168.168.2

debug: Sending TFTP-request for file C/Satelliet/Nokia-dbox2/dBox2-Bootmanager/P

pcboot

will verify ELF image, start= 0x800000, size= 222280

verify sig: 262

boot net: boot file has no valid signature

Branching to 0x40000

ppcboot 0.6.4 (Jul 12 2001 - 02:51:28)

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-50-9c-44-2c-7d

FLASH: 8 MB

FB logo at: none

Input: serial

Output: serial

Any key druecken um das Flashing abzubrechen.. : 0

LCD driver (KS0713) initialized

Logo FlashingBOOTP broadcast 1

TFTP from server 192.168.168.1; our IP address is 192.168.168.2

Filename '/tftpboot/flash.img'.

Load address: 0x100000

Loading: #####################debug: 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-1a.f8.82.07.00.00-95

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.168.1, My IP 192.168.168.2

debug: Sending TFTP-request for file C/Satelliet/Nokia-dbox2/dBox2-Bootmanager/P

pcboot

will verify ELF image, start= 0x800000, size= 222280

verify sig: 262

boot net: boot file has no valid signature

Branching to 0x40000

ppcboot 0.6.4 (Jul 12 2001 - 02:51:28)

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-50-9c-44-2c-7d

FLASH: 8 MB

FB logo at: none

Input: serial

Output: serial

Any key druecken um das Flashing abzubrechen.. : 0

LCD driver (KS0713) initialized

Logo FlashingBOOTP broadcast 1

TFTP from server 192.168.168.1; our IP address is 192.168.168.2

Filename '/tftpboot/flash.img'.

Load address: 0x100000

Loading: ###############################debug: DDF: Calibrating delay loop... de

bug: DDF: 67.79 BogoMIPS

debug: WATCHDOG RESET

debug: BMon V1.2 mID 01

debug: feID dd gtxID 0b

debug: fpID 5a dsID 01-1a.f8.82.07.00.00-95

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.168.1, My IP 192.168.168.2

debug: Sending TFTP-request for file C/Satelliet/Nokia-dbox2/dBox2-Bootmanager/P

pcboot

will verify ELF image, start= 0x800000, size= 222280

verify sig: 262

boot net: boot file has no valid signature

Branching to 0x40000

ppcboot 0.6.4 (Jul 12 2001 - 02:51:28)

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-50-9c-44-2c-7d

FLASH: 8 MB

FB logo at: none

Input: serial

Output: serial

Any key druecken um das Flashing abzubrechen.. : 0

LCD driver (KS0713) initialized

Logo FlashingBOOTP broadcast 1

TFTP from server 192.168.168.1; our IP address is 192.168.168.2

Filename '/tftpboot/flash.img'.

Load address: 0x100000

Loading: #######################################################################

################################################################################

######################

done

lo: 0x100000unprotecting 4

[10001]-> [0] [s800080] unprotecting 5

[10001]-> [0] [s800080] unprotecting 6

[10001]-> [0] [s800080] unprotecting 7

[10001]-> [0] [s800080] unprotecting 8

[10001]-> [0] [s800080] unprotecting 9

[10001]-> [0] [s800080] unprotecting a

[10001]-> [0] [s800080] unprotecting b

[10001]-> [0] [s800080] unprotecting c

[10001]-> [0] [s800080] unprotecting d

[10001]-> [0] [s800080] unprotecting e

[10001]-> [0] [s800080] unprotecting f

[10001]-> [0] [s800080] unprotecting 10

[10001]-> [0] [s800080] unprotecting 11

[10001]-> [0] [s800080] unprotecting 12

[10001]-> [0] [s800080] unprotecting 13

[10001]-> [0] [s800080] unprotecting 14

[10001]-> [0] [s800080] unprotecting 15

[10001]-> [0] [s800080] unprotecting 16

[10001]-> [0] [s800080] unprotecting 17

[10001]-> [0] [s800080] unprotecting 18

[10001]-> [0] [s800080] unprotecting 19

[10001]-> [0] [s800080] unprotecting 1a

[10001]-> [0] [s800080] unprotecting 1b

[10001]-> [0] [s800080] unprotecting 1c

[10001]-> [0] [s800080] unprotecting 1d

[10001]-> [0] [s800080] unprotecting 1e

[10001]-> [0] [s800080] unprotecting 1f

[10001]-> [0] [s800080] unprotecting 20

[10001]-> [0] [s800080] unprotecting 21

[10001]-> [0] [s800080] unprotecting 22

[10001]-> [0] [s800080] unprotecting 23

[10001]-> [0] [s800080] unprotecting 24

[10001]-> [0] [s800080] unprotecting 25

[10001]-> [0] [s800080] unprotecting 26

[10001]-> [0] [s800080] unprotecting 27

[10001]-> [0] [s800080] unprotecting 28

[10001]-> [0] [s800080] unprotecting 29

[10001]-> [0] [s800080] unprotecting 2a

[10001]-> [0] [s800080] unprotecting 2b

[10001]-> [0] [s800080] unprotecting 2c

[10001]-> [0] [s800080] unprotecting 2d

[10001]-> [0] [s800080] unprotecting 2e

[10001]-> [0] [s800080] unprotecting 2f

[10001]-> [0] [s800080] unprotecting 30

[10001]-> [0] [s800080] unprotecting 31

[10001]-> [0] [s800080] unprotecting 32

[10001]-> [0] [s800080] unprotecting 33

[10001]-> [0] [s800080] unprotecting 34

[10001]-> [0] [s800080] unprotecting 35

[10001]-> [0] [s800080] unprotecting 36

[10001]-> [0] [s800080] unprotecting 37

[10001]-> [0] [s800080] unprotecting 38

[10001]-> [0] [s800080] unprotecting 39

[10001]-> [0] [s800080] unprotecting 3a

[10001]-> [0] [s800080] unprotecting 3b

[10001]-> [0] [s800080] unprotecting 3c

[10001]-> [0] [s800080] unprotecting 3d

[10001]-> [0] [s800080] unprotecting 3e

[10001]-> [0] [s800080] unprotecting 3f

[10001]-> [0] [s800080] unprotecting 40

[10001]-> [0] [s800080] unprotecting 41

[10001]-> [0] [s800080] unprotecting 42

[10001]-> [0] [s800080] Un-Protected 63 sectors

Erase Flash from 0x10020000 to 0x107fffff

sector 66 .... done

Erased 63 sectors

Copy to Flash... done

LCD driver (KS0713) initialized

Logo Flashing done !

dbox2-ppcboot>

=====================================================================

Ohne nullmodemkabel:

====================

***Adapter Desc: Realtek 8139-series PCI NIC (via IpHlpApi #0)

***MAC address: 00:E0:4C:F0:61:97 Local IP: 192.168.168.1

***BootP server started... Port 67

***TFTP server started... Port 69

BootP> Request from 00:50:9C:44:2C:7D (assuming that this is DBox).

BootP> Created dynamic ARP entry for DBoxIP 192.168.168.2 with MAC 00:50:9C:44:2C:7D

BootP> Answer sent!

TFTP> Started TFTP-Transfer for "C:\Satelliet\Nokia-dbox2\dBox2-Bootmanager\Ppcboot"...

TFTP> Transfer finished, sent 435 blocks

BootP> Created dynamic ARP entry for DBoxIP 192.168.168.2 with MAC 00:50:9C:44:2C:7D

BootP> Answer sent!

TFTP> Non-BootP TFTP-transfer requested "\tftpboot\flash.img"

TFTP> Started TFTP-Transfer for "\tftpboot\flash.img"...

BootP> Created dynamic ARP entry for DBoxIP 192.168.168.2 with MAC 00:50:9C:44:2C:7D

BootP> Answer sent!

TFTP> Started TFTP-Transfer for "C:\Satelliet\Nokia-dbox2\dBox2-Bootmanager\Ppcboot"...

TFTP> Transfer finished, sent 435 blocks

BootP> Created dynamic ARP entry for DBoxIP 192.168.168.2 with MAC 00:50:9C:44:2C:7D

BootP> Answer sent!

TFTP> Non-BootP TFTP-transfer requested "\tftpboot\flash.img"

TFTP> Started TFTP-Transfer for "\tftpboot\flash.img"...

TFTP> Transfer finished, sent 16129 blocks

====================================

Een keer opgestart dat ik o.a. camd3 en Das Ertse gezien heb, daarna alleen maar ne meer Betaresearch... en geen opstart meer in debugmode!

Hij moet toch wel degelijk in debug gestaan hebben want anders kon ik die niet flashen, of ben ik verkeerd?

Een hij gedebuged is start ie toch elke keer in debugmode op of ben ik terug verkeerd?

-= [ Appien ] =- · 7 maart 2006

Het kan zijn dat het geheugen rot is, teminste, die meldingen die voorbij komen geven me niet echt een fris gevoel... <img src="/forums/images/graemlins/frown.gif" alt="" />

Jan Ambers · 7 maart 2006

Bedoel je dat: DRAM: (faked) 32 MB

Dat verontrust me ook: boot net: boot file has no valid signature

Het is wel nen heksentoer om dat ding in debug te krijgen, en die reageert ook niet normaal op PijlUp

Gelet op dat randomeffekt denk ik ook aan hardware problemen, maar kan nog niet zeggen ik welke richting.

Jan Ambers · 8 april 2006

Probleem opgelost, een baan onderbroken op de print en een geheugenchip vervangen...

Nu zit er de NG Neutrino in en Camd en Cam3d en alles loopt perfekt!

Waar is een uitleg te vinden hoe die Neutrino werkt en wat zijn mogelijkheden zijn?

Inloggen

[DBOX-II] DBox2 voor Sat: kein system

Aanbevolen berichten

Jan Ambers

Beste reacties in dit onderwerp

Populaire dagen

Beste reacties in dit onderwerp

Populaire dagen

Unetwork

ricow

Unetwork

Jan Ambers

DRG

Jan Ambers

-= [ Appien ] =-

Jan Ambers

Jan Ambers

Maak een account aan of log in om te reageren

Account aanmaken

Inloggen

Wie is er online 0 leden

Overig

Activiteit