[akhud 0]

Собрал rootfs для платы mini6410 с помощью http://narcissus.angstrom-distribution.org/. Опции: mini6410, bare-bone, udev, tar.gz. Образ busybox-image-mini6410.tar.gz распаковал на SD карту. Изменил командную строку bootargs в u-boot для загрузки rootfs c sd карты

console=tty0 console=ttySAC0,115200 root=/dev/mmcblk0p1 rootwait

Загрузка происходит, но возникают непонятные ошибки.

 

## Booting image at c0008000 ...

 

Image Name: Angstrom/2.6.28/mini6410

 

Created: 2011-05-23 11:32:51 UTC

 

Image Type: ARM Linux Kernel Image (uncompressed)

 

Data Size: 2344536 Bytes = 2.2 MB

 

Load Address: 50008000

 

Entry Point: 50008000

 

Verifying Checksum ... OK

 

OK

 

 

Starting kernel ...

 

 

Uncompressing Linux...........................................................................

.................................................................................

..... done, booting the kernel.

Linux version 2.6.28.6 (andy@andy-desktop) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #3 PREEMPT Mon May 23 15:32:03 MSD 2011

CPU: ARMv6-compatible processor [410fb766] revision 6 (ARMv7), cr=00c5387f

CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

Machine: SMDK6410

Memory policy: ECC disabled, Data cache writeback

CPU S3C6410 (id 0x36410101)

S3C24XX Clocks, © 2004 Simtec Electronics

S3C64XX: PLL settings, A=532000000, M=532000000, E=24000000

S3C64XX: HCLKx2=266000000, HCLK=133000000, PCLK=66500000

div1: 00000555

 

...

здесь опустил часть лога

...

 

Driver 'sd' needs updating - please use bus_type methods

S3C NAND Driver, © 2008 Samsung Electronics

S3C NAND Driver is using hardware ECC.

NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)

Creating 4 MTD partitions on "NAND 256MiB 3,3V 8-bit":

0x00000000-0x00100000 : "Bootloader"

0x00100000-0x00400000 : "Kernel"

0x00400000-0x03400000 : "Rootfs"

0x03400000-0x10000000 : "File System"

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 79, io mem 0x74300000

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 2 ports detected

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.28.6 ohci_hcd

usb usb1: SerialNumber: s3c24xx

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

s3c-udc : S3C HS USB OTG Device Driver, © 2008-2009 Samsung Electronics

s3c-udc : version 15 March 2009 (DMA Mode)

mice: PS/2 mouse device common for all mice

S3C Touchscreen driver, © 2008 Samsung Electronics

S3C TouchScreen got loaded successfully : 12 bits

input: S3C TouchScreen as /devices/virtual/input/input0

S3C24XX RTC, © 2004,2006 Simtec Electronics

s3c2410_rtc: tick irq 34, alarm irq 92

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 377 KHz

parent clock for camera: 266.000 MHz, divisor: 11

[CAM]RESET CAM.<6>s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter

S3C2410 Watchdog Timer, © 2004 Simtec Electronics

s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled

cpuidle: using governor ladder

sdhci: Secure Digital Host Controller Interface driver

sdhci: Copyright© Pierre Ossman

s3c-sdhci s3c-sdhci.0: clock source 0: hsmmc (133000000 Hz)

s3c-sdhci s3c-sdhci.0: clock source 1: hsmmc (133000000 Hz)

s3c-sdhci s3c-sdhci.0: clock source 2: mmc_bus (44333333 Hz)

[sDHCI]to add external irq as a card detect signal......

[sDHCI]if (pdata->cfg_ext_cd)......

mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA

[sDHCI]request_irq......

sdhci: card inserted.

usbcore: registered new interface driver usbhid

usbhid: v2.6:USB HID core driver

Advanced Linux Sound Architecture Driver Version 1.0.18rc3.

ASoC version 0.13.2

WM9713/WM9714 SoC Audio Codec 0.15

playback: 1, capture : 1

asoc: AC97 HiFi <-> s3c64xx-ac97 mapping ok

ALSA device list:

#0: SMDK6400 (WM9713)

TCP cubic registered

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5

s3c2410-rtc s3c2410-rtc: setting system clock to 2011-05-24 10:31:52 UTC (1306233112)

Waiting for root device /dev/mmcblk0p1...

mmc0: new SD card at address aaaa

mmcblk0: mmc0:aaaa SD02G 1.84 GiB

mmcblk0: p1

kjournald starting. Commit interval 5 seconds

EXT3 FS on mmcblk0p1, internal journal

EXT3-fs: recovery complete.

EXT3-fs: mounted filesystem with ordered data mode.

VFS: Mounted root (ext3 filesystem).

Freeing init memory: 132K

Warning: unable to open an initial console.

 

... здесь пауза секунд 10

 

udev: starting version 151

end_request: I/O error, dev mtdblock1, sector 0

Buffer I/O error on device mtdblock1, logical block 0

s3c-nand: 1 bit error detected at byte 1269, correcting from 0x00 to 0x10...OK

end_request: I/O error, dev mtdblock1, sector 8

Buffer I/O error on device mtdblock1, logical block 1

s3c-nand: 1 bit error detected at byte 1230, correcting from 0x00 to 0x08...OK

end_request: I/O error, dev mtdblock1, sector 16

Buffer I/O error on device mtdblock1, logical block 2

end_request: I/O error, dev mtdblock1, sector 24

Buffer I/O error on device mtdblock1, logical block 3

s3c-nand: 1 bit error detected at byte 529, correcting from 0x7d to 0x5d...OK

end_request: I/O error, dev mtdblock1, sector 32

Buffer I/O error on device mtdblock1, logical block 4

 

... много аналогичных ошибок

 

end_request: I/O error, dev mtdblock0, sector 232

end_request: I/O error, dev mtdblock0, sector 240

end_request: I/O error, dev mtdblock0, sector 248

end_request: I/O error, dev mtdblock0, sector 0

 

.-------.

| | .-.

| | |-----.-----.-----.| | .----..-----.-----.

| | | __ | ---'| '--.| .-'| | |

| | | | | |--- || --'| | | ' | | | |

'---'---'--'--'--. |-----''----''--' '-----'-'-'-'

-' |

'---'

 

The Angstrom Distribution mini6410 ttySAC0

 

Angstrom 2010.7-test-20101121 mini6410 ttySAC0

 

mini6410 login:

 

Система вроде работоспособная, но что означают эти ошибки? В mtdblock0 находится u-boot, а в mtdblock1 ядро и все нормально грузится. Подскажите в какую сторону капать.

[mdmitry 0]

У Вас в логе упоминается NAND, в которой что у Вас записано? Похоже, при сборке проекта по умолчанию все в NAND идет. Помниться, что Angstrom любит все в неё заложить.

[Lampus 0]

Warning: unable to open an initial console.

Надо посмотреть есть ли в образе rootfs файл /dev/console

 

s3c-nand: 1 bit error detected at byte 1269, correcting from 0x00 to 0x10...OK

Смахивает на то что NAND-флеш повреждена. Здесь видно как отрабатывает ECC.

У тебя случаем к ядру ничего не прицеплено в качестве initramfs?

grep CONFIG_INITRAMFS_SOURCE .config

Вообще смущает то, что всё это начинает валится после запуска udev.

Покажи-ка вывод:

grep CONFIG_MTD .config