* Problems loading ffs image
@ 2006-09-15 17:22 Luís Vitório Cargnini
[not found] ` <ae36f8040609181359u40b0862cyfd380e33192d1a6d@mail.gmail.com>
0 siblings, 1 reply; 10+ messages in thread
From: Luís Vitório Cargnini @ 2006-09-15 17:22 UTC (permalink / raw)
To: OMAP
Hi everybody,
I having problems to boot my file system image i receive the following
error:
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000:
0x0a10 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004:
0x9c14 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008:
0x7828 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c:
0xc8e0 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010:
0x47c7 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014:
0x0a3e instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018:
0xf051 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c:
0xa4c2 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020:
0x8ff0 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024:
0xf1a4 instead
Further such events for this erase block will not be printed
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 116K
Warning: unable to open an initial console.
Kernel panic - not syncing: Attempted to kill init!
i updated the kernel yesterday, and created the image with following
options:
mkfs.jffs2 -p -e 0x20000 -n -v -r bbox/ -o instramed.jffs2
i used the mkfs.jffs2 compiled from latest mtd-utils (as recommended)
uploaded to osk 5912 board, punt on flsh with cp.b 0x1000...... 0x0010......
size
than i boot and the error, could someone help please.
--
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Mastering Degree student @ PUC-RS Electrical Engineer Faculty
^ permalink raw reply [flat|nested] 10+ messages in thread* RE: Fwd: Problems loading ffs image
@ 2006-09-19 20:42 Woodruff, Richard
2006-09-19 21:12 ` Luís Vitório Cargnini
0 siblings, 1 reply; 10+ messages in thread
From: Woodruff, Richard @ 2006-09-19 20:42 UTC (permalink / raw)
To: Luís Vitório Cargnini, Nishanth Menon; +Cc: OMAP
You boot command doesn't look right...
bootcmd=0x00100000 0x10000000 142b34;bootm
What type of device is your root file system on NAND or NOR? NAND and NOR JFFS2 images are created differently. It used to be the clean markers were in-lined in a NOR image (you must specify this in image build). NAND ones are kept in the NAND's OOB area and are not part of the basic image.
Can you even read reasonable data in your flash device when the kernel is on the way up? It could be as simple as your memory timings are wrong given your boot speed and they simply are read up incorrectly.
Regards,
Richard W.
> Hi I've downloaded an fresh git
> tree, free of mtd patches and I still receiving the same error. The
> console is related tot the image blocks errors ?
> my u-boot env:
>
> bootdelay=3
> baudrate=115200
> bootfile="uImage"
> etheraddr=00:0e:99:02:0a:4d
> ethaddr=00:0E:99:02:0A:4D
> bootargs=mem=32M console=ttyS0,115200n8 noinitrd rw ip=off
> root=/dev/mtdblock3 rootfstype=jffs2
> filesize=142b34
> fileaddr=10000000
> netmask=255.255.254.0
> ipaddr=192.168.1.1
> serverip=192.168.1.3
> bootcmd=0x00100000 0x10000000 142b34;bootm
> stdin=serial
> stdout=serial
> stderr=serial
>
>
> On 9/19/06, Nishanth Menon <menon.nishanth@gmail.com> wrote:
> > Luís Vitório Cargnini stated on 9/18/2006 11:46 PM:
> > > yes I'm using the latest kernel and i have patched it with mtd-utils
> > > oficial
> > > patches from site, so i must rollback my patch of mtd ?
> > >
> > I had suspected something like 2.4/2.6.10+latest mtd. Try using the
> > plain kernel with the mtd. I think mtd-utils 1.0 was released by david
> > on mtd. further, MTD
> > list(http://lists.infradead.org/mailman/listinfo/linux-mtd/) might be
> > able to help you better on this. it may even be your mkfs.jffs2 options
> > that goofed it up..
> >
> > Regards,
> > Nishanth Menon
> >
>
>
> --
> Thanks && Regards
> Msc. Bsc. Luís Vitório Cargnini
> IEEE Member
> Mastering Degree student @ PUC-RS Electrical Engineer Faculty
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Fwd: Problems loading ffs image
2006-09-19 20:42 Woodruff, Richard
@ 2006-09-19 21:12 ` Luís Vitório Cargnini
2006-09-20 1:09 ` Nishanth Menon
0 siblings, 1 reply; 10+ messages in thread
From: Luís Vitório Cargnini @ 2006-09-19 21:12 UTC (permalink / raw)
To: Woodruff, Richard; +Cc: OMAP
[-- Attachment #1: Type: text/plain, Size: 6646 bytes --]
itś a nand type i suppose. Is a OSK 5912 starter kit where I'm trying
to boot my new system.
My full boot message log on console screen:
OMAP5912 OSK # boot
Unknown command '0x00100000' - try 'help'
## Booting image at 10000000 ...
Image Name: Linux-2.6.18-rc7-omap1-gf16bdc72
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1321716 Bytes = 1.3 MB
Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux.......................................................................................
done, booting the kernel.
Linux version 2.6.18-rc7-omap1-gf16bdc72 (lvcargnini@enterprise) (gcc
version 4.0.0 (DENX ELDK 4.0 4.0.0)) #1 Tue Sep 19 18:09:46 BRT 2006
CPU: ARM926EJ-S [41069263] revision 3 (ARMv5TEJ), cr=00053177
Machine: TI-OSK
Memory policy: ECC disabled, Data cache writeback
OMAP162123 revision 2 handled as 16xx id: 8605907dc1530214
SRAM: Mapped pa 0x20000000 to va 0xd0000000 size: 0x100000
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists. Total pages: 8192
Kernel command line: mem=32M console=ttyS0,115200n8 noinitrd rw ip=off
root=/dev/mtdblock3 rootfstype=jffs2
Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x2833 ARM_CKCTL: 0x2000
Clocking rate (xtal/DPLL1/MPU): 12.0/192.0/192.0 MHz
Total of 128 interrupts in 4 interrupt banks
OMAP GPIO hardware version 1.0
MUX: initialized M7_1610_GPIO62
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 29616KB available (2201K code, 477K data, 116K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
OMAP DMA hardware version 1
DMA capabilities: 000c0000:00000000:01ff:003f:007f
Initializing OMAP McBSP system
omap_dsp_init() done
USB: hmc 16, usb0 2 wires
i2c_omap i2c_omap.1: bus 0 rev2.2 at 100 kHz
tps65010: version 2 May 2005
No IRQF_TRIGGER set_type function for IRQ 353 (MPUIO)
MUX: initialized N14_1610_UWIRE_CS0
MUX: initialized P15_1610_UWIRE_CS3
NET: Registered protocol family 2
IP route cache hash table entries: 256 (order: -2, 1024 bytes)
TCP established hash table entries: 1024 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 1024 bind 512)
TCP reno registered
Power Management for TI OMAP.
MUX: initialized T20_1610_LOW_PWR
NetWinder Floating Point Emulator V0.97 (double precision)
OMAP OCPI interconnect driver loaded
OMAP DSP driver initialization
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST16654
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
PPP generic driver version 2.4.2
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org>
eth0: SMC91C94 (rev 9) at c2850300 IRQ 160 [nowait]
eth0: Ethernet addr: 00:0e:99:02:0a:4d
i2c /dev entries driver
Clock enabled to MCBSP1 & 3
TLV320AIC23 I2C version 1.8 (10-Feb-2006)
omapflash.0: Found 1 x16 devices at 0x0 in 16-bit bank
omapflash.0: Found 1 x16 devices at 0x1000000 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
Creating 4 MTD partitions on "omapflash.0":
0x00000000-0x00020000 : "bootloader"
0x00020000-0x00040000 : "params"
0x00040000-0x00240000 : "kernel"
0x00240000-0x02000000 : "filesystem"
MUX: initialized W11_1610_CF_CD1
MUX: initialized P11_1610_CF_CD2
MUX: initialized R11_1610_CF_IOIS16
MUX: initialized V10_1610_CF_IREQ
MUX: initialized W10_1610_CF_RESET
omap_cf: cs2 on irq 222
mice: PS/2 mouse device common for all mice
OMAP Keypad Driver
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22
13:55:50 2006 UTC).
audio support initialized
ALSA device list:
#0: OSK AIC23
TCP bic registered
NET: Registered protocol family 1
Disabling unused clock "usb_dc_ck"... done
FIXME: Clock "tc2_ck" seems unused
Disabling unused clock "tc1_ck"... done
Skipping reset check for DSP domain clock "dsptim_ck"
Skipping reset check for DSP domain clock "dspper_ck"
OMAP GPIO switch handler initializing
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000:
0x9d8d instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004:
0x0b59 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008:
0x4f8f instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c:
0xd159 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010:
0xe226 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014:
0x9318 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018:
0x030a instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c:
0xb702 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020:
0x7044 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024:
0x6d97 instead
Further such events for this erase block will not be printed
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 116K
Warning: unable to open an initial console.
I'm using the mkfs.jffs2 of mtd-utils 1.00 as i said before.
the command to create image is:
mkfs.jffs2 -p -l -e 0x20000 -n -v -r ilfs/ -o instramed.jffs2
On 9/19/06, Woodruff, Richard <r-woodruff2@ti.com> wrote:
> You boot command doesn't look right...
> bootcmd=0x00100000 0x10000000 142b34;bootm
>
> What type of device is your root file system on NAND or NOR? NAND and NOR JFFS2 images are created differently. It used to be the clean markers were in-lined in a NOR image (you must specify this in image build). NAND ones are kept in the NAND's OOB area and are not part of the basic image.
>
> Can you even read reasonable data in your flash device when the kernel is on the way up? It could be as simple as your memory timings are wrong given your boot speed and they simply are read up incorrectly.
>
> Regards,
> Richard W.
>
>
>
--
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Mastering Degree student @ PUC-RS Electrical Engineer Faculty
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Fwd: Problems loading ffs image
2006-09-19 21:12 ` Luís Vitório Cargnini
@ 2006-09-20 1:09 ` Nishanth Menon
0 siblings, 0 replies; 10+ messages in thread
From: Nishanth Menon @ 2006-09-20 1:09 UTC (permalink / raw)
To: Luís Vitório Cargnini; +Cc: OMAP
Assumption: mtd-utils
ftp://ftp.infradead.org/pub/mtd-utils/mtd-utils-1.0.0.tar.gz was used to
create the mkfs.jffs2
>cfi_cmdset_0001: Erase suspend on write enabled
>0x00020000-0x00040000 : "params"
Cmdset1+sectorsize=128K looks like a strataflash
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000:
> 0x9d8d instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004:
> 0x0b59 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008:
> 0x4f8f instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c:
> 0xd159 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010:
> 0xe226 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014:
> 0x9318 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018:
> 0x030a instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c:
> 0xb702 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020:
> 0x7044 instead
> VFS: Mounted root (jffs2 filesystem).
> Freeing init memory: 116K
> Warning: unable to open an initial console.
as karthik said: check ur inittab and console device settings esp since
ur using udev now a days..
> I'm using the mkfs.jffs2 of mtd-utils 1.00 as i said before.
> the command to create image is:
> mkfs.jffs2 -p -l -e 0x20000 -n -v -r ilfs/ -o instramed.jffs2
>
<snip>
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024:
> 0x6d97 instead
> Further such events for this erase block will not be printed
Try something simpler.
mkfs.jffs2 -d root_folder -o rootfs_image.jffs2 -e 0x20000
and flash rootfs_image.jffs2 to flash using the following command
(assuming you downloaded to memory at 0x80000000(if this is not the
address of SDRAM memory, change it) and have erased the flash from
0x04240000 to 0x06240000)
cp.b 0x80000000 0x04240000 (size of the filesystem)
> On 9/19/06, Woodruff, Richard <r-woodruff2@ti.com> wrote:
>> You boot command doesn't look right...
>> bootcmd=0x00100000 0x10000000 142b34;bootm
>>
yup. the bootargs also look good, but the bootcmd is faulty.
>>
>> Can you even read reasonable data in your flash device when the kernel
>> is on the way up? It could be as simple as your memory timings are
>> wrong given your boot speed and they simply are read up incorrectly.
This cannot be true as the CFI probe did work.. so guess the strata
flash is active.
OK just in case nothing worked, as an last ditch alternate strategy, in
case you do have ethernet working:
boot out of NFS. have the filesystem you would like to have in the flash
visible in the NFS filesystem.
Now, with the mtd-utils, do the following:
./flash_eraseall -j /dev/mtd/3
mount -t jffs2 /dev/mtdblock/3 /mnt
cd /mnt
cp -rvf <theflashfilesystemdirectory/*> .
ls -al
it should now look like
usr bin lib include tmp dev
etc..
if ur filesystem looks good (i'd use a filesystem that boots off NFS for
this so a good checkpoint if your filesystem has console and others will
be that), next:
cd
umount /mnt
cat /dev/mtd/3>anewImage.jffs2
you can now use the anewImage.jffs2
happy hunting..
Regards,
Nishanth Menon
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Fwd: Problems loading ffs image
@ 2006-09-19 21:21 Woodruff, Richard
2006-09-19 21:39 ` Kipisz, Steven
0 siblings, 1 reply; 10+ messages in thread
From: Woodruff, Richard @ 2006-09-19 21:21 UTC (permalink / raw)
To: Luís Vitório Cargnini; +Cc: OMAP
> itś a nand type i suppose. Is a OSK 5912 starter kit where I'm trying
> to boot my new system.
I don't think this is correct. The boot log shows its using the MTD-CFI driver which is used for NOR type flashes. I don't know a NAND which uses that command format.
> My full boot message log on console screen:
> OMAP5912 OSK # boot
> Unknown command '0x00100000' - try 'help'
> ## Booting image at 10000000 ...
This error comes from the bit I pointed out below about a bad boot command.
I would guess your issue might be with what ever your JFFS image creation command was. It will need to know your erase block size so it can in-line the clean markers and it will need to be told to do so. You should be able to google the correct command, and you need to look up the flash part's data sheet for its attributes to feed into the command.
Regards,
Richard W.
> Image Name: Linux-2.6.18-rc7-omap1-gf16bdc72
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 1321716 Bytes = 1.3 MB
> Load Address: 10008000
> Entry Point: 10008000
> Verifying Checksum ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing
> Linux.....................................................................
> ..................
> done, booting the kernel.
> Linux version 2.6.18-rc7-omap1-gf16bdc72 (lvcargnini@enterprise) (gcc
> version 4.0.0 (DENX ELDK 4.0 4.0.0)) #1 Tue Sep 19 18:09:46 BRT 2006
> CPU: ARM926EJ-S [41069263] revision 3 (ARMv5TEJ), cr=00053177
> Machine: TI-OSK
> Memory policy: ECC disabled, Data cache writeback
> OMAP162123 revision 2 handled as 16xx id: 8605907dc1530214
> SRAM: Mapped pa 0x20000000 to va 0xd0000000 size: 0x100000
> CPU0: D VIVT write-back cache
> CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
> CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
> Built 1 zonelists. Total pages: 8192
> Kernel command line: mem=32M console=ttyS0,115200n8 noinitrd rw ip=off
> root=/dev/mtdblock3 rootfstype=jffs2
> Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x2833 ARM_CKCTL: 0x2000
> Clocking rate (xtal/DPLL1/MPU): 12.0/192.0/192.0 MHz
> Total of 128 interrupts in 4 interrupt banks
> OMAP GPIO hardware version 1.0
> MUX: initialized M7_1610_GPIO62
> PID hash table entries: 256 (order: 8, 1024 bytes)
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 32MB = 32MB total
> Memory: 29616KB available (2201K code, 477K data, 116K init)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> NET: Registered protocol family 16
> OMAP DMA hardware version 1
> DMA capabilities: 000c0000:00000000:01ff:003f:007f
> Initializing OMAP McBSP system
> omap_dsp_init() done
> USB: hmc 16, usb0 2 wires
> i2c_omap i2c_omap.1: bus 0 rev2.2 at 100 kHz
> tps65010: version 2 May 2005
> No IRQF_TRIGGER set_type function for IRQ 353 (MPUIO)
> MUX: initialized N14_1610_UWIRE_CS0
> MUX: initialized P15_1610_UWIRE_CS3
> NET: Registered protocol family 2
> IP route cache hash table entries: 256 (order: -2, 1024 bytes)
> TCP established hash table entries: 1024 (order: 0, 4096 bytes)
> TCP bind hash table entries: 512 (order: -1, 2048 bytes)
> TCP: Hash tables configured (established 1024 bind 512)
> TCP reno registered
> Power Management for TI OMAP.
> MUX: initialized T20_1610_LOW_PWR
> NetWinder Floating Point Emulator V0.97 (double precision)
> OMAP OCPI interconnect driver loaded
> OMAP DSP driver initialization
> JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> serial8250.0: ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST16654
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> loop: loaded (max 8 devices)
> PPP generic driver version 2.4.2
> smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org>
> eth0: SMC91C94 (rev 9) at c2850300 IRQ 160 [nowait]
> eth0: Ethernet addr: 00:0e:99:02:0a:4d
> i2c /dev entries driver
> Clock enabled to MCBSP1 & 3
> TLV320AIC23 I2C version 1.8 (10-Feb-2006)
> omapflash.0: Found 1 x16 devices at 0x0 in 16-bit bank
> omapflash.0: Found 1 x16 devices at 0x1000000 in 16-bit bank
> Intel/Sharp Extended Query Table at 0x0031
> Using buffer write method
> cfi_cmdset_0001: Erase suspend on write enabled
> Creating 4 MTD partitions on "omapflash.0":
> 0x00000000-0x00020000 : "bootloader"
> 0x00020000-0x00040000 : "params"
> 0x00040000-0x00240000 : "kernel"
> 0x00240000-0x02000000 : "filesystem"
> MUX: initialized W11_1610_CF_CD1
> MUX: initialized P11_1610_CF_CD2
> MUX: initialized R11_1610_CF_IOIS16
> MUX: initialized V10_1610_CF_IREQ
> MUX: initialized W10_1610_CF_RESET
> omap_cf: cs2 on irq 222
> mice: PS/2 mouse device common for all mice
> OMAP Keypad Driver
> Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22
> 13:55:50 2006 UTC).
> audio support initialized
> ALSA device list:
> #0: OSK AIC23
> TCP bic registered
> NET: Registered protocol family 1
> Disabling unused clock "usb_dc_ck"... done
> FIXME: Clock "tc2_ck" seems unused
> Disabling unused clock "tc1_ck"... done
> Skipping reset check for DSP domain clock "dsptim_ck"
> Skipping reset check for DSP domain clock "dspper_ck"
> OMAP GPIO switch handler initializing
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000:
> 0x9d8d instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004:
> 0x0b59 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008:
> 0x4f8f instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c:
> 0xd159 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010:
> 0xe226 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014:
> 0x9318 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018:
> 0x030a instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c:
> 0xb702 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020:
> 0x7044 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024:
> 0x6d97 instead
> Further such events for this erase block will not be printed
> VFS: Mounted root (jffs2 filesystem).
> Freeing init memory: 116K
> Warning: unable to open an initial console.
> I'm using the mkfs.jffs2 of mtd-utils 1.00 as i said before.
> the command to create image is:
> mkfs.jffs2 -p -l -e 0x20000 -n -v -r ilfs/ -o instramed.jffs2
>
> On 9/19/06, Woodruff, Richard <r-woodruff2@ti.com> wrote:
> > You boot command doesn't look right...
> > bootcmd=0x00100000 0x10000000 142b34;bootm
> >
> > What type of device is your root file system on NAND or NOR? NAND and
> NOR JFFS2 images are created differently. It used to be the clean markers
> were in-lined in a NOR image (you must specify this in image build). NAND
> ones are kept in the NAND's OOB area and are not part of the basic image.
> >
> > Can you even read reasonable data in your flash device when the kernel
> is on the way up? It could be as simple as your memory timings are wrong
> given your boot speed and they simply are read up incorrectly.
> >
> > Regards,
> > Richard W.
> >
> >
> >
>
>
>
> --
> Thanks && Regards
> Msc. Bsc. Luís Vitório Cargnini
> IEEE Member
> Mastering Degree student @ PUC-RS Electrical Engineer Faculty
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Fwd: Problems loading ffs image
2006-09-19 21:21 Woodruff, Richard
@ 2006-09-19 21:39 ` Kipisz, Steven
0 siblings, 0 replies; 10+ messages in thread
From: Kipisz, Steven @ 2006-09-19 21:39 UTC (permalink / raw)
To: Woodruff, Richard, Luís Vitório Cargnini; +Cc: OMAP
This web page http://tree.celinuxforum.org/CelfPubWiki/OSK has lots of information on the OSK 5912.
Steve K.
-----Original Message-----
From: linux-omap-open-source-bounces@linux.omap.com [mailto:linux-omap-open-source-bounces@linux.omap.com] On Behalf Of Woodruff, Richard
Sent: Tuesday, September 19, 2006 4:22 PM
To: Luís Vitório Cargnini
Cc: OMAP
Subject: RE: Fwd: Problems loading ffs image
> itś a nand type i suppose. Is a OSK 5912 starter kit where I'm trying
> to boot my new system.
I don't think this is correct. The boot log shows its using the MTD-CFI driver which is used for NOR type flashes. I don't know a NAND which uses that command format.
> My full boot message log on console screen:
> OMAP5912 OSK # boot
> Unknown command '0x00100000' - try 'help'
> ## Booting image at 10000000 ...
This error comes from the bit I pointed out below about a bad boot command.
I would guess your issue might be with what ever your JFFS image creation command was. It will need to know your erase block size so it can in-line the clean markers and it will need to be told to do so. You should be able to google the correct command, and you need to look up the flash part's data sheet for its attributes to feed into the command.
Regards,
Richard W.
> Image Name: Linux-2.6.18-rc7-omap1-gf16bdc72
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 1321716 Bytes = 1.3 MB
> Load Address: 10008000
> Entry Point: 10008000
> Verifying Checksum ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing
> Linux.....................................................................
> ..................
> done, booting the kernel.
> Linux version 2.6.18-rc7-omap1-gf16bdc72 (lvcargnini@enterprise) (gcc
> version 4.0.0 (DENX ELDK 4.0 4.0.0)) #1 Tue Sep 19 18:09:46 BRT 2006
> CPU: ARM926EJ-S [41069263] revision 3 (ARMv5TEJ), cr=00053177
> Machine: TI-OSK
> Memory policy: ECC disabled, Data cache writeback
> OMAP162123 revision 2 handled as 16xx id: 8605907dc1530214
> SRAM: Mapped pa 0x20000000 to va 0xd0000000 size: 0x100000
> CPU0: D VIVT write-back cache
> CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
> CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
> Built 1 zonelists. Total pages: 8192
> Kernel command line: mem=32M console=ttyS0,115200n8 noinitrd rw ip=off
> root=/dev/mtdblock3 rootfstype=jffs2
> Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x2833 ARM_CKCTL: 0x2000
> Clocking rate (xtal/DPLL1/MPU): 12.0/192.0/192.0 MHz
> Total of 128 interrupts in 4 interrupt banks
> OMAP GPIO hardware version 1.0
> MUX: initialized M7_1610_GPIO62
> PID hash table entries: 256 (order: 8, 1024 bytes)
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 32MB = 32MB total
> Memory: 29616KB available (2201K code, 477K data, 116K init)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> NET: Registered protocol family 16
> OMAP DMA hardware version 1
> DMA capabilities: 000c0000:00000000:01ff:003f:007f
> Initializing OMAP McBSP system
> omap_dsp_init() done
> USB: hmc 16, usb0 2 wires
> i2c_omap i2c_omap.1: bus 0 rev2.2 at 100 kHz
> tps65010: version 2 May 2005
> No IRQF_TRIGGER set_type function for IRQ 353 (MPUIO)
> MUX: initialized N14_1610_UWIRE_CS0
> MUX: initialized P15_1610_UWIRE_CS3
> NET: Registered protocol family 2
> IP route cache hash table entries: 256 (order: -2, 1024 bytes)
> TCP established hash table entries: 1024 (order: 0, 4096 bytes)
> TCP bind hash table entries: 512 (order: -1, 2048 bytes)
> TCP: Hash tables configured (established 1024 bind 512)
> TCP reno registered
> Power Management for TI OMAP.
> MUX: initialized T20_1610_LOW_PWR
> NetWinder Floating Point Emulator V0.97 (double precision)
> OMAP OCPI interconnect driver loaded
> OMAP DSP driver initialization
> JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> serial8250.0: ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST16654
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> loop: loaded (max 8 devices)
> PPP generic driver version 2.4.2
> smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org>
> eth0: SMC91C94 (rev 9) at c2850300 IRQ 160 [nowait]
> eth0: Ethernet addr: 00:0e:99:02:0a:4d
> i2c /dev entries driver
> Clock enabled to MCBSP1 & 3
> TLV320AIC23 I2C version 1.8 (10-Feb-2006)
> omapflash.0: Found 1 x16 devices at 0x0 in 16-bit bank
> omapflash.0: Found 1 x16 devices at 0x1000000 in 16-bit bank
> Intel/Sharp Extended Query Table at 0x0031
> Using buffer write method
> cfi_cmdset_0001: Erase suspend on write enabled
> Creating 4 MTD partitions on "omapflash.0":
> 0x00000000-0x00020000 : "bootloader"
> 0x00020000-0x00040000 : "params"
> 0x00040000-0x00240000 : "kernel"
> 0x00240000-0x02000000 : "filesystem"
> MUX: initialized W11_1610_CF_CD1
> MUX: initialized P11_1610_CF_CD2
> MUX: initialized R11_1610_CF_IOIS16
> MUX: initialized V10_1610_CF_IREQ
> MUX: initialized W10_1610_CF_RESET
> omap_cf: cs2 on irq 222
> mice: PS/2 mouse device common for all mice
> OMAP Keypad Driver
> Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22
> 13:55:50 2006 UTC).
> audio support initialized
> ALSA device list:
> #0: OSK AIC23
> TCP bic registered
> NET: Registered protocol family 1
> Disabling unused clock "usb_dc_ck"... done
> FIXME: Clock "tc2_ck" seems unused
> Disabling unused clock "tc1_ck"... done
> Skipping reset check for DSP domain clock "dsptim_ck"
> Skipping reset check for DSP domain clock "dspper_ck"
> OMAP GPIO switch handler initializing
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000:
> 0x9d8d instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004:
> 0x0b59 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008:
> 0x4f8f instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c:
> 0xd159 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010:
> 0xe226 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014:
> 0x9318 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018:
> 0x030a instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c:
> 0xb702 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020:
> 0x7044 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024:
> 0x6d97 instead
> Further such events for this erase block will not be printed
> VFS: Mounted root (jffs2 filesystem).
> Freeing init memory: 116K
> Warning: unable to open an initial console.
> I'm using the mkfs.jffs2 of mtd-utils 1.00 as i said before.
> the command to create image is:
> mkfs.jffs2 -p -l -e 0x20000 -n -v -r ilfs/ -o instramed.jffs2
>
> On 9/19/06, Woodruff, Richard <r-woodruff2@ti.com> wrote:
> > You boot command doesn't look right...
> > bootcmd=0x00100000 0x10000000 142b34;bootm
> >
> > What type of device is your root file system on NAND or NOR? NAND and
> NOR JFFS2 images are created differently. It used to be the clean markers
> were in-lined in a NOR image (you must specify this in image build). NAND
> ones are kept in the NAND's OOB area and are not part of the basic image.
> >
> > Can you even read reasonable data in your flash device when the kernel
> is on the way up? It could be as simple as your memory timings are wrong
> given your boot speed and they simply are read up incorrectly.
> >
> > Regards,
> > Richard W.
> >
> >
> >
>
>
>
> --
> Thanks && Regards
> Msc. Bsc. Luís Vitório Cargnini
> IEEE Member
> Mastering Degree student @ PUC-RS Electrical Engineer Faculty
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Fwd: Problems loading ffs image
@ 2006-09-19 22:03 karthik
0 siblings, 0 replies; 10+ messages in thread
From: karthik @ 2006-09-19 22:03 UTC (permalink / raw)
To: linux-omap-open-source
Basic :
Do you have the device node in your image for console device ? (/dev/console)
karthik
---------------------------------
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2006-09-20 1:09 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-15 17:22 Problems loading ffs image Luís Vitório Cargnini
[not found] ` <ae36f8040609181359u40b0862cyfd380e33192d1a6d@mail.gmail.com>
2006-09-18 21:00 ` Fwd: " Luís Vitório Cargnini
2006-09-19 1:08 ` Nishanth Menon
[not found] ` <ae36f8040609182146w2c81f262n308421935165dc07@mail.gmail.com>
[not found] ` <450FCC8F.5050600@gmail.com>
2006-09-19 20:31 ` Luís Vitório Cargnini
-- strict thread matches above, loose matches on Subject: below --
2006-09-19 20:42 Woodruff, Richard
2006-09-19 21:12 ` Luís Vitório Cargnini
2006-09-20 1:09 ` Nishanth Menon
2006-09-19 21:21 Woodruff, Richard
2006-09-19 21:39 ` Kipisz, Steven
2006-09-19 22:03 karthik
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox