Other Parts Discussed in Thread: OMAP-L138
Hello! I have a custom board based on OMAP-L138. I'm trying to fight with the kernel and root filesystem from this wiki page:
http://processors.wiki.ti.com/index.php/SmartCard_Implementation_on_OMAPL_PRU_-_Software_Users_Guide
My previos problem was corresponded with not supported in the kernel JTAG IDs. See this link:
http://e2e.ti.com/support/embedded/linux/f/354/p/151835/730059.aspx#730059
Now I'm fighting with filesystem. After building of filesystem and uImage I try to start the board. But with this filesystem I have a problem the kernel init. This is a part of log:
EXT3-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is recommend
ed
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 156K
Kernel panic - not syncing: Attempted to kill init!
Backtrace:
[<c0033628>] (dump_backtrace+0x0/0x114) from [<c033433c>] (dump_stack+0x18/0x1c)
r7:c1420000 r6:c1420000 r5:c1422000 r4:c0442260
[<c0334324>] (dump_stack+0x0/0x1c) from [<c0334394>] (panic+0x54/0x134)
[<c0334340>] (panic+0x0/0x134) from [<c00498c4>] (do_exit+0x74/0x678)
r3:c0426298 r2:c1422000 r1:c1423e50 r0:c03c2482
[<c0049850>] (do_exit+0x0/0x678) from [<c0049f88>] (do_group_exit+0xc0/0xf4)
[<c0049ec8>] (do_group_exit+0x0/0xf4) from [<c0056014>] (get_signal_to_deliver+0
x3bc/0x41c)
r7:c1423ee0 r6:c1423fb0 r5:c1422000 r4:00000004
[<c0055c58>] (get_signal_to_deliver+0x0/0x41c) from [<c00322d8>] (do_notify_resu
me+0x7c/0x640)
[<c003225c>] (do_notify_resume+0x0/0x640) from [<c002ffa8>] (work_pending+0x1c/0
x20)
Also I tryed different uImages. Result is the same. But with my current filesystem all uImages start fine.
Can somebody provide me advice where to find the problem?
Thanks!