Bilder wechseln

Wie blitze ich ein Bild - Permanent Outgoing Incomes
rmaerte1
Semiprofi
Semiprofi
Beiträge: 1293
Registriert: Montag 21. Januar 2002, 23:27

Bilder wechseln

Beitrag von rmaerte1 »

Hallo,

wollte eben mal das "logo-fb" wechseln.
Vorgehensweise:

1) Normales 1.5er Basisimage flashen
2) cramfs hinterher
3) Sender suchen
4) Image auslesen
5) Image mit "Tuxboxflashtools" bearbeiten (logo ausgetauscht)
6) dieses Image wieder geflashed

Beim Booten der Box kommt:
debug: DDF: Calibrating delay loop... debug: DDF: 66.76 BogoMIPS
debug: BMon V1.0 mID 03
debug: feID 00 enxID 03
debug: fpID 52 dsID 01-1a.96.8a.07.00.00-3a
debug: HWrev 41 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
File /root/platform/sagem-dbox2/kernel/os not found: No such file or directory
boot flash /root/platform/sagem-dbox2/kernel/os failed

Flash-FS bootstrap loader (v1.5)

Found Flash-FS superblock version 3.1
File /root/platform/mpc8xx-dbox2/kernel/os not found: No such file or directory
boot flash /root/platform/mpc8xx-dbox2/kernel/os failed

Flash-FS bootstrap loader (v1.5)

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

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


ppcboot 0.6.4 (Mar 2 2002 - 20:44:32)

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-39-30-19
FLASH: 8 MB
LCD driver (KS0713) initialized
LCD logo at: 0x8F049 (0x1E00 bytes)
FB logo at: 0x90E71 (0x199AD bytes)
AVIA Frambuffer
Input: serial
Output: serial


1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select (1-3), other keys to stop autoboot: 0
...............................................................
Un-Protected 63 sectors
Kernel image at: 0x10020034 (0x8EFED bytes)
## Booting Linux kernel at 10020034 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 585645 Bytes = 571 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.19-pre8-dbox2 (von alexW) (gcc version 3.0.4) #16 Son Mai 19 1
9:32:22 UTC 2002
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: ro root=1f03 console=ttyS0
WARNING: Frequency is not in HZ. Please consider using a newer bootloader!
WARNING: OLD intfreq = 66 busfreq = 66
WARNING: NEW intfreq = 66000000 busfreq = 66000000
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: 30920k available (1032k kernel code, 352k data, 64k 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.12 (20020219) 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:39:30:19
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
Amd/Fujitsu Extended Query Table v1.1 at 0x0040
number of CFI chips: 1
Creating 7 MTD partitions on "D-Box 2 flash memory":
0x00000000-0x00020000 : "BR bootloader"
0x00020000-0x000c0000 : "idxfs (kernel, logos)"
0x000c0000-0x00160000 : "var (jffs2)"
0x00160000-0x00760000 : "root (cramfs)"
0x00760000-0x00800000 : "flfs (ppcboot)"
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: 64k init
init started: BusyBox v0.61.pre (2002.04.02-22:55+0000) multi-cajffs2_scan_eras
eblock(): Magic bitmask 0x1985 not found at 0x0000a81c: 0x01b7 instead
Inode #5 was a directory with children - removing those too...
Inode #6 was a directory with children - removing those too...
Inode #8 was a directory with children - removing those too...
mount: Mounting ramfs on /var/tmp failed: No such file or directory
Update altes Baseimage...
#####################################################
# #
# ZU ALTES BASEIMAGE, BITTE V1.5 INSTALLIEREN!! #
# #
#####################################################

The system is going down NOW !!
Sending SIGTERM to all processes.
Sending SIGKILL to all processes.
open: No such file or directory
The system is halted. Press CTRL-ALT-DEL or turn off power
System halt
Was ist das denn? Habe schon so oft Bilder gewechselt.
Zu sagen ist noch, dass ich testhalber das 1.6er vorher drauf hatte. Kann es damit zusammenhängen??
Ich geh bald am Stock ;)
chkdesign
Senior Member
Beiträge: 1544
Registriert: Freitag 12. Oktober 2001, 00:00

Beitrag von chkdesign »

Du darfst nur das idxfs beim 1.5er mit den FlashTools bearbeiten:

Schau mal da:
http://www.chatlogin.com/dbox2/chkdesig ... ?p=147#147
Bild
rmaerte1
Semiprofi
Semiprofi
Beiträge: 1293
Registriert: Montag 21. Januar 2002, 23:27

Beitrag von rmaerte1 »

das mach ich ja. Fakt ist, ich hatte vorher die 1.6er drauf, und denke, dass es damit zu tun hat! Trotz neuem Aufspielen der 1.5er kommen im Bootmanager seltsame Bemerkungen wie: "Basisimage zu alt, mind. 1.5!!" Ich habe das richtige Basisimage drauf!