Bad blocks in NAND-flash

[Gerhard]

Hello,

I am new in the mini-2440-world and tried to upload Qtopia. The Mini2440-Board is new. I processed the instruction steps in the user manual but the system installation fails. Maybe I do any principal error.

I execited following steps:

Step 1.) Upload supervivi-64M to mini2440-board using v-command in menu -> success
Step 2.) Upload zImage_N35 to mini 2440-boad using k-command in menu -> success
Step 3.) Upload root_qtopia-64M.img to mini 2440-boad using k-command in menu ->

Enter your selection: y
USB host is connected. Waiting a download.

Now, Downloading [ADDRESS:30000000h,TOTAL:51505882]
Downloaded file at 0x30000000, size = 51505872 bytes
Flash params: oobsize = 64, oobblock = 2048, erasesize = 131072, partition size
= 131596288
Erasing and programming NAND with yaffs image
Block erasing(addr/count) --- Block bad(addr/count) --- Block processed/All(%)
--------------------------------------------------------------------------------

0x07fc0000/01002 0x037a0000/00002 01004/01004=100%
Load yaffs OK:
Blocks scanned: 1004, Blocks erased: 1002, Blocks are bad: 2
RECEIVED and Writed FILE SIZE:51505882 (598KB/S, 84S)

So it seems that thre are two bad blocks in the flash

Step 4: Unplug USB cable, and reboot system

The system startups and the TFT-screen shows the FriendlyARM-picture and following message appears in the terminal window:

Creating 4 MTD partitions on "NAND 128MiB 3,3V 8-bit":
0x000000000000-0x000000060000 : "supervivi"
0x000000060000-0x000000260000 : "Kernel"
0x000000260000-0x000040260000 : "root"
mtd: partition "root" extends beyond the end of device "NAND 128MiB 3,3V 8-bit"
-- size truncated to 0x7da0000
0x000000000000-0x000040000000 : "nand"
mtd: partition "nand" extends beyond the end of device "NAND 128MiB 3,3V 8-bit"
-- size truncated to 0x8000000
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: S3C24XX OHCI
usb usb1: Manufacturer: Linux 2.6.29.4-FriendlyARM ohci_hcd
usb usb1: SerialNumber: s3c24xx
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
mice: PS/2 mouse device common for all mice
s3c2410 TouchScreen successfully loaded
input: s3c2410 TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c2410-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
s3c2440-i2c s3c2440-i2c: slave address 0x10
s3c2440-i2c s3c2440-i2c: bus frequency set to 98 KHz
s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled
mapped channel 0 to 0
s3c2440-sdi s3c2440-sdi: powered down.
s3c2440-sdi s3c2440-sdi: initialisation done.
s3c2440-sdi s3c2440-sdi: running at 0kHz (requested: 0kHz).
s3c2440-sdi s3c2440-sdi: running at 198kHz (requested: 197kHz).
s3c2440-sdi s3c2440-sdi: running at 198kHz (requested: 197kHz).
s3c2440-sdi s3c2440-sdi: running at 198kHz (requested: 197kHz).
s3c2440-sdi s3c2440-sdi: powered down.
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18a.
No device for DAI UDA134X
No device for DAI s3c24xx-i2s
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: UDA134X <-> s3c24xx-i2s mapping ok
ALSA device list:
#0: S3C24XX_UDA134X (UDA134X)
TCP cubic registered
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
lib80211: common routines for IEEE802.11 drivers
s3c2410-rtc s3c2410-rtc: setting system clock to 2005-06-19 16:50:29 UTC (111919
9829)
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs: auto selecting yaffs2
block 3 is bad
block 4 is bad
....
...
...
block 382 is bad
block 383 is bad
block 384 is bad
block 427 is bad
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 128K
Warning: unable to open an initial console.
Failed to execute /linuxrc. Attempting defaults...
Kernel panic - not syncing: No init found. Try passing init= option to kernel.

Does anybody have an idea how to solve this problem?

Friendly regards

Gerhard

[esky-sh]

You may installed a 64MB image on a 128MB nand flash board. You can try to load 128MB image.

[esky-sh]

do not forget use 'x' command to format nand flash before your burning.

[Gerhard]

Hello

Thank you, that worked for me . There are still two bad blocks but with 128 MB-image it works. I took the 64 MB-image because of the user manual

Friendly regards and thank you for the fast and effective help

Geri