zu früh gefreut!! sagem hängt sich auf!?

Wie blitze ich ein Bild - Permanent Outgoing Incomes
someone11111
Einsteiger
Einsteiger
Beiträge: 131
Registriert: Mittwoch 9. Oktober 2002, 23:01

zu früh gefreut!! sagem hängt sich auf!?

Beitrag von someone11111 »

tja nun habe ich das eine problem behobven und dann kommt auch schon das andere!! mit dem flashen geht nun alles glatt aber wenn ich die box neu starten will kommt dieses log:



debug: DDF: Calibrating delay loop... debug: DDF: 66.76 BogoMIPS
debug: BMon V1.2 mID 03
debug: feID 00 enxID 03
debug: fpID 52 dsID 01-93.4d.bb.07.00.00-af
debug: HWrev 21 FPrev 0.23
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: Given up BOOTP/TFTP boot
boot net failed

Flash-FS bootstrap loader (v1.5)

Found Flash-FS superblock version 3.1
Found file /root/platform/sagem-dbox2/kernel/os in Flash-FS
debug: Got Block #0052

will verify ELF image, start= 0x800000, size= 203620
verify sig: 262
Branching to 0x40000


PPCBoot 1.1.6 (TuxBox) (Mar 13 2003 - 12:09:31)

CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Watchdog enabled
Board: DBOX2, Sagem
I2C: ready
DRAM: 32 MB
FLASH: 8 MB
Scanning JFFS2 FS: done.
find_inode failed for name=tuxbox
load: Failed to find inode
LCD: Scanning JFFS2 FS: done.
find_inode failed for name=tuxbox
load: Failed to find inode
ready - can't find logo in flash
FB: Scanning JFFS2 FS: done.
find_inode failed for name=tuxbox
load: Failed to find inode
can't find logo in flash - no init
In: serial
Out: serial
Err: serial

Options:
1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select (1-3), other keys to stop autoboot: 0
### FS (cramfs) loading 'vmlinuz' to 0x100000
### FS LOAD ERROR<ffffffff> for vmlinuz!
=>
DieMade
Oberlamer, Administrator & Supernanny
Beiträge: 10532
Registriert: Samstag 13. Juli 2002, 10:49

Beitrag von DieMade »

Hmmm, da sind bestimmt noch mehr Kontakte am Flash nicht OK.

Mal komplett sichten und ggf. nachlöten.
There are 10 types of people in the world: those who know binary and those who don't
someone11111
Einsteiger
Einsteiger
Beiträge: 131
Registriert: Mittwoch 9. Oktober 2002, 23:01

Beitrag von someone11111 »

jetzt is die frage... pin 14 und 16 .. sind diese belegt?? oder kann mir einer sagen welche von allen pins belegt sind und welche nicht???? damit ich überhaupt weiss welche ich prüfen muss und welche nicht?! irgendwie sieht die box sowieso schon ziemlich sch*** aus!! genau gegenüber ist auch noch ein pin.. da war wohl auch schon einer dran! (ist das pin 42?)
DieMade
Oberlamer, Administrator & Supernanny
Beiträge: 10532
Registriert: Samstag 13. Juli 2002, 10:49

Beitrag von DieMade »

Also Intel hat sicher nicht aus purer Langeweile 56 Pins an den Flash "geklebt" - die sollten ALLE sauber Kontakt haben.

OB das Pin 42 ist? Seh ich Deinen Flash? Du kannst das sicher besser abzählen ;)

Grobe Schema-Zeichnung zum Abzählen:

Code: Alles auswählen

 56..............................29
 | | | | | | | | | | | | | | | | |
+-------------------------------+
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
|                               |
| O                             |
|                               |
+-------------------------------+
 | | | | | | | | | | | | | | | | |
 1...............................28
someone11111
Einsteiger
Einsteiger
Beiträge: 131
Registriert: Mittwoch 9. Oktober 2002, 23:01

Beitrag von someone11111 »

da hast du wohl recht!! aber bei manchen sieht man keine leiterbahnen abgehen .. na gut jetzt ist noch die frage wieviel lagen hat die platine.. aber egal.. es ist übrigens pin 43 der rotz aussieht! ich werde mich jetz gleich ma ranmachen und alles nachlöten... hoffentlich geht das gut!?! :-?
someone11111
Einsteiger
Einsteiger
Beiträge: 131
Registriert: Mittwoch 9. Oktober 2002, 23:01

Beitrag von someone11111 »

nu ma des komplette log: war vorhin irgendwie nich dran?!



debug: DDF: Calibrating delay loop... debug: DDF: 66.76 BogoMIPS
debug: BMon V1.2 mID 03
debug: feID 00 enxID 03
debug: fpID 52 dsID 01-93.4d.bb.07.00.00-af
debug: HWrev 21 FPrev 0.23
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: Given up BOOTP/TFTP boot
boot net failed

Flash-FS bootstrap loader (v1.5)

Found Flash-FS superblock version 3.1
Found file /root/platform/sagem-dbox2/kernel/os in Flash-FS
debug: Got Block #0052

will verify ELF image, start= 0x800000, size= 203620
verify sig: 262
Branching to 0x40000


PPCBoot 1.1.6 (TuxBox) (Mar 13 2003 - 12:09:31)

CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Watchdog enabled
Board: DBOX2, Sagem
I2C: ready
DRAM: 32 MB
FLASH: 8 MB
Scanning JFFS2 FS: . done.
LCD: ready
FB: loading - ready
In: serial
Out: serial
Err: serial

Options:
1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select (1-3), other keys to stop autoboot: 0
### FS (cramfs) loading 'vmlinuz' to 0x100000
### FS load compleate: 571677 bytes loaded to 0x100000
## Booting image at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 571613 Bytes = 558 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.20-dbox2 (von alexW) Wer Kernels nachmacht, oder faelscht, wir
d bestraft ;-) #1 Son Apr 13 14:50:18 CEST 2003
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 console=ttyS0
Decrementer Frequency = 247500000/60
mpc8xx-wdt: active wdt found (SWTC: 0xFFFF, SWP: 0x1)
mpc8xx-wdt: keep-alive trigger activated (PITC: 0x2000)
Console: colour dummy device 80x25
Calibrating delay loop... 65.74 BogoMIPS
Memory: 30964k available (996k kernel code, 348k data, 60k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis Communications
AB.
i2c-core.o: i2c core module
CPM UART driver version 0.03
ttyS00 at 0x0280 is a SMC
ttyS01 at 0x0380 is a SMC
pty: 256 Unix98 ptys configured
eth0: CPM ENET Version 0.2 on SCC2, 00:50:9c:32:b7:82
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
CFI: Found no D-Box 2 flash memory device at location zero
cfi_cmdset_0001: Erase suspend on write enabled
Using buffer write method
Creating 6 MTD partitions on "D-Box 2 flash memory":
0x00000000-0x00020000 : "BR bootloader"
0x00020000-0x00040000 : "flfs (ppcboot)"
0x00040000-0x00720000 : "root (cramfs)"
0x00720000-0x00800000 : "var (jffs2)"
0x00020000-0x00800000 : "flash without bootloader"
0x00000000-0x00800000 : "complete flash"
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (cramfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 60k init
init started: BusyBox v0.61.pre (2003.04.09-05:48+0000) multi-caUsing /lib/modu
les/2.4.20-dbox2/misc/i2c-8xx.o
[i2c-8xx]: mpc 8xx i2c init
i2c-core.o: adapter registered as adapter 0.
[i2c-8xx]: adapter: 0
Using /lib/modules/2.4.20-dbox2/misc/info.o
i2c-core.o: driver FOR_PROBE_ONLY registered.
i2c-core.o: driver unregistered: FOR_PROBE_ONLY
Using /lib/modules/2.4.20-dbox2/misc/event.o
event: init ...
Using /lib/modules/2.4.20-dbox2/misc/fp.o
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 0
).
[1] 19
Using /lib/modules/2.4.20-dbox2/misc/lcd.o
lcd.o: init lcd driver module
lcd.o: found KS0713/SED153X lcd interface on 3
[lcdip] Bootmanager IP gefunden.
[lcdip] Unmounting jffs2... success
debug: DDF: Calibrating delay loop... debug: DDF: 66.76 BogoMIPS
debug: BMon V1.2 mID 03
debug: feID 00 enxID 03
debug: fpID 52 dsID 01-93.4d.bb.07.00.00-af
debug: HWrev 21 FPrev 0.23
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: Given up BOOTP/TFTP boot
boot net failed

Flash-FS bootstrap loader (v1.5)

Found Flash-FS superblock version 3.1
Found file /root/platform/sagem-dbox2/kernel/os in Flash-FS
debug: Got Block #0052

will verify ELF image, start= 0x800000, size= 203620
verify sig: 262
Branching to 0x40000


PPCBoot 1.1.6 (TuxBox) (Mar 13 2003 - 12:09:31)

CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Watchdog enabled
Board: DBOX2, Sagem
I2C: ready
DRAM: 32 MB
FLASH: 8 MB
Scanning JFFS2 FS: done.
find_inode failed for name=tuxbox
load: Failed to find inode
LCD: Scanning JFFS2 FS: done.
find_inode failed for name=tuxbox
load: Failed to find inode
ready - can't find logo in flash
FB: Scanning JFFS2 FS: done.
find_inode failed for name=tuxbox
load: Failed to find inode
can't find logo in flash - no init
In: serial
Out: serial
Err: serial

Options:
1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select (1-3), other keys to stop autoboot: 0
### FS (cramfs) loading 'vmlinuz' to 0x100000
### FS LOAD ERROR<ffffffff> for vmlinuz!
=>
debug: DDF: Calibrating delay loop... debug: DDF: 66.76 BogoMIPS
debug: BMon V1.2 mID 03
debug: feID 00 enxID 03
debug: fpID 52 dsID 01-93.4d.bb.07.00.00-af
debug: HWrev 21 FPrev 0.23
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: Given up BOOTP/TFTP boot
boot net failed

Flash-FS bootstrap loader (v1.5)

Found Flash-FS superblock version 3.1
Found file /root/platform/sagem-dbox2/kernel/os in Flash-FS
debug: Got Block #0052

will verify ELF image, start= 0x800000, size= 203620
verify sig: 262
Branching to 0x40000


PPCBoot 1.1.6 (TuxBox) (Mar 13 2003 - 12:09:31)

CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Watchdog enabled
Board: DBOX2, Sagem
I2C: ready
DRAM: 32 MB
FLASH: 8 MB
Scanning JFFS2 FS: done.
find_inode failed for name=tuxbox
load: Failed to find inode
LCD: Scanning JFFS2 FS: done.
find_inode failed for name=tuxbox
load: Failed to find inode
ready - can't find logo in flash
FB: Scanning JFFS2 FS: done.
find_inode failed for name=tuxbox
load: Failed to find inode
can't find logo in flash - no init
In: serial
Out: serial
Err: serial

Options:
1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select (1-3), other keys to stop autoboot: 0
### FS (cramfs) loading 'vmlinuz' to 0x100000
### FS LOAD ERROR<ffffffff> for vmlinuz!
=>