Hi Pavel,
Pardon the dumb questions, and I hope you can straighten me out. Let me answer the questions you asked.
1. I am booting using the NAND memory. The Platform I am using is the DM8127_IPNC_Camera.
2. I am using the TI Linux PSP to make the kernel, and am using the ezsdk for the root filesystem.
3. I have made modifications to allow the DM8148 Kernel to boot on the DM8127 IPNC Camera (I am using the Appro IPNC RDK 3.50 U-boot loader to start booting the Linux PSP Kernel). The reason I am doing that is so I can use the syslink libnotify library and v4l2 drivers, rather than the IPNC iss drivers with different notifications scheme (and no support for the image sensors we want to be using).
4. Everything appears to be working now except for loading the M3 Video Cores, which is where I am having the trouble.
5. Using your init script above, the following is what I get when I attempt to run:
Loading HDVICP2 Firmware
./load-hd-firmware.sh: line 6: prcm_config_app: not found
notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbf900000
SysLink version : 2.21.02.10
SysLink module created on Date:Jan 23 2014 Time:11:00:26
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.1.1
FIRMWARE: Could not open ProcMgr: ProcMgr status 0xfffffffe
Loading HDVPSS Firmware
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.1.1
FIRMWARE: Could not open ProcMgr: ProcMgr status 0xfffffffe
VPSS_FVID2: Unable to get firmware version
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
VPSS_CORE : failed to register ti81xx-vpss driver
FATAL: Error inserting vpss (/lib/modules/2.6.37/kernel/drivers/video/ti81xx/vpss/vpss.ko): No such device
VPSS_FVID2: Unable to get firmware version
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
VPSS_CORE : failed to register ti81xx-vpss driver
Unable to handle kernel paging request at virtual address 6000005b
pgd = c2418000
[6000005b] *pgd=00000000
Internal error: Oops: 805 [#1]
last sysfs file: /sys/module/notifyk/initstate
Modules linked in: syslink notifyk ipv6
CPU: 0 Not tainted (2.6.37 #401)
PC is at serial_omap_irq+0xac/0x610
LR is at __uart_start+0x4c/0x50
pc : [<c0201000>] lr : [<c01f8b4c>] psr: 60000093
sp : c3cabe50 ip : 00000843 fp : c3cabe5c
r10: a0000013 r9 : c461ac00 r8 : 00000000
r7 : c461b076 r6 : 00000076 r5 : 00000000 r4 : 60000013
r3 : c0200a24 r2 : c45ac000 r1 : 000007cd r0 : c45ac000
Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c5387d Table: 82418019 DAC: 00000015
Process modprobe (pid: 931, stack limit = 0xc3caa2e8)
Stack: (0xc3cabe50 to 0xc3cac000)
be40: c3cabe74 c3cabe60 c01f8b68 c01f8b0c
be60: 00000843 c450a400 c3cabea4 c3cabe78 c01faae8 c01f8b5c c01faa20 c461ac00
be80: 00000077 c461b000 c3caa000 c47c5900 c461b000 c461af88 c3cabef4 c3cabea8
bea0: c01e482c c01faa2c c3cabec4 c461ace8 c3cabef4 00000000 c3d722c0 c0066ba0
bec0: c461ace8 c461ace8 c03453f8 c461ac00 00000077 c47c5900 c3caa000 00000077
bee0: 0001b538 00000077 c3cabf3c c3cabef8 c01e1cb0 c01e45f4 c00391f4 c01e45e8
bf00: c3cbc0c0 00000000 c00c2298 c00c2130 00000000 00000077 c47c5900 0001b538
bf20: c3cabf70 00000077 c3caa000 00000000 c3cabf6c c3cabf40 c00c5ea8 c01e1b2c
bf40: 40315000 c003e9c8 c4401284 c47c5900 0001b538 00000000 00000000 00000077
bf60: c3cabfa4 c3cabf70 c00c612c c00c5df8 00000000 00000000 c3cabfa4 00000000
bf80: c00b8258 00000077 0001b538 4025d688 00000004 c0043548 00000000 c3cabfa8
bfa0: c00433a0 c00c60f4 00000077 0001b538 00000002 0001b538 00000077 00000000
bfc0: 00000077 0001b538 4025d688 00000004 00000077 beb93c34 0001b538 beb93c34
bfe0: 0001b538 beb93870 4019bc70 401ebabc 60000010 00000002 e5901054 e5812000
Backtrace:
[<c01f8b00>] (__uart_start+0x0/0x50) from [<c01f8b68>] (uart_start+0x18/0x20)
[<c01f8b50>] (uart_start+0x0/0x20) from [<c01faae8>] (uart_write+0xc8/0xd4)
r4:c450a400 r3:00000843
[<c01faa20>] (uart_write+0x0/0xd4) from [<c01e482c>] (n_tty_write+0x244/0x3b4)
[<c01e45e8>] (n_tty_write+0x0/0x3b4) from [<c01e1cb0>] (tty_write+0x190/0x230)
[<c01e1b20>] (tty_write+0x0/0x230) from [<c00c5ea8>] (vfs_write+0xbc/0x148)
[<c00c5dec>] (vfs_write+0x0/0x148) from [<c00c612c>] (sys_write+0x44/0x70)
r8:00000077 r7:00000000 r6:00000000 r5:0001b538 r4:c47c5900
[<c00c60e8>] (sys_write+0x0/0x70) from [<c00433a0>] (ret_fast_syscall+0x0/0x30)
r8:c0043548 r7:00000004 r6:4025d688 r5:0001b538 r4:00000077
Code: 00000000 00000000 00000000 00000000 (e5843048)
---[ end trace 5d3df142158c23eb ]---
Please keep in mind that this is a DM8127 although I found a page that showed very slight differences between a DM8127 and a DM8148 that I don't believe should be significant.
So what glaring things have I done wrong?
And please don't try to convince to use the IPNC RDK 3.50 linux on the system as it has proven to us that it will never accommodate anything but the sensors Appro uses in their cameras. (We spent months fumbling with IPNC RDK 3.50 and have gotten nowhere with it).