From: Harry J M. <hj...@ec...> - 2008-08-20 10:31:31
|
On Tue, 19 Aug 2008, Chuck Randall wrote: > I just reflashed my connex-400xm with a newly built gumstix-basic- > image. Now I get a "bad magic number" when I try to boot it. What > could have gone wrong? The log of the reflash procedure is show below. [snip] > GUM> fatload mmc 1 a20000000 rootfs > GUM> cp.b a20000000 40000 ${filesize} Too many zeros here. The correct address is a2000000 (6 zeros). -- | Harry Mason | .------------. | .___, |"Whatever you do will be | | University of | | hjm200 @ | | ___('v')___ | insignificant. However, | | Southampton | | zepler.net | | `"-\._./-"' | it is vitally important | | England | '------------' | hjm ^ ^ | that you do it." Gandhi | |
From: Harry J M. <hj...@ec...> - 2008-08-20 18:19:13
|
On Wed, 20 Aug 2008, Chuck Randall wrote: > On Aug 20, 2008, at 3:31 AM, Harry J Mason wrote: > >> On Tue, 19 Aug 2008, Chuck Randall wrote: >> >>> I just reflashed my connex-400xm with a newly built gumstix-basic- >>> image. Now I get a "bad magic number" when I try to boot it. What >>> could have gone wrong? The log of the reflash procedure is show >>> below. >> >> [snip] >> >>> GUM> fatload mmc 1 a20000000 rootfs >>> GUM> cp.b a20000000 40000 ${filesize} >> >> Too many zeros here. The correct address is a2000000 (6 zeros). > > Yes, I just noticed that, too. When I use a2000000 I get a bunch of > errors. See the log listing below. > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at > 0x00000000: 0x0f0f id > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at > 0x00000004: 0x0404 id It looks like there's incorrect data instead of a valid jffs2, and the kernel is trying and failing to mount it. Did you reflash the filesystem with the correct address, before you reflashed the kernel? Did you protect on 1:0-1 ; erase all first? Did you flash the correct file from oe/tmp/deploy/glibc/images ? -- | Harry Mason | .------------. | .___, |"Whatever you do will be | | University of | | hjm200 @ | | ___('v')___ | insignificant. However, | | Southampton | | zepler.net | | `"-\._./-"' | it is vitally important | | England | '------------' | hjm ^ ^ | that you do it." Gandhi | |
From: Chuck R. <shi...@ro...> - 2008-08-20 21:16:23
|
On Aug 20, 2008, at 11:19 AM, Harry J Mason wrote: > On Wed, 20 Aug 2008, Chuck Randall wrote: > >> On Aug 20, 2008, at 3:31 AM, Harry J Mason wrote: >> >>> On Tue, 19 Aug 2008, Chuck Randall wrote: >>> >>>> I just reflashed my connex-400xm with a newly built gumstix-basic- >>>> image. Now I get a "bad magic number" when I try to boot it. What >>>> could have gone wrong? The log of the reflash procedure is show >>>> below. >>> >>> [snip] >>> >>>> GUM> fatload mmc 1 a20000000 rootfs >>>> GUM> cp.b a20000000 40000 ${filesize} >>> >>> Too many zeros here. The correct address is a2000000 (6 zeros). >> >> Yes, I just noticed that, too. When I use a2000000 I get a bunch of >> errors. See the log listing below. > >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >> 0x00000000: 0x0f0f id >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >> 0x00000004: 0x0404 id > > It looks like there's incorrect data instead of a valid jffs2, and the > kernel is trying and failing to mount it. > > Did you reflash the filesystem with the correct address, before you > reflashed the kernel? > Did you protect on 1:0-1 ; erase all first? > Did you flash the correct file from oe/tmp/deploy/glibc/images ? Well, I thought I did! ;-) I'll re-do all of the steps again and see what happens. Thx, Chuck |
From: Chuck R. <shi...@ro...> - 2008-08-20 15:58:44
|
On Aug 20, 2008, at 3:31 AM, Harry J Mason wrote: > On Tue, 19 Aug 2008, Chuck Randall wrote: > >> I just reflashed my connex-400xm with a newly built gumstix-basic- >> image. Now I get a "bad magic number" when I try to boot it. What >> could have gone wrong? The log of the reflash procedure is show >> below. > > [snip] > >> GUM> fatload mmc 1 a20000000 rootfs >> GUM> cp.b a20000000 40000 ${filesize} > > Too many zeros here. The correct address is a2000000 (6 zeros). Yes, I just noticed that, too. When I use a2000000 I get a bunch of errors. See the log listing below. Chuck U-Boot 1.2.0 (May 10 2008 - 13:33:03) - 400 MHz - 1604 *** Welcome to Gumstix *** DRAM:64 MB Flash: 16 MB Using default environment SMC91C1111-0 Net: SMC91C1111-0 Hit any key to stop autoboot: 0 Instruction Cache is ON Copying kernel to 0xa2000000 from 0x00f00000 (length 0x00100000)...done ## Booting image at a2000000 ... Image Name: Angstrom/2.6.21/gumstix-custom-c Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1041252 Bytes = 1016.8 kB Load Address: a0008000 Entry Point: a0008000 OK Starting kernel ... Linux version 2.6.21 (otto@otto) (gcc version 4.1.2) #1 PREEMPT Mon May 12 14:38 CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE), cr=0000397f Machine: The Gumstix Platform Memory policy: ECC disabled, Data cache writeback Memory clock: 99.53MHz (*27) Run Mode clock: 398.13MHz (*4) Turbo Mode clock: 398.13MHz (*1.0, inactive) CPU0: D VIVT undefined 5 cache CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Built 1 zonelists. Total pages: 16256 Kernel command line: console=ttyS0,115200n8 root=1f01 rootfstype=jffs2 reboot=cd PID hash table entries: 256 (order: 8, 1024 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 64MB = 64MB total Memory: 62652KB available (1884K code, 191K data, 144K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 Time: pxa_timer clocksource has been installed. NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered JFFS2 version 2.2. (NAND) (SUMMARY)(C) 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler cfq registered (default) Console: switching to colour frame buffer device 80x24 pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 0) is a HWUART Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit bankwidth) Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x0031 Using buffer write method cfi_cmdset_0001: Erase suspend on write enabled Using static partitions on Gumstix Flash ROM Creating 3 MTD partitions on "Gumstix Flash ROM": 0x00000000-0x00040000 : "Bootloader" 0x00040000-0x00f00000 : "RootFS" 0x00f00000-0x01000000 : "Kernel" TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 XScale DSP coprocessor detected. jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0x0f0f id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004: 0x0404 id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008: 0x0808 id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c: 0x0c0c id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010: 0x1010 id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014: 0x1414 id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018: 0x1818 id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c: 0x1c1c id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020: 0x0f0f id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024: 0x2424 id Further such events for this erase block will not be printed jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020000: 0x0f0f id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020004: 0x0404 id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020008: 0x0808 id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002000c: 0x0c0c id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020010: 0x1010 id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020014: 0x1414 id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020018: 0x1818 id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002001c: 0x1c1c id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0088001c: 0x1c1c id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00880020: 0x0f0f id jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00880024: 0x2424 id Further such events for this erase block will not be printed Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes empty_blocks 49, bad_blocks 0, c->nr_blocks 118 VFS: Cannot open root device "1f01" or unknown-block(31,1) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(31,1) |