Печать

Пожалуйста, войдите или зарегистрируйтесь.
1 час 1 день 1 неделя 1 месяц Навсегда

[ZAA]

Загрузил ядро на тион про2 скачал образ КФС отсюда: ядро выводит следущие сообщения:

VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 124K
pgd = c0658000
[00000000] *pgd=00653031, *pte=00000000, *ppte=00000000

Pid: 250, comm:                 init
pgd = c0010000
[000000fa] *pgd=00018031CPU: 0
PC is at 0x40001150
LR is at __init_begin+0x3fff8000/0x30
pc : [<40001150>]    lr : [<00000000>]    Not tainted
sp : bef56c04  ip : 00000000  fp : bef56da0
r10: 4000c238  r9 : bef56eac  r8 : bef56ebc
r7 : 00000002  r6 : 40003e1c  r5 : 00000000  r4 : 00000000
r3 : 00000025  r2 : 00000000  r1 : 00000000  r0 : 00000000
Flags: nzCv  IRQs on  FIQs on  Mode USER_32  Segment user
Control: C000717F
Table: 00658000  DAC: 00000015
[<c0028f4c>] (show_regs+0x0/0x50) from [<c002dca8>] (__do_user_fault+0x5c/0xa4)
 r4 = C0512820
[<c002dc4c>] (__do_user_fault+0x0/0xa4) , *pte=00000000, *ppte=00000000

при вводе команды ls в U-Bootе содержимое КФС выводится.
значение переменных окружения и версия U-Bootа:

u-boot> printenv
baudrate=57600
bootfile="tion.img"
mtdparts=mtdparts=physmap-flash.0:512k(u-boot)ro,2560k(ukernel),62208k(root),12
ethact=ep93xx_eth-0
mtdids=nor0=physmap-flash.0
bootdelay=5
fileaddr=0x60080000
bootards=root=/dev/sda1 console=ttyAM1,57600
autostart=yes
bootcmd=bootm 60080000
filesize=CC0000
partition=nor0,2
mtddevnum=2
mtddevname=root
bootargs=root=/dev/mtdblock2 rootfstype=jffs2 console=ttyAM0,57600 user_debug=31

stdin=serial
stdout=serial
stderr=serial
ethaddr=00:50:c2:bb:4d:ad

Environment size: 528/65531 bytes
u-boot> version

U-Boot 2010.09-00020-ga313ade (Nov 23 2011 - 16:02:07)

[asv]

1. Напишите (по командам) как записывали КФС во Flash
2. Проверяли ли контрольную сумму после записи
3. Приведите сообщения ядра полностью

[ZAA]

А как проверить контрольную сумму после записи образа?
Записывал так:

U-Boot 2010.09-00020-ga313ade (Nov 23 2011 - 16:02:07)

DRAM:  64 MiB
Flash: 64 MiB
In:    serial
Out:   serial
Err:   serial
Note: to disable console close COL0 to COL1 pin
Net:   ep93xx_eth-0
Hit any key to stop autoboot:  0
u-boot> protect off all
Un-Protect Flash Bank # 1
................................................................................
................................................................................
................................................................................
................... done
u-boot> mtdparts

device nor0 <physmap-flash.0>, # parts = 6
 #: name                size            offset          mask_flags
 0: u-boot              0x00080000      0x00000000      1
 1: ukernel             0x00280000      0x00080000      0
 2: root                0x03cc0000      0x00300000      0
 3: free                0x00020000      0x03fc0000      0
 4: u-boot_env1         0x00010000      0x03fe0000      0
 5: u-boot_env2         0x00010000      0x03ff0000      0

active partition: nor0,2 - (root) 0x03cc0000 @ 0x00300000

defaults:
mtdids  : nor0=physmap-flash.0
mtdparts: mtdparts=physmap-flash.0:512k(u-boot)ro,2560k(ukernel),62208k(root),12
8k(free),64k(u-boot_env1),64k(u-boot_env2)
u-boot> erase 60300000 +3cc0000

................................................................................
................................................................................
................................................................................
... done
Erased 243 sectors
u-boot> loady
## Ready for binary (ymodem) download to 0x04000000 at 57600 bps...
CCCCCCCCCxyzModem - CRC mode, 2(SOH)/13056(STX)/0(CAN) packets, 11 retries
## Total Size      = 0x00cc0000 = 13369344 Bytes
u-boot> cp.b 4000000 60300000 cc0000
Copy to Flash... done

Загрузил другую сборку ядра сначала использовал это, а теперь перешол на вот это вывод ядра:

## Booting kernel from Legacy Image at 60080000 ...
   Image Name:   Linux-2.6.20.21
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1780528 Bytes = 1.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
Linux version 2.6.20.21 (asv@debian) (gcc version 4.3.4 (GCC) ) #1 PREEMPT Mon 1
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
Machine: Tion-Pro2 Board
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists.  Total pages: 16192
Kernel command line: root=/dev/mtdblock2 rootfstype=jffs2 console=ttyAM0,57600
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: 32MB 32MB = 64MB total
Memory: 61140KB available (3268K code, 340K data, 124K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
ep93xx: PLL1 running at 399 MHz, PLL2 at 192 MHz
ep93xx: FCLK 199 MHz, HCLK 99 MHz, PCLK 49 MHz
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (extended precision)
audit: initializing netlink socket (disabled)
audit(0.380:1): initialized
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered (default)
io scheduler anticipatory registered
ep93xx-backlight ep93xx-backlight.0: initialized
ep93xxfb_get_par: VGA 640x480
Console: switching to colour frame buffer device 80x30
fb0: EP93xx frame buffer at 640x480x16bpp
ep93xx_wdt: EP93XX watchdog, driver version 0.3
Serial: AMBA driver $Revision: 1.41 $
RS485 hardware flow control on 3rd serial port
apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
RAMDISK driver initialized: 2 RAM disks of 32768K size 1024 blocksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
Cirrus Logic EP93XX IDE initialization.
physmap platform flash device: 03ff0000 at 60000000
physmap-flash.0: Found 2 x16 devices at 0x0 in 32-bit bank
NOR chip too large to fit in mapping. Attempting to cope...
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
Using buffer write method
Using auto-unlock on power-up/resume
cfi_cmdset_0001: Erase suspend on write enabled
Reducing visibility of 65536KiB chip to 65472KiB
RedBoot partition parsing not available
Using physmap partition information
Creating 3 MTD partitions on "physmap-flash.0":
0x00000000-0x00080000 : "bootloader"
0x00080000-0x00300000 : "kernel"
0x00300000-0x03fc0000 : "rootfs"
ep93xx-spi ep93xx-spi.1: SPI controller initialized
ep93xx-usb ep93xx-usb: EP93xx OHCI
ep93xx-usb ep93xx-usb: new USB bus registered, assigned bus number 1
ep93xx-usb ep93xx-usb: irq 56, io mem 0x80020000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usb 1-1: new low speed USB device using ep93xx-usb and address 2
usb 1-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver hiddev
input:   USB Keyboard as /class/input/input0
input: USB HID v1.10 Keyboard [  USB Keyboard] on usb-ep93xx-1
input:   USB Keyboard as /class/input/input1
input: USB HID v1.10 Device [  USB Keyboard] on usb-ep93xx-1
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Sere
usbcore: registered new interface driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
mice: PS/2 mouse device common for all mice
m41t00 0-0068: rtc core: registered m41t00 as rtc0
Registered led device: ep93xx:green
Registered led device: ep93xx:red
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
m41t00 0-0068: hctosys: invalid date/time
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 124K
Unable to handle kernel NULL pointer dereference at virtual address 00000094
pgd = c07d0000
[00000094] *pgd=007bc031, *pte=00000000, *ppte=00000000
Internal error: Oops: 17 [#1]
Modules linked in: mmc_spi mmc_core
CPU: 0
PC is at mmc_spi_probe+0x2c/0x3b0 [mmc_spi]
LR is at mmc_spi_probe+0x30/0x3b0 [mmc_spi]
pc : [<bf00e2ac>]    lr : [<bf00e2b0>]    Not tainted
sp : c580bd94  ip : c580bdd0  fp : c580bdcc
r10: c064a3a0  r9 : bf00f124  r8 : 00000014
r7 : c01b9e6c  r6 : c05c7000  r5 : 00000000  r4 : bf00f124
r3 : 00000000  r2 : 00000001  r1 : 00000000  r0 : c05c7000
Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: C000717F
Table: 007D0000  DAC: 00000015
Process insmod (pid: 262, stack limit = 0xc580a258)
Stack: (0xc580bd94 to 0xc580c000)
bd80:                                              c02c48cc c05c7000 00000000
bda0: c05c7068 c01b9e6c bf00f124 c05c7000 c064a3a0 c01b9e6c 00000014 c064a3a0
bdc0: c580bddc c580bdd0 c01fe340 bf00e290 c580be0c c580bde0 c01b9ca0 c01fe330
bde0: 00000000 bf00f124 c05c7000 c064a3a0 c01b9e6c 00000014 bf00f208 c0020fc4
be00: c580be2c c580be10 c01b9e50 c01b9c44 c580be44 c05c7000 c05c70d4 bf00f124
be20: c580be44 c580be30 c01b9f50 c01b9db8 00000000 c580be4c c580be74 c580be48
be40: c01b9584 c01b9e7c bf00f208 c036f510 c036f510 c05c7048 bf00f124 bf00f138
be60: 00000000 c036f410 c580be84 c580be78 c01b9b4c c01b9534 c580bea4 c580be88
be80: c01b8e48 c01b9b3c bf00f124 c0020e00 c6859f24 bf00f1c0 c580bebc c580bea8
bea0: c01ba0cc c01b8de8 c008b7fc bf00f1c0 c580becc c580bec0 c01fead4 c01ba078
bec0: c580bedc c580bed0 bf011014 c01fea98 c580bfa4 c580bee0 c006ac68 bf011010
bee0: 00000000 40006000 c07aae10 00000007 00000007 bf00f1cc c580a000 00000000
bf00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf20: 0000000a 00000000 00000000 00000000 00000000 c685a89c c064a9a0 c6859b64
bf40: c6859c04 c6858000 c6859ed4 c6859e0c c01fec4c 00000060 00000060 00000002
bf60: 00000002 c02c76a0 c6859efc 00000014 00000000 00000000 00000002 00000003
bf80: 00000000 00000000 00000080 c0028724 c580a000 00900071 00000000 c580bfa8
bfa0: c0027f40 c006ab48 00000000 00000000 00900080 40006000 00002ba5 0018c008
bfc0: 00000003 00000000 00000000 be9d6f62 00000000 00000000 00000002 0000cfa8
bfe0: 4009a69c be9d6d6c 00037ae0 4009a6ac 20000010 00900080 00000000 00000000
Backtrace:
[<bf00e280>] (mmc_spi_probe+0x0/0x3b0 [mmc_spi]) from [<c01fe340>] (spi_drv_pro)
[<c01fe320>] (spi_drv_probe+0x0/0x24) from [<c01b9ca0>] (really_probe+0x6c/0x17)
[<c01b9c34>] (really_probe+0x0/0x174) from [<c01b9e50>] (driver_probe_device+0x)
[<c01b9da8>] (driver_probe_device+0x0/0xc4) from [<c01b9f50>] (__driver_attach+)
 r6 = BF00F124  r5 = C05C70D4  r4 = C05C7000
[<c01b9e6c>] (__driver_attach+0x0/0xe8) from [<c01b9584>] (bus_for_each_dev+0x6)
 r5 = C580BE4C  r4 = 00000000
[<c01b9524>] (bus_for_each_dev+0x0/0x8c) from [<c01b9b4c>] (driver_attach+0x20/)
 r7 = C036F410  r6 = 00000000  r5 = BF00F138  r4 = BF00F124
[<c01b9b2c>] (driver_attach+0x0/0x28) from [<c01b8e48>] (bus_add_driver+0x70/0x)
[<c01b8dd8>] (bus_add_driver+0x0/0x190) from [<c01ba0cc>] (driver_register+0x64)
 r7 = BF00F1C0  r6 = C6859F24  r5 = C0020E00  r4 = BF00F124
[<c01ba068>] (driver_register+0x0/0xa0) from [<c01fead4>] (spi_register_driver+)
 r4 = BF00F1C0
[<c01fea88>] (spi_register_driver+0x0/0x60) from [<bf011014>] (mmc_spi_init+0x1)
[<bf011000>] (mmc_spi_init+0x0/0x1c [mmc_spi]) from [<c006ac68>] (sys_init_modu)
[<c006ab38>] (sys_init_module+0x0/0x1758) from [<c0027f40>] (ret_fast_syscall+0)
Code: e5c05135 e590312c e1a06000 e1a0e00f (e593f094)

Please press Enter to activate this console.

Теперь после нажатия Enter я попадаю в консоль но кфс монтирована read only хотя в переменных окружения я указал RW
память стоит  P33TF а U-Boot версии 2010.09

[asv]

> mmc_spi_probe

Думаю, теперь понятно. КФС rootfs_crater_svn819_tion-pro2.jffs2 собрана с
OABI.  И в ней есть драйверы mmc в виде модулей ядра, также OABI. А ядро у
вас видимо с EABI с поддержкой OABI.  Проблема возникает, когда OABI модуль
вставляют в EABI ядро. Вы можете (1) убрать загрузку этих модулей, (2)
собрать новые модули и заменить ими старые (перезаписав файлы в Linux на
Тионе), или (3) записать на плату OABI ядро.

По поводу проверки данных во Flash, после того как вы загрузили файл в RAM,
посчитайте командой U-Boot его контрольную сумму в RAM (размер файла в
байтах ${filesize}), и контрольную сумму данных этого файла во Flash, после
их записи туда. Или можно использовать
   cmp.b ${fileaddr} flash_addr ${filesize}

Проверить файл загруженный с сайта можно по md5sum, файл с md5 есть в
таблице перечня файлов на wiki.

[ZAA]

Убрал загрузку модулей все работает. Только не могу понять зачем эти модули. Мне кажется что они предназначены для работы с MultiMedia Card но ведь у платы нет слота для них?

[asv]

> ведь у платы нет слота для них?

В режиме SPI, через SPI интерфейс.