ich bekomme folgende fehlermeldung wenn ich mir das hunter image bzw. das alexw1.6.2. image flashen will. Kann mir jemand was zu den Logs sagen? Habe ich ein Flash defekt.
BTW: Das 1.6 Baseimage bekomme ich auch nicht ans laufen. Das einzige was lüppt ist ein YADD-System.
==============HUNTERLOG================
lcddclient: connect: Stale NFS file handle
controldclient: connect: Stale NFS file handle
debug: DDF: Calibrating delay loop... debug: DDF: 66.76 BogoMIPS
debug: BMon V1.1 mID 03
debug: feID 00 enxID 03
debug: fpID 52 dsID 01-cb.ef.86.07.00.00-45
debug: HWrev 01 FPrev 0.23
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
debug: &_text 0x10000, &_etext 0x26ec0, &_data 0x26ec0, &_edata 0x2a9bc
debug: &_end 0x35944, &__stack 0x400000
debug: Memory tests (0x400000 -- 0x2000000)
debug: NumberTest: debug: passed
debug: MarchTest: debug: passed
debug: PermTest: debug: passed
dbox2:root> boot
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.23
debug: Sending TFTP-request for file C/Programme/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: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-50-9c-31-1f-e0
FLASH: 8 MB
LCD driver (KS0713) initialized
BOOTP broadcast 1
TFTP from server 192.168.0.1; our IP address is 192.168.0.23
Filename 'C/Programme/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
LCD logo at: 0x130000 (0x1F9FFC0 bytes)
BOOTP broadcast 1
TFTP from server 192.168.0.1; our IP address is 192.168.0.23
Filename 'C/Programme/tftpboot/logo-fb'.
Load address: 0x120000
Loading: #########
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 120000 /C/dbox2/images/Hunter_V04_2xI.img
BOOTP broadcast 1
TFTP from server 192.168.0.1; our IP address is 192.168.0.23
Filename '/C/dbox2/images/Hunter_V04_2xI.img'.
Load address: 0x120000
Loading: #######################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
######################
dbox2-ppcboot> protect off 10020000 107fffff
...............................................................
Un-Protected 63 sectors
dbox2-ppcboot> erase 10020000 107fffff
Erase Flash from 0x10020000 to 0x107fffff
..........................
Erased 63 sectors
dbox2-ppcboot> cp.l 120000 10020000 1F8000
Copy to Flash... Flash not Erased
dbox2-ppcboot>
============ENDLOG===============
============BASEIMAGE1.6.2==========
Un-Protected 63 sectors
### FS (cramfs) loading 'vmlinuz' to 0x100000
### FS load compleate: 547317 bytes loaded to 0x100000
## Booting image at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 547253 Bytes = 534 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.19 (von alexW) Wer Kernels nachmacht, oder faelscht, wird best
raft ;-) #1 Son Aug 4 10:58:46 CEST 2002
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.53 BogoMIPS
Memory: 30916k available (1028k kernel code, 364k 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.12a (20020514) 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:31:1f:e0
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
Amd/Fujitsu Extended Query Table v1.1 at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling fast programming due to code brokenness.
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"
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 2048)
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
console=/dev/console
init started: BusyBox v0.61.pre (2002.08.18-16:06+0000) multi-caStarting pid 9,
console /dev/console: '/etc/init.d/rcS'
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0003fff4: 0xffff in
stead
Using /lib/modules/2.4.19/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.19/misc/info.o
i2c-core.o: driver FOR_PROBE_ONLY registered.
i2c-core.o: driver unregistered: FOR_PROBE_ONLY
Using /lib/modules/2.4.19/misc/event.o
event: init ...
Using /lib/modules/2.4.19/misc/input.o
Using /lib/modules/2.4.19/misc/fp.o
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 0
).
Using /lib/modules/2.4.19/misc/lcd.o
lcd.o: init lcd driver module
lcd.o: found KS0713/SED153X lcd interface on 3
[lcdip] Bootmanager IP gefunden.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Internal flash device timeout occured or write operation was performed while fla
sh was programming.
Warning: DQ5 raised while program operation was in progress, however operation c
ompleted OK
Waiting for write to complete timed out in do_write_oneword.Scheduling in interr
upt
kernel BUG at sched.c:566!
Oops: Kernel Mode Software FPU Emulation, sig: 8
NIP: C000DA08 XER: 00000000 LR: C000DA08 SP: C1D3FF10 REGS: c1d3fe60 TRAP: 1000
Not tainted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c1d3e000[23] 'lcdip' Last syscall: 4
last math 00000000 last altivec 00000000
GPR00: C000DA08 C1D3FF10 C1D3E000 0000001B 00001032 00000001 00000001 C1F81060
GPR08: 00003391 C011D43C 00000000 C1D3FE30 0000000D 1001EBD4 00000000 00000000
GPR16: 00000000 00000000 00000000 00000000 00009032 01D3FF40 00000000 C0004634
GPR24: C00043A0 00000006 005A9000 7FFFF868 3EEC448C 00000400 00000000 C1D3FF10
Call backtrace:
C000DA08 C0004650 10004058 10003724 0FE3DC70 00000000
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
<0>Rebooting in 180 seconds..