User Info
Добро пожаловать, Guest Пользователей: 2 Поисковых ботов: 3 Гостей: 1
Не запускается ядро linux на DM8148
Ska1006
Пункты: 163
Регистрация: 01.11.2015
Пол: Мужчина
Из: Москва
Здравствуйте!
Я столкнулся со следующей проблемой:
Разработана плата на базе ti DM8148. Большинство микросхем и связей соответствует SK-DM8148, за исключением:
1)отсутствуют PCI-E, SATA, CAN, второй разъем SD, Audio, часть GPIO, разъем по Sim.
2)Заменены микросхемы памяти, объем увеличен до 2GB
3)Заменена микросхема NAND.
Я рассчитал и внес в U-boot тайминги и параметры новой памяти. U-boot запускается, встроенный memtest проходит. NAND работает, запуск U-boot с nand работает.
При запуске имеем следующий вывод:
Код
U-Boot 2010.06 (Nov 16 2015 - 19:06:28)
TI8148-GP rev 3.0
ARM clk: 600MHz
DDR clk: 200MHz
RAM Configuration:
Bank #0: 80000000 1 GiB
Bank #1: c0000000 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment
The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is already flashed
Hit any key to stop autoboot: 0
reading u-boot.bin
212296 bytes read
## Starting application at 0x80800000 ...
U-Boot 2010.06 (Nov 16 2015 - 19:06:50)
TI8148-GP rev 3.0
ARM clk: 600MHz
DDR clk: 200MHz
I2C: ready
RAM Configuration:
Bank #0: 80000000 1 GiB
Bank #1: c0000000 1 GiB
NAND: HW ECC BCH8 Selected
256 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC or NAND, using default environment
.:;rrr;;.
,5#@@@@#####@@@@@@#2,
,A@@@hi;;;r5;;;;r;rrSG@@@A,
r@@#i;:;s222hG;rrsrrrrrr;ri#@@r
:@@hr:r;SG3ssrr2r;rrsrsrsrsrr;rh@@:
B@H;;rr;3Hs;rrr;sr;;rrsrsrsrsrsr;;H@B
@@s:rrs;5#;;rrrr;r#@H:;;rrsrsrsrsrr:s@@
@@;;srs&X#9;r;r;;,2@@@rrr:;;rrsrsrsrr;;@@
@@;;rrsrrs@MB#@@@@@###@@@@@@#rsrsrsrsrr;;@@
G@r;rrsrsr;#X;SX25Ss#@@#M@#9H9rrsrsrsrsrs;r@G
@9:srsrsrs;2@;:;;:.X@@@@@H::;rrsrsrsrsrsrr:3@
X@;rrsrsrsrr;XAi;;:&@@#@Bs:rrsrsrsrsrsrsrsrr;@X
@#;rsrsrsrsrr;r2ir@@@###::rrsrsrsrsrsrsrsrsr:@@
@A:rrsrsrsrr;:2@29@@M@@@;:;rrrrsrsrsrsrsrsrs;H@
@&;rsrsrsrr;A@@@@@@###@@@s::;:;;rrsrsrsrsrsr;G@
@#:rrsrsrsr;G@5Hr25@@@#@@@#9XG9s:rrrrsrsrsrs:#@
M@;rsrsrsrs;r@&#;::S@@@@@@@M@@@@Grr:;rsrsrsr;@#
:@s;rsrsrsrr:M#Msrr;;&#@@@@@@@@@@H@@5;rsrsr;s@,
@@:rrsrsrsr;S@rrrsr;:;r3MH@@#@M5,S@@irrsrr:@@
@A:rrsrsrsrrrrrsrsrrr;::;@##@r:;rH@h;srr:H@
;@9:rrsrsrsrrrsrsrsrsr;,S@Hi@i:;s;MX;rr:h@;
r@B:rrrrsrsrsrsrsrr;;sA@#i,i@h;r;S5;r:H@r
,@@r;rrrsrsrsrsrr;2BM3r:;r:G@:rrr;;r@@,
B@Mr;rrrrsrsrsr@@S;;;rrr:5M;rr;rM@H
.@@@i;;rrrrsrs2i;rrrrr;r@M:;i@@@.
.A@@#5r;;;r;;;rrr;r:r#AsM@@H.
;&@@@@MhXS5i5SX9B@@@@G;
:ihM#@@@@@##hs,
Net: <ethaddr> not set. Reading from E-fuse
Detected MACID:84:7e:40:8a:9e:de
cpsw
Hit any key to stop autoboot: 0
DM8148#setenv bootargs_mmc console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=2000M@0x80000000 vmalloc=500M notifyk.vpssm3_sva=0xBF900000 noinitrd
DM8148#mmc rescan 0; setenv bootargs $bootargs_mmc; fatload mmc 0 0x81000000 uImage; bootm 0x81000000
reading uImage
2962332 bytes read
## Booting kernel from Legacy Image at 81000000 ...
Image Name: linux-2.6
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2962268 Bytes = 2.8 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
На этом моменте все зависает. Я попробовал добавить в строку bootargs следующие параметры
Код earlyprintk debug ignore_loglevel log_buf_len=10M print_fatal_signals=1 LOGLEVEL=8
при этом появились следующие сообщения после "Uncompressing Linux... done, booting the kernel.":
Код
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (root@DM8148-bld) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #117 Mon Nov 16 15:03:28 FET 2015
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
bootconsole [earlycon0] enabled
debug: ignoring loglevel setting.
reserved size = 52428800 at 0x0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 3.0
SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
On node 0 totalpages: 499200
free_area_init_node: node 0, pgdat c05e9274, node_mem_map c082a000
Normal zone: 891 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 100485 pages, LIFO batch:31
HighMem zone: 3609 pages used for memmap
HighMem zone: 394215 pages, LIFO batch:31
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 494700
Kernel command line: console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=2000M@0x80000000 vmalloc=500M notifyk.vpssm3_sva=0xBF900000 noinitrd earlyprintk debug ignore_loglevel log_buf_len=10M print_fatal_signals=1 LOGLEVEL=8
log_buf_len: 16777216
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 1950MB = 1950MB total
Memory: 1953596k/1953596k available, 94404k reserved, 1591296K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xd9000000 - 0xf8000000 ( 496 MB)
lowmem : 0xc0000000 - 0xd8c00000 ( 396 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc0046000 ( 248 kB)
.text : 0xc0046000 - 0xc05a2000 (5488 kB)
.data : 0xc05a2000 - 0xc05f17c0 ( 318 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:375
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ368
Trying to install interrupt handler for IRQ369
Trying to install interrupt handler for IRQ370
Trying to install interrupt handler for IRQ371
Trying to install interrupt handler for IRQ372
Trying to install interrupt handler for IRQ373
Trying to install interrupt handler for IRQ374
Trying to install type control for IRQ375
Trying to set irq flags for IRQ375
OMAP clockevent source: GPTIMER1 at 20000000 Hz
Console: colour dummy device 80x30
------------------------
| Locking API testsuite:
----------------------------------------------------------------------------
| spin |wlock |rlock |mutex | wsem | rsem |
--------------------------------------------------------------------------
A-A deadlock:failed|failed| ok |failed|failed|failed|
A-B-B-A deadlock:failed|failed| ok |failed|failed|failed|
A-B-B-C-C-A deadlock:failed|failed| ok |failed|failed|failed|
A-B-C-A-B-C deadlock:failed|failed| ok |failed|failed|failed|
A-B-B-C-C-D-D-A deadlock:failed|failed| ok |failed|failed|failed|
A-B-C-D-B-D-D-A deadlock:failed|failed| ok |failed|failed|failed|
A-B-C-D-B-C-D-A deadlock:failed|failed| ok |failed|failed|failed|
double unlock:failed|failed|failed|failed|failed|failed|
initialize held:failed|failed|failed|failed|failed|failed|
bad unlock order: ok | ok | ok | ok | ok | ok |
--------------------------------------------------------------------------
recursive read-lock: | ok | |failed|
recursive read-lock #2: | ok | |failed|
mixed read-write-lock: |failed| |failed|
mixed write-read-lock: |failed| |failed|
--------------------------------------------------------------------------
hard-irqs-on + irq-safe-A/12:failed|failed| ok |
soft-irqs-on + irq-safe-A/12:failed|failed| ok |
hard-irqs-on + irq-safe-A/21:failed|failed| ok |
soft-irqs-on + irq-safe-A/21:failed|failed| ok |
sirq-safe-A => hirqs-on/12:failed|failed| ok |
sirq-safe-A => hirqs-on/21:failed|failed| ok |
hard-safe-A + irqs-on/12:failed|failed| ok |
soft-safe-A + irqs-on/12:failed|failed| ok |
hard-safe-A + irqs-on/21:failed|failed| ok |
soft-safe-A + irqs-on/21:failed|failed| ok |
hard-safe-A + unsafe-B #1/123:failed|failed| ok |
soft-safe-A + unsafe-B #1/123:failed|failed| ok |
hard-safe-A + unsafe-B #1/132:failed|failed| ok |
soft-safe-A + unsafe-B #1/132:failed|failed| ok |
hard-safe-A + unsafe-B #1/213:failed|failed| ok |
soft-safe-A + unsafe-B #1/213:failed|failed| ok |
hard-safe-A + unsafe-B #1/231:failed|failed| ok |
soft-safe-A + unsafe-B #1/231:failed|failed| ok |
hard-safe-A + unsafe-B #1/312:failed|failed| ok |
soft-safe-A + unsafe-B #1/312:failed|failed| ok |
hard-safe-A + unsafe-B #1/321:failed|failed| ok |
soft-safe-A + unsafe-B #1/321:failed|failed| ok |
hard-safe-A + unsafe-B #2/123:failed|failed| ok |
soft-safe-A + unsafe-B #2/123:failed|failed| ok |
hard-safe-A + unsafe-B #2/132:failed|failed| ok |
soft-safe-A + unsafe-B #2/132:failed|failed| ok |
hard-safe-A + unsafe-B #2/213:failed|failed| ok |
soft-safe-A + unsafe-B #2/213:failed|failed| ok |
hard-safe-A + unsafe-B #2/231:failed|failed| ok |
soft-safe-A + unsafe-B #2/231:failed|failed| ok |
hard-safe-A + unsafe-B #2/312:failed|failed| ok |
soft-safe-A + unsafe-B #2/312:failed|failed| ok |
hard-safe-A + unsafe-B #2/321:failed|failed| ok |
soft-safe-A + unsafe-B #2/321:failed|failed| ok |
hard-irq lock-inversion/123:failed|failed| ok |
soft-irq lock-inversion/123:failed|failed| ok |
hard-irq lock-inversion/132:failed|failed| ok |
soft-irq lock-inversion/132:failed|failed| ok |
hard-irq lock-inversion/213:failed|failed| ok |
soft-irq lock-inversion/213:failed|failed| ok |
hard-irq lock-inversion/231:failed|failed| ok |
soft-irq lock-inversion/231:failed|failed| ok |
hard-irq lock-inversion/312:failed|failed| ok |
soft-irq lock-inversion/312:failed|failed| ok |
hard-irq lock-inversion/321:failed|failed| ok |
soft-irq lock-inversion/321:failed|failed| ok |
hard-irq read-recursion/123: ok |
soft-irq read-recursion/123: ok |
hard-irq read-recursion/132: ok |
soft-irq read-recursion/132: ok |
hard-irq read-recursion/213: ok |
soft-irq read-recursion/213: ok |
hard-irq read-recursion/231: ok |
soft-irq read-recursion/231: ok |
hard-irq read-recursion/312: ok |
soft-irq read-recursion/312: ok |
hard-irq read-recursion/321: ok |
soft-irq read-recursion/321: ok |
--------------------------------------------------------
145 out of 218 testcases failed, as expected. |
----------------------------------------------------
ODEBUG: 8 of 8 active objects replaced
ODEBUG: selftest passed
Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
kobject: 'fs' (d841a400): kobject_add_internal: parent: '<NULL>', set: '<NULL>'
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
kobject: 'devices' (d842f308): kobject_add_internal: parent: '<NULL>', set: '<NULL>'
kobject: 'devices' (d842f308): kobject_uevent_env
kobject: 'devices' (d842f308): kobject_uevent_env: attempted to send uevent without kset!
kobject: 'dev' (d842f480): kobject_add_internal: parent: '<NULL>', set: '<NULL>'
kobject: 'block' (d842f600): kobject_add_internal: parent: 'dev', set: '<NULL>'
kobject: 'char' (d842f780): kobject_add_internal: parent: 'dev', set: '<NULL>'
kobject: 'bus' (d842f908): kobject_add_internal: parent: '<NULL>', set: '<NULL>'
kobject: 'bus' (d842f908): kobject_uevent_env
kobject: 'bus' (d842f908): kobject_uevent_env: attempted to send uevent without kset!
kobject: 'class' (d842fa88): kobject_add_internal: parent: '<NULL>', set: '<NULL>'
kobject: 'class' (d842fa88): kobject_uevent_env
kobject: 'class' (d842fa88): kobject_uevent_env: attempted to send uevent without kset!
kobject: 'firmware' (d842fc00): kobject_add_internal: parent: '<NULL>', set: '<NULL>'
device: 'platform': device_add
kobject: 'platform' (c05d0710): kobject_add_internal: parent: 'devices', set: 'devices'
kobject: 'platform' (c05d0710): kobject_uevent_env
kobject: 'platform' (c05d0710): kobject_uevent_env: filter function caused the event to drop!
kobject: 'platform' (d842aa88): kobject_add_internal: parent: 'bus', set: 'bus'
kobject: 'platform' (d842aa88): kobject_uevent_env
kobject: 'platform' (d842aa88): fill_kobj_path: path = '/bus/platform'
kobject: 'devices' (d8431008): kobject_add_internal: parent: 'platform', set: '<NULL>'
kobject: 'devices' (d8431008): kobject_uevent_env
kobject: 'devices' (d8431008): kobject_uevent_env: filter function caused the event to drop!
kobject: 'drivers' (d8431188): kobject_add_internal: parent: 'platform', set: '<NULL>'
kobject: 'drivers' (d8431188): kobject_uevent_env
kobject: 'drivers' (d8431188): kobject_uevent_env: filter function caused the event to drop!
bus: 'platform': registered
kobject: 'system' (d8431308): kobject_add_internal: parent: 'devices', set: '<NULL>'
kobject: 'system' (d8431308): kobject_uevent_env
kobject: 'system' (d8431308): kobject_uevent_env: attempted to send uevent without kset!
Registering sysdev class 'cpu'
kobject: 'cpu' (c05d0864): kobject_add_internal: parent: 'system', set: 'system'
kobject: 'cpu' (c05d0864): kobject_uevent_env
kobject: 'cpu' (c05d0864): fill_kobj_path: path = '/devices/system/cpu'
omap_voltage_early_init: voltage driver support not added
device: 'omap': device_add
kobject: 'omap' (c05bc108): kobject_add_internal: parent: 'platform', set: 'devices'
kobject: 'omap' (c05bc108): kobject_uevent_env
kobject: 'omap' (c05bc108): kobject_uevent_env: filter function caused the event to drop!
kobject: 'kernel' (d8431780): kobject_add_internal: parent: '<NULL>', set: '<NULL>'
kobject: 'power' (d8431900): kobject_add_internal: parent: '<NULL>', set: '<NULL>'
kobject: 'debug' (d8431b00): kobject_add_internal: parent: 'kernel', set: '<NULL>'
atomic64 test passed
regulator: core version 0.5
device class 'regulator': registering
kobject: 'regulator' (d8407608): kobject_add_internal: parent: 'class', set: 'class'
kobject: 'regulator' (d8407608): kobject_uevent_env
kobject: 'regulator' (d8407608): fill_kobj_path: path = '/class/regulator'
Registering platform device 'reg-dummy'. Parent at platform
device: 'reg-dummy': device_add
kobject: 'reg-dummy' (d8405210): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device reg-dummy
kobject: 'reg-dummy' (d8405210): kobject_uevent_env
kobject: 'reg-dummy' (d8405210): fill_kobj_path: path = '/devices/platform/reg-dummy'
device: 'regulator.0': device_add
kobject: 'virtual' (d8441080): kobject_add_internal: parent: 'devices', set: '<NULL>'
kobject: 'regulator' (d8441200): kobject_add_internal: parent: 'virtual', set: '(null)'
kobject: 'regulator.0' (d8405498): kobject_add_internal: parent: 'regulator', set: 'devices'
kobject: 'regulator.0' (d8405498): kobject_uevent_env
kobject: 'regulator.0' (d8405498): fill_kobj_path: path = '/devices/virtual/regulator/regulator.0'
regulator: dummy:
NET: Registered protocol family 16
Registering platform device 'mpu.0'. Parent at omap
device: 'mpu.0': device_add
kobject: 'mpu.0' (d8405d50): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device mpu.0
kobject: 'mpu.0' (d8405d50): kobject_uevent_env
kobject: 'mpu.0' (d8405d50): fill_kobj_path: path = '/devices/platform/omap/mpu.0'
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
Registering platform device 'l3_slow.0'. Parent at omap
device: 'l3_slow.0': device_add
kobject: 'l3_slow.0' (d847a010): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device l3_slow.0
kobject: 'l3_slow.0' (d847a010): kobject_uevent_env
kobject: 'l3_slow.0' (d847a010): fill_kobj_path: path = '/devices/platform/omap/l3_slow.0'
Registering platform device 'omap_gpio.0'. Parent at omap
device: 'omap_gpio.0': device_add
kobject: 'omap_gpio.0' (d847a250): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_gpio.0
kobject: 'omap_gpio.0' (d847a250): kobject_uevent_env
kobject: 'omap_gpio.0' (d847a250): fill_kobj_path: path = '/devices/platform/omap/omap_gpio.0'
Registering platform device 'omap_gpio.1'. Parent at omap
device: 'omap_gpio.1': device_add
kobject: 'omap_gpio.1' (d847a490): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_gpio.1
kobject: 'omap_gpio.1' (d847a490): kobject_uevent_env
kobject: 'omap_gpio.1' (d847a490): fill_kobj_path: path = '/devices/platform/omap/omap_gpio.1'
Registering platform device 'omap_gpio.2'. Parent at omap
device: 'omap_gpio.2': device_add
kobject: 'omap_gpio.2' (d847a6d0): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_gpio.2
kobject: 'omap_gpio.2' (d847a6d0): kobject_uevent_env
kobject: 'omap_gpio.2' (d847a6d0): fill_kobj_path: path = '/devices/platform/omap/omap_gpio.2'
Registering platform device 'omap_gpio.3'. Parent at omap
device: 'omap_gpio.3': device_add
kobject: 'omap_gpio.3' (d847a910): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_gpio.3
kobject: 'omap_gpio.3' (d847a910): kobject_uevent_env
kobject: 'omap_gpio.3' (d847a910): fill_kobj_path: path = '/devices/platform/omap/omap_gpio.3'
bus: 'platform': add driver omap_gpio
kobject: 'omap_gpio' (d845d9c0): kobject_add_internal: parent: 'drivers', set: 'drivers'
bus: 'platform': driver_probe_device: matched device omap_gpio.0 with driver omap_gpio
bus: 'platform': really_probe: probing driver omap_gpio with device omap_gpio.0
OMAP GPIO hardware version 0.1
driver: 'omap_gpio.0': driver_bound: bound to device 'omap_gpio'
bus: 'platform': really_probe: bound device omap_gpio.0 to driver omap_gpio
bus: 'platform': driver_probe_device: matched device omap_gpio.1 with driver omap_gpio
bus: 'platform': really_probe: probing driver omap_gpio with device omap_gpio.1
OMAP GPIO hardware version 0.1
driver: 'omap_gpio.1': driver_bound: bound to device 'omap_gpio'
bus: 'platform': really_probe: bound device omap_gpio.1 to driver omap_gpio
bus: 'platform': driver_probe_device: matched device omap_gpio.2 with driver omap_gpio
bus: 'platform': really_probe: probing driver omap_gpio with device omap_gpio.2
OMAP GPIO hardware version 0.1
driver: 'omap_gpio.2': driver_bound: bound to device 'omap_gpio'
bus: 'platform': really_probe: bound device omap_gpio.2 to driver omap_gpio
bus: 'platform': driver_probe_device: matched device omap_gpio.3 with driver omap_gpio
bus: 'platform': really_probe: probing driver omap_gpio with device omap_gpio.3
OMAP GPIO hardware version 0.1
driver: 'omap_gpio.3': driver_bound: bound to device 'omap_gpio'
bus: 'platform': really_probe: bound device omap_gpio.3 to driver omap_gpio
kobject: 'omap_gpio' (d845d9c0): kobject_uevent_env
kobject: 'omap_gpio' (d845d9c0): fill_kobj_path: path = '/bus/platform/drivers/omap_gpio'
device class 'bdi': registering
kobject: 'bdi' (d8407708): kobject_add_internal: parent: 'class', set: 'class'
kobject: 'bdi' (d8407708): kobject_uevent_env
kobject: 'bdi' (d8407708): fill_kobj_path: path = '/class/bdi'
device class 'lcd': registering
kobject: 'lcd' (d8407808): kobject_add_internal: parent: 'class', set: 'class'
kobject: 'lcd' (d8407808): kobject_uevent_env
kobject: 'lcd' (d8407808): fill_kobj_path: path = '/class/lcd'
device class 'backlight': registering
kobject: 'backlight' (d8407908): kobject_add_internal: parent: 'class', set: 'class'
kobject: 'backlight' (d8407908): kobject_uevent_env
kobject: 'backlight' (d8407908): fill_kobj_path: path = '/class/backlight'
device class 'video_output': registering
kobject: 'video_output' (d8407a08): kobject_add_internal: parent: 'class', set: 'class'
kobject: 'video_output' (d8407a08): kobject_uevent_env
kobject: 'video_output' (d8407a08): fill_kobj_path: path = '/class/video_output'
device class 'tty': registering
kobject: 'tty' (d8407b08): kobject_add_internal: parent: 'class', set: 'class'
kobject: 'tty' (d8407b08): kobject_uevent_env
kobject: 'tty' (d8407b08): fill_kobj_path: path = '/class/tty'
device class 'vtconsole': registering
kobject: 'vtconsole' (d8407c08): kobject_add_internal: parent: 'class', set: 'class'
kobject: 'vtconsole' (d8407c08): kobject_uevent_env
kobject: 'vtconsole' (d8407c08): fill_kobj_path: path = '/class/vtconsole'
device: 'vtcon0': device_add
kobject: 'vtconsole' (d8464280): kobject_add_internal: parent: 'virtual', set: '(null)'
kobject: 'vtcon0' (d847afc8): kobject_add_internal: parent: 'vtconsole', set: 'devices'
kobject: 'vtcon0' (d847afc8): kobject_uevent_env
kobject: 'vtcon0' (d847afc8): fill_kobj_path: path = '/devices/virtual/vtconsole/vtcon0'
kobject: 'spi' (d845db48): kobject_add_internal: parent: 'bus', set: 'bus'
kobject: 'spi' (d845db48): kobject_uevent_env
kobject: 'spi' (d845db48): fill_kobj_path: path = '/bus/spi'
kobject: 'devices' (d8464788): kobject_add_internal: parent: 'spi', set: '<NULL>'
kobject: 'devices' (d8464788): kobject_uevent_env
kobject: 'devices' (d8464788): kobject_uevent_env: filter function caused the event to drop!
kobject: 'drivers' (d8464908): kobject_add_internal: parent: 'spi', set: '<NULL>'
kobject: 'drivers' (d8464908): kobject_uevent_env
kobject: 'drivers' (d8464908): kobject_uevent_env: filter function caused the event to drop!
bus: 'spi': registered
device class 'spi_master': registering
kobject: 'spi_master' (d8407d08): kobject_add_internal: parent: 'class', set: 'class'
kobject: 'spi_master' (d8407d08): kobject_uevent_env
kobject: 'spi_master' (d8407d08): fill_kobj_path: path = '/class/spi_master'
kobject: 'i2c' (d845dc08): kobject_add_internal: parent: 'bus', set: 'bus'
kobject: 'i2c' (d845dc08): kobject_uevent_env
kobject: 'i2c' (d845dc08): fill_kobj_path: path = '/bus/i2c'
kobject: 'devices' (d8464c88): kobject_add_internal: parent: 'i2c', set: '<NULL>'
kobject: 'devices' (d8464c88): kobject_uevent_env
kobject: 'devices' (d8464c88): kobject_uevent_env: filter function caused the event to drop!
kobject: 'drivers' (d8464e08): kobject_add_internal: parent: 'i2c', set: '<NULL>'
kobject: 'drivers' (d8464e08): kobject_uevent_env
kobject: 'drivers' (d8464e08): kobject_uevent_env: filter function caused the event to drop!
bus: 'i2c': registered
kobject: 'i2c-adapter' (d8466000): kobject_add_internal: parent: 'class', set: '<NULL>'
bus: 'i2c': add driver dummy
kobject: 'dummy' (d845dcc0): kobject_add_internal: parent: 'drivers', set: 'drivers'
kobject: 'dummy' (d845dcc0): kobject_uevent_env
kobject: 'dummy' (d845dcc0): fill_kobj_path: path = '/bus/i2c/drivers/dummy'
omap_mux_init: Add partition: #1: core, flags: 4
Registering platform device 'omap_uart.0'. Parent at omap
device: 'omap_uart.0': device_add
kobject: 'omap_uart.0' (d847b210): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_uart.0
kobject: 'omap_uart.0' (d847b210): kobject_uevent_env
kobject: 'omap_uart.0' (d847b210): fill_kobj_path: path = '/devices/platform/omap/omap_uart.0'
Registering platform device 'omap_uart.1'. Parent at omap
device: 'omap_uart.1': device_add
kobject: 'omap_uart.1' (d847b450): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_uart.1
kobject: 'omap_uart.1' (d847b450): kobject_uevent_env
kobject: 'omap_uart.1' (d847b450): fill_kobj_path: path = '/devices/platform/omap/omap_uart.1'
Registering platform device 'omap_uart.2'. Parent at omap
device: 'omap_uart.2': device_add
kobject: 'omap_uart.2' (d847b690): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_uart.2
kobject: 'omap_uart.2' (d847b690): kobject_uevent_env
kobject: 'omap_uart.2' (d847b690): fill_kobj_path: path = '/devices/platform/omap/omap_uart.2'
Registering platform device 'omap_uart.3'. Parent at omap
device: 'omap_uart.3': device_add
kobject: 'omap_uart.3' (d847b8d0): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_uart.3
kobject: 'omap_uart.3' (d847b8d0): kobject_uevent_env
kobject: 'omap_uart.3' (d847b8d0): fill_kobj_path: path = '/devices/platform/omap/omap_uart.3'
Registering platform device 'omap_uart.4'. Parent at omap
device: 'omap_uart.4': device_add
kobject: 'omap_uart.4' (d847bb10): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_uart.4
kobject: 'omap_uart.4' (d847bb10): kobject_uevent_env
kobject: 'omap_uart.4' (d847bb10): fill_kobj_path: path = '/devices/platform/omap/omap_uart.4'
Registering platform device 'omap_uart.5'. Parent at omap
device: 'omap_uart.5': device_add
kobject: 'omap_uart.5' (d847bd50): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_uart.5
kobject: 'omap_uart.5' (d847bd50): kobject_uevent_env
kobject: 'omap_uart.5' (d847bd50): fill_kobj_path: path = '/devices/platform/omap/omap_uart.5'
Registering platform device 'omap_i2c.1'. Parent at omap
device: 'omap_i2c.1': device_add
kobject: 'omap_i2c.1' (d84ae010): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap_i2c.1
kobject: 'omap_i2c.1' (d84ae010): kobject_uevent_env
kobject: 'omap_i2c.1' (d84ae010): fill_kobj_path: path = '/devices/platform/omap/omap_i2c.1'
Registering platform device 'davinci-mcasp.0'. Parent at platform
device: 'davinci-mcasp.0': device_add
kobject: 'davinci-mcasp.0' (c05a6c98): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device davinci-mcasp.0
kobject: 'davinci-mcasp.0' (c05a6c98): kobject_uevent_env
kobject: 'davinci-mcasp.0' (c05a6c98): fill_kobj_path: path = '/devices/platform/davinci-mcasp.0'
Registering platform device 'mmci-omap-hs.0'. Parent at platform
device: 'mmci-omap-hs.0': device_add
kobject: 'mmci-omap-hs.0' (d84ae250): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device mmci-omap-hs.0
kobject: 'mmci-omap-hs.0' (d84ae250): kobject_uevent_env
kobject: 'mmci-omap-hs.0' (d84ae250): fill_kobj_path: path = '/devices/platform/mmci-omap-hs.0'
Registering platform device 'mmci-omap-hs.1'. Parent at platform
device: 'mmci-omap-hs.1': device_add
kobject: 'mmci-omap-hs.1' (d84ae490): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device mmci-omap-hs.1
kobject: 'mmci-omap-hs.1' (d84ae490): kobject_uevent_env
kobject: 'mmci-omap-hs.1' (d84ae490): fill_kobj_path: path = '/devices/platform/mmci-omap-hs.1'
Registering platform device 'omap2-nand.0'. Parent at platform
device: 'omap2-nand.0': device_add
kobject: 'omap2-nand.0' (c05bbde0): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device omap2-nand.0
kobject: 'omap2-nand.0' (c05bbde0): kobject_uevent_env
kobject: 'omap2-nand.0' (c05bbde0): fill_kobj_path: path = '/devices/platform/omap2-nand.0'
Registering platform device 'ti81xx-usbss'. Parent at omap
device: 'ti81xx-usbss': device_add
kobject: 'ti81xx-usbss' (d84ae6d0): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device ti81xx-usbss
kobject: 'ti81xx-usbss' (d84ae6d0): kobject_uevent_env
kobject: 'ti81xx-usbss' (d84ae6d0): fill_kobj_path: path = '/devices/platform/omap/ti81xx-usbss'
Registering platform device 'hdmi-dai'. Parent at platform
device: 'hdmi-dai': device_add
kobject: 'hdmi-dai' (c05baff8): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device hdmi-dai
kobject: 'hdmi-dai' (c05baff8): kobject_uevent_env
kobject: 'hdmi-dai' (c05baff8): fill_kobj_path: path = '/devices/platform/hdmi-dai'
Registering platform device 'hdmi-dummy-codec'. Parent at platform
device: 'hdmi-dummy-codec': device_add
kobject: 'hdmi-dummy-codec' (c05bb128): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device hdmi-dummy-codec
kobject: 'hdmi-dummy-codec' (c05bb128): kobject_uevent_env
kobject: 'hdmi-dummy-codec' (c05bb128): fill_kobj_path: path = '/devices/platform/hdmi-dummy-codec'
hw-breakpoint: debug architecture 0x4 unsupported.
hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
Registering platform device 'omap-mailbox'. Parent at platform
device: 'omap-mailbox': device_add
kobject: 'omap-mailbox' (c05a74c0): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device omap-mailbox
kobject: 'omap-mailbox' (c05a74c0): kobject_uevent_env
kobject: 'omap-mailbox' (c05a74c0): fill_kobj_path: path = '/devices/platform/omap-mailbox'
Registering platform device 'omap2_mcspi.1'. Parent at platform
device: 'omap2_mcspi.1': device_add
kobject: 'omap2_mcspi.1' (c05a7698): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device omap2_mcspi.1
kobject: 'omap2_mcspi.1' (c05a7698): kobject_uevent_env
kobject: 'omap2_mcspi.1' (c05a7698): fill_kobj_path: path = '/devices/platform/omap2_mcspi.1'
Registering platform device 'omap2_mcspi.2'. Parent at platform
device: 'omap2_mcspi.2': device_add
kobject: 'omap2_mcspi.2' (c05a77c8): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device omap2_mcspi.2
kobject: 'omap2_mcspi.2' (c05a77c8): kobject_uevent_env
kobject: 'omap2_mcspi.2' (c05a77c8): fill_kobj_path: path = '/devices/platform/omap2_mcspi.2'
Registering platform device 'omap2_mcspi.3'. Parent at platform
device: 'omap2_mcspi.3': device_add
kobject: 'omap2_mcspi.3' (c05a78f8): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device omap2_mcspi.3
kobject: 'omap2_mcspi.3' (c05a78f8): kobject_uevent_env
kobject: 'omap2_mcspi.3' (c05a78f8): fill_kobj_path: path = '/devices/platform/omap2_mcspi.3'
Registering platform device 'omap2_mcspi.4'. Parent at platform
device: 'omap2_mcspi.4': device_add
kobject: 'omap2_mcspi.4' (c05a7a28): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device omap2_mcspi.4
kobject: 'omap2_mcspi.4' (c05a7a28): kobject_uevent_env
kobject: 'omap2_mcspi.4' (c05a7a28): fill_kobj_path: path = '/devices/platform/omap2_mcspi.4'
Registering platform device 'omap2_elm.1'. Parent at omap
device: 'omap2_elm.1': device_add
kobject: 'omap2_elm.1' (d84ae910): kobject_add_internal: parent: 'omap', set: 'devices'
bus: 'platform': add device omap2_elm.1
kobject: 'omap2_elm.1' (d84ae910): kobject_uevent_env
kobject: 'omap2_elm.1' (d84ae910): fill_kobj_path: path = '/devices/platform/omap/omap2_elm.1'
Registering platform device 'arm-pmu.0'. Parent at platform
device: 'arm-pmu.0': device_add
kobject: 'arm-pmu.0' (c05a7b58): kobject_add_internal: parent: 'platform', set: 'devices'
bus: 'platform': add device arm-pmu.0
kobject: 'arm-pmu.0' (c05a7b58): kobject_uevent_env
kobject: 'arm-pmu.0' (c05a7b58): fill_kobj_path: path = '/devices/platform/arm-pmu.0'
С чем может быть связано данное зависание или хотя бы в какую сторону копать?
Были испробованы разные настройки памяти, разные варианты конфигурации ядра, результат не изменяется.
Jury093
Пункты: 54271
Регистрация: 25.05.2009
Пол: Мужчина
Из: Санкт-Петербург
Код kobject: 'arm-pmu.0' (c05a7b58): kobject_uevent_env
kobject: 'arm-pmu.0' (c05a7b58): fill_kobj_path: path = '/devices/platform/arm-pmu.0'
и на этом все или что-то дальше есть?
обычно ядро крешится с диагностикой или догружается и ругается на отсутствие накопителя с рутовой..
проверьте, что ваша схема подключена в соответствие с пинами, которые интятся - хотя бы для отладочного порта и mmc/sd карты
для пробы можно вставить в функцию инита борды отладочные printk, чтобы убедится, что дело доходит до инита периферии..
типовой лог загрузки выглядит примерно так:
http://starterkit.ru/html/index.php?name=forum&op=view&id=19949#19949
На любой вопрос есть любой ответ.
Ska1006
Пункты: 163
Регистрация: 01.11.2015
Пол: Мужчина
Из: Москва
Я закоментировал процедуры инициализации неиспользуемого оборудования в файле arch/arm/mach-omap2/devices.c и проблема решилась.
Код
static int __init omap2_init_devices(void)
{
/*
* please keep these calls, and their implementations above,
* in alphabetical order so they're easier to sort through.
*/
printk("[SKA1006][omap2_init_devices(void)]");
omap_hsmmc_reset();
#if !defined(CONFIG_ARCH_TI81XX)
omap_init_audio();
#endif
omap_init_camera();
omap_init_mbox();
omap_init_mcspi();
omap_init_elm();
omap_init_pmu();
omap_hdq_init();
omap_init_sti();
omap_init_sham();
omap_init_aes();
omap_init_vout();
#ifdef CONFIG_ARCH_TI81XX
//if (cpu_is_ti814x()) {
/* Init PCIe,SATA PLL here, before invoking respective init*/
// ti814x_pcie_pllcfg();
// ti814x_sata_pllcfg();
//}
ti81xx_ethernet_init();
//ti81xx_init_pcie();
ti81xx_register_edma();
ti81xx_init_pcm();
ti816x_sr_init();
ti81xx_video_mux();
#ifdef CONFIG_ARCH_TI814X
ti814x_enable_i2c2();
ti814x_d_can_init(0);
// ti814x_d_can_init(1);
#endif
#ifdef CONFIG_MTD_CFI
// ti814x_nor_init();
#endif
#endif
// omap_init_ahci();
#ifdef CONFIG_ARCH_TI81XX
ti81xx_rtc_init();
#endif
return 0;
}
Появились следующие проблемы
Вывод при загрузке с mmc:
Код
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (root@DM8148-bld) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #128 Wed Nov 18 16:26:48 FET 2015
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
reserved size = 52428800 at 0x0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 3.0
SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 30126
Kernel command line: console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=169M@0x80000000 vmaloc=500M notifyk.vpssm3_sva=0xBF900000 noinitrd
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 119MB = 119MB total
Memory: 114608k/114608k available, 58448k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xcb000000 - 0xf8000000 ( 720 MB)
lowmem : 0xc0000000 - 0xca900000 ( 169 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc003a000 ( 200 kB)
.text : 0xc003a000 - 0xc0513000 (4964 kB)
.data : 0xc0514000 - 0xc055ba00 ( 287 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:375
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ368
Trying to install interrupt handler for IRQ369
Trying to install interrupt handler for IRQ370
Trying to install interrupt handler for IRQ371
Trying to install interrupt handler for IRQ372
Trying to install interrupt handler for IRQ373
Trying to install interrupt handler for IRQ374
Trying to install type control for IRQ375
Trying to set irq flags for IRQ375
OMAP clockevent source: GPTIMER1 at 20000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
registered ti81xx_vin device
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea2080b
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
tps65910 1-002d: read from reg 3f failed
tps65910 1-002d: read from reg 1e failed
set_machine_constraints: failed to enable VRTC
tps65910 1-002d: failed to register tps65910-pmic regulator
tps65910-pmic: probe of tps65910-pmic failed with error -121
tps65910 1-002d: No interrupt support, no core IRQ
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at cb01e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at cb028800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 223
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
omap2-nand driver initializing
ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Creating 6 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "U-Boot-min"
0x000000020000-0x000000080000 : "U-Boot"
0x000000080000-0x0000000a0000 : "U-Boot Env"
0x0000000a0000-0x0000004e0000 : "Kernel"
0x0000004e0000-0x000001000000 : "Safe kernel (initramfs)"
0x000001000000-0x000010000000 : "File System"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffff5
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver RTL821x Gigabit Ethernet
davinci_mdio davinci_mdio.0: phy[3]: device 0:03, driver RTL821x Gigabit Ethernet
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
rtc-pcf8563 1-0051: chip found, driver version 0.4.3
rtc-pcf8563 1-0051: rtc core: registered rtc-pcf8563 as rtc1
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
mmc0: mmc_rescan: trying to init card at 400000 Hz
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbf900000
usbcore: registered new interface driver snd-usb-audio
AIC23 Audio Codec 0.1
tlv320aic23_write cannot write 000 to register R15
tlv320aic23_write cannot write 047 to register R6
tlv320aic23_write cannot write 004 to register R5
tlv320aic23_write cannot write 117 to register R0
tlv320aic23_write cannot write 117 to register R1
tlv320aic23_write cannot write 010 to register R4
tlv320aic23_write cannot write 070 to register R2
tlv320aic23_write cannot write 070 to register R3
tlv320aic23_write cannot write 001 to register R9
asoc: tlv320aic23-hifi <-> davinci-mcasp.0 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
#0: TI81XX EVM
IPv4 over IPv4 tunneling driver
GRE over IPv4 demultiplexor driver
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=84:7e:40:8a:9e:de
Detected MACID=84:7e:40:8a:9e:df
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
Waiting for root device /dev/mmcblk0p2...
mmc1: mmc_rescan: trying to init card at 400000 Hz
mmc1: host does not support reading read-only switch. assuming write-enable.
mmc1: new high speed SDHC card at address aaaa
mmcblk0: mmc1:aaaa SU04G 3.69 GiB
mmcblk0: p1 p2
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 200K
Init: mkdir: can't create directory '/mnt/mmcblk0p1': File exists
rm: can't remove '/bin/ip': No such file or directory
Starting logging: OK
Initializing random number generator... done.
Starting network...
CPSW phy found : id is : 0x1cc912
CPSW phy found : id is : 0x1cc912
RTNETLINK answers: No such process
Cannot find device "can0"
Starting dropbear sshd: ipv6: disagrees about version of symbol module_layout
ipv6: disagrees about version of symbol module_layout
OK
Starting sshd: ipv6: disagrees about version of symbol module_layout
OK
Starting wi-fi network ...
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; No such device.
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; No such device.
ifconfig: SIOCSIFADDR: No such device
Loading HDVICP2 Firmware
ipv6: disagrees about version of symbol module_layout
DM814X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
PRCM for IVHD0 is in Progress, Please wait.....
BW Phy Addr : 0x48180600 Data : 0x00000001
AW Phy Addr : 0x48180600 Data : 0x00000002
Phy Addr : 0x48180c04 Data : 0x00000037
BW Phy Addr : 0x48180620 Data : 0x00070000
AW Phy Addr : 0x48180620 Data : 0x00050002
BW Phy Addr : 0x48180624 Data : 0x00030000
AW Phy Addr : 0x48180624 Data : 0x00010002
Phy Addr : 0x48180600 Data : 0x00000102
BW Phy Addr : 0x48180c10 Data : 0x00000007
AW Phy Addr : 0x48180c10 Data : 0x00000003
Phy Addr : 0x48180c14 Data : 0x00000004
BW Phy Addr : 0x58088000 Data : 0x30d09925
AW Phy Addr : 0x58088000 Data : 0xeafffffe
BW Phy Addr : 0x58098000 Data : 0x55619196
AW Phy Addr : 0x58098000 Data : 0xeafffffe
BW Phy Addr : 0x48180c10 Data : 0x00000003
AW Phy Addr : 0x48180c10 Data : 0x00000000
Phy Addr : 0x48180c14 Data : 0x00000007
PRCM for IVHD0 is Done Successfully
PRCM Initialization completed
syslink: disagrees about version of symbol iopgtable_lookup_entry
syslink: Unknown symbol iopgtable_lookup_entry (err -22)
syslink: disagrees about version of symbol iopgtable_clear_entry
syslink: Unknown symbol iopgtable_clear_entry (err -22)
syslink: disagrees about version of symbol __class_create
syslink: Unknown symbol __class_create (err -22)
syslink: disagrees about version of symbol class_destroy
syslink: Unknown symbol class_destroy (err -22)
syslink: disagrees about version of symbol set_user_nice
syslink: Unknown symbol set_user_nice (err -22)
syslink: disagrees about version of symbol clk_get
syslink: Unknown symbol clk_get (err -22)
syslink: disagrees about version of symbol wake_up_process
syslink: Unknown symbol wake_up_process (err -22)
syslink: disagrees about version of symbol iommu_put
syslink: Unknown symbol iommu_put (err -22)
syslink: disagrees about version of symbol device_create
syslink: Unknown symbol device_create (err -22)
syslink: disagrees about version of symbol iopgtable_store_entry
syslink: Unknown symbol iopgtable_store_entry (err -22)
syslink: disagrees about version of symbol iommu_get
syslink: Unknown symbol iommu_get (err -22)
syslink: disagrees about version of symbol device_destroy
syslink: Unknown symbol device_destroy (err -22)
insmod: can't insert '/lib/modules/2.6.37/kernel/drivers/dsp/syslink.ko': Invalid argument
Как видно, ядру не удалось подключить модуль syslink. При этом ядро зависает.
Посмотрел скрипты инициализации(/etc/init.d/ в rootfs) и обнаружил что система встает в цикле ожидая syslink
Скрипт /etc/init.d/S70load-hd-firmware:
Код
#!/bin/sh
#
# manage HDVICP2 and HDVPSS Engine firmware
PATH=$PATH:/usr/share/ti/ti-media-controller-utils
HDVICP2_ID=1
HDVPSS_ID=2
configure_lcd()
{
echo "Configuring fb0 to LCD"
echo 40 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio40/direction
echo 1 > /sys/class/gpio/gpio40/value
# echo 1:dvo2 > /sys/devices/platform/vpss/graphics0/nodes
# echo 0 > /sys/devices/platform/vpss/display1/enabled
# echo 33500,800/164/89/10,480/10/23/10,1 > /sys/devices/platform/vpss/display1/timings
# echo triplediscrete,rgb888 > /sys/devices/platform/vpss/display1/output
# echo 1 > /sys/devices/platform/vpss/display1/enabled
# fbset -xres 800 -yres 480 -vxres 800 -vyres 480
}
case "$1" in
start)
echo "Loading HDVICP2 Firmware"
prcm_config_app s
# modprobe syslink
insmod /lib/modules/2.6.37/kernel/drivers/dsp/syslink.ko
until [[ -e /dev/syslinkipc_ProcMgr && -e /dev/syslinkipc_ClientNotifyMgr ]]
do
sleep 1
done
firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvicp.xem3 start
echo "Loading HDVPSS Firmware"
firmware_loader $HDVPSS_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvpss.xem3 start
modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:1080p-60 mode=dvo2:800x480@60 i2c_mode=1
modprobe ti81xxfb vram=0:24M,1:16M,2:6M
configure_lcd
modprobe ti81xxhdmi
modprobe fbcon
;;
stop)
echo "Unloading HDVICP2 Firmware"
firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvicp.xem3 stop
echo "Unloading HDVPSS Firmware"
rmmod fbcon
rmmod ti81xxhdmi
rmmod ti81xxfb
rmmod vpss
firmware_loader $HDVPSS_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvpss.xem3 stop
rm /tmp/firmware.$HDVPSS_ID
rmmod syslink
;;
*)
echo "Usage: /etc/init.d/load-hd-firmware.sh {start|stop}"
exit 1
;;
esac
exit 0
При удалении данного скрипта ядро нормально загружается.
Что не так может быть c модулем syslink и как это исправить, т.к. хотелось бы использовать DSP?
Еще один вопрос:
Я попытался собрать ядро со встроенyой rootfs(safe_fs).
при этом загрузка выглядит следующим образом:
Код
NAND read: device 0 offset 0x4e0000, size 0xb20000
11665408 bytes read: OK
## Booting kernel from Legacy Image at 81000000 ...
Image Name: Linux-2.6.37
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5507040 Bytes = 5.3 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (root@DM8148-bld) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #127 Wed Nov 18 15:57:11 FET 2015
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
reserved size = 52428800 at 0x0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 3.0
SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 79656
Kernel command line: console=ttyO0,115200n8 ubi.mtd=5 root=ubi0:nandfs rw rootfstype=ubifs mem=364M@0x80000000 324M@0x9F900000 notifyk.vpssm3_sva=0xBF900000 noinitrd
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 314MB = 314MB total
Memory: 305820k/305820k available, 66916k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xd7000000 - 0xf8000000 ( 528 MB)
lowmem : 0xc0000000 - 0xd6c00000 ( 364 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc06b3000 (6828 kB)
.text : 0xc06b3000 - 0xc0b8d000 (4968 kB)
.data : 0xc0b8e000 - 0xc0bd5a00 ( 287 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:375
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ368
Trying to install interrupt handler for IRQ369
Trying to install interrupt handler for IRQ370
Trying to install interrupt handler for IRQ371
Trying to install interrupt handler for IRQ372
Trying to install interrupt handler for IRQ373
Trying to install interrupt handler for IRQ374
Trying to install type control for IRQ375
Trying to set irq flags for IRQ375
OMAP clockevent source: GPTIMER1 at 20000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 598.01 BogoMIPS (lpj=2990080)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
registered ti81xx_vin device
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea2080b
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
tps65910 1-002d: read from reg 3f failed
tps65910 1-002d: read from reg 1e failed
set_machine_constraints: failed to enable VRTC
tps65910 1-002d: failed to register tps65910-pmic regulator
tps65910-pmic: probe of tps65910-pmic failed with error -121
tps65910 1-002d: No interrupt support, no core IRQ
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d701e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d7028800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 597
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
omap2-nand driver initializing
ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Creating 6 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "U-Boot-min"
0x000000020000-0x000000080000 : "U-Boot"
0x000000080000-0x0000000a0000 : "U-Boot Env"
0x0000000a0000-0x0000004e0000 : "Kernel"
0x0000004e0000-0x000001000000 : "Safe kernel (initramfs)"
0x000001000000-0x000010000000 : "File System"
UBI: attaching mtd5 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: max. sequence number: 864
UBI: attached mtd5 to ubi0
UBI: MTD device name: "File System"
UBI: MTD device size: 240 MiB
UBI: number of good PEBs: 1920
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 271
UBI: total number of reserved PEBs: 1649
UBI: number of PEBs reserved for bad PEB handling: 19
UBI: max/mean erase counter: 1/0
UBI: image sequence number: 443988505
UBI: background thread "ubi_bgt0d" started, PID 42
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffff5
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver RTL821x Gigabit Ethernet
davinci_mdio davinci_mdio.0: phy[3]: device 0:03, driver RTL821x Gigabit Ethernet
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
rtc-pcf8563 1-0051: chip found, driver version 0.4.3
rtc-pcf8563 1-0051: rtc core: registered rtc-pcf8563 as rtc1
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
mmc0: mmc_rescan: trying to init card at 400000 Hz
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbf900000
usbcore: registered new interface driver snd-usb-audio
AIC23 Audio Codec 0.1
tlv320aic23_write cannot write 000 to register R15
tlv320aic23_write cannot write 047 to register R6
tlv320aic23_write cannot write 004 to register R5
tlv320aic23_write cannot write 117 to register R0
tlv320aic23_write cannot write 117 to register R1
tlv320aic23_write cannot write 010 to register R4
tlv320aic23_write cannot write 070 to register R2
tlv320aic23_write cannot write 070 to register R3
tlv320aic23_write cannot write 001 to register R9
asoc: tlv320aic23-hifi <-> davinci-mcasp.0 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
#0: TI81XX EVM
IPv4 over IPv4 tunneling driver
GRE over IPv4 demultiplexor driver
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=84:7e:40:8a:9e:de
Detected MACID=84:7e:40:8a:9e:df
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
Warning: unable to open an initial console.
VFS: Cannot open root device "ubi0:nandfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 128 mtdblock0 (driver?)
1f01 384 mtdblock1 (driver?)
1f02 128 mtdblock2 (driver?)
1f03 4352 mtdblock3 (driver?)
1f04 11392 mtdblock4 (driver?)
1f05 245760 mtdblock5 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Backtrace:
[<c06c1bc0>] (dump_backtrace+0x0/0x110) from [<c0a4c560>] (dump_stack+0x18/0x1c)
r7:d3415000 r6:c06e8028 r5:c06a49bc r4:c0bd6210
[<c0a4c548>] (dump_stack+0x0/0x1c) from [<c0a4c5c4>] (panic+0x60/0x17c)
[<c0a4c564>] (panic+0x0/0x17c) from [<c00092b4>] (mount_block_root+0x1e0/0x220)
r3:00000000 r2:00000000 r1:d342bf78 r0:c0b0f27c
[<c00090d4>] (mount_block_root+0x0/0x220) from [<c0009454>] (prepare_namespace+0x94/0x1d4)
[<c00093c0>] (prepare_namespace+0x0/0x1d4) from [<c00087c4>] (kernel_init+0x114/0x154)
r5:c00086b0 r4:c0bd5a00
[<c00086b0>] (kernel_init+0x0/0x154) from [<c06e8028>] (do_exit+0x0/0x5e4)
r5:c00086b0 r4:00000000
Что может быть не так и как собрать ядро с safe_fs правильно?
Jury093
Пункты: 54271
Регистрация: 25.05.2009
Пол: Мужчина
Из: Санкт-Петербург
Цитата При удалении данного скрипта ядро нормально загружается.
Что не так может быть c модулем syslink и как это исправить, т.к. хотелось бы использовать DSP?
а вы модули пересобираете или только ядро? может модули не обновили..
я не помню откуда генерится syslink - поищите в исходниках ядра. если там нет, то гляньте по ссылке:
http://www.starterkit.ru/html/index.php?name=forum&op=view&id=19863&num=2
я "зачем-то" брал его из ezsdk..
Цитата Что может быть не так и как собрать ядро с safe_fs правильно?
я не интересовался темой монолитной сборки, на форуме есть подходящие треды, где описано как правильно настроить ядро и прикрутить рутовую в единый файл..
что у вас бросается в глаза - ядру сказано:
Код root=ubi0:nandfs
рутовой оно там не видит:
Код VFS: Cannot open root device "ubi0:nandfs" or unknown-block(0,0)
и естественно, все валится..
то ли раздел в нанде пустой, то ли номер указан неправильно
существеннее не скажу - не знаю..
PS длинные логи желательно наливать на какой-нить pastebin.com с линком сюда, а то два сообщения и новая страница..
На любой вопрос есть любой ответ.