firmware loader video.xem3 start - Kernel panic - DM8168

Jonathan Distler

Prodigy 90 points

Hi. I am using TI-EVM*DM8168

I upgraded my sdk from v5.00.00.11 to a newer one, with the following components:

arm_a8_codegen-2009q1_203/

bios-6.32.01.38/

dsp_c6x_codegen-7.2.5/

framework_components-3.21.01.26/

ipc-1.23.03.31/

linux-kernel-2.6.37-psp-04.00.00.12/

linuxutils-3.21.00.04/

osal-1.21.01.08/

syslink-02.00.02.80/

uia-1.00.01.17/

xdais-7.21.00.02/

xdctools-3.22.01.21/

I run the following commands:

1. insmod syslink.ko (load the syslink compiled for the linux kernel i am using)

2. ./firmware_loader 1 video.xem3 start

and the kernel craches with the following errors:

FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.1.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 1 start Successful
root@dm816x-evm:/opt/decoderSim# Unable to handle kernel NULL pointer dereference at virtual address 00000010
pgd = c0004000
[00000010] *pgd=00000000
Internal error: Oops: 17 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: syslink
CPU: 0    Not tainted (2.6.37 #2)
PC is at notify_shmdrv_isr_callback+0x1c/0xac
LR is at notify_shmdrv_video_isr+0x2c/0x3c
pc : [<c02a5c90>]    lr : [<c02a5d88>]    psr: 60000013
sp : c3b7fe88 ip : c3b7fea8 fp : c3b7fea4
r10: 00000004 r9 : c0061750 r8 : 00000004
r7 : 00000000 r6 : 00000000 r5 : 00000000 r4 : 00000000
r3 : 00000004 r2 : 00000009 r1 : 00000004 r0 : 00000000
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
Control: 10c5387d Table: 83b88019 DAC: 00000017
Process kworker/0:2 (pid: 45, stack limit = 0xc3b7e2e8)
Stack: (0xc3b7fe88 to 0xc3b80000)
fe80:                   00000004 00000000 fffffffe 00000000 c3b7febc c3b7fea8
fea0: c02a5d88 c02a5c80 00000000 00000000 c3b7fee4 c3b7fec0 c03694cc c02a5d68
fec0: c04aaae8 c04aaadc 00000004 ffffffff 00000004 00000000 c3b7ff14 c3b7fee8
fee0: c00836d0 c03694a4 00000000 c04addb8 c3b7ff14 c3a90a00 00000004 c3b7ff34
ff00: c04addb8 c3864400 c3b7ff2c c3b7ff18 c0083708 c0083688 00000000 c04ade64
ff20: c3b7ff54 c3b7ff30 c0061798 c00836f4 c036952c 00000004 00000000 c3a90a14
ff40: c04ade64 c3ab4dc0 c3b7ff8c c3b7ff58 c0079a2c c006175c c3b7ff7c 00000000
ff60: c0078ac4 c3ab4dc0 c04addb8 00000009 c04addb8 c04addb8 c3ab4dd0 c3b7e000
ff80: c3b7ffbc c3b7ff90 c007a384 c007984c 00000000 c3b7ffcc c3831ee0 c3ab4dc0
ffa0: c007a1d0 00000000 00000000 00000000 c3b7fff4 c3b7ffc0 c007e684 c007a1dc
ffc0: c3831ee0 00000000 c3ab4dc0 00000000 c3b7ffd0 c3b7ffd0 c3831ee0 c007e5f8
ffe0: c006ace0 00000013 00000000 c3b7fff8 c006ace0 c007e604 ee40e382 40534013
Backtrace:
[<c02a5c74>] (notify_shmdrv_isr_callback+0x0/0xac) from [<c02a5d88>] (notify_shmdrv_video_isr+0x2c/0x3c)
r7:00000000 r6:fffffffe r5:00000000 r4:00000004
[<c02a5d5c>] (notify_shmdrv_video_isr+0x0/0x3c) from [<c03694cc>] (notifier_call_chain+0x34/0x78)
r5:00000000 r4:00000000
[<c0369498>] (notifier_call_chain+0x0/0x78) from [<c00836d0>] (__blocking_notifier_call_chain+0x54/0x6c)
[<c008367c>] (__blocking_notifier_call_chain+0x0/0x6c) from [<c0083708>] (blocking_notifier_call_chain+0x20/0x28)
r8:c3864400 r7:c04addb8 r6:c3b7ff34 r5:00000004 r4:c3a90a00
[<c00836e8>] (blocking_notifier_call_chain+0x0/0x28) from [<c0061798>] (mbox_rx_work+0x48/0xec)
[<c0061750>] (mbox_rx_work+0x0/0xec) from [<c0079a2c>] (process_one_work+0x1ec/0x318)
r6:c3ab4dc0 r5:c04ade64 r4:c3a90a14
[<c0079840>] (process_one_work+0x0/0x318) from [<c007a384>] (worker_thread+0x1b4/0x2d0)
[<c007a1d0>] (worker_thread+0x0/0x2d0) from [<c007e684>] (kthread+0x8c/0x94)
[<c007e5f8>] (kthread+0x0/0x94) from [<c006ace0>] (do_exit+0x0/0x5e4)
r7:00000013 r6:c006ace0 r5:c007e5f8 r4:c3831ee0
Code: e1a06000 f57ff04f e3a04000 e2843004 (e7960103)

FROM THE CODE I'VE BEEN ABLE TO SEE THAT THIS HAPPENS AFTER I CALL ipc_attach() function inside OMX_init() -> Domx_init() -> DomxCore_procInit() ->

any suggestions?

over 13 years ago

0 MUGDHA ARORA over 13 years ago

Genius 4120 points

Hi,

Are you using the appropriate value for notifyk.vpssm3_sva in bootargs?

See here: http://processors.wiki.ti.com/index.php/DM816X_AM389X_VPSS_Video_Driver_User_Guide

Regards,
Mugdha

0 Jonathan Distler over 13 years ago in reply to MUGDHA ARORA

Prodigy 90 points

Thnx Mugdha

I am using DM816x Linux PSP - 04.00.00.12. The link you post is for 04.00.02.14. I think the notifyk.vpssm3_sva doesn't apply.

Also, the crash happens even when loading videom3 bin alone... regardless of the vpss.

Do you have any other clue?

thnx

0 MUGDHA ARORA over 13 years ago in reply to Jonathan Distler

Genius 4120 points

Jonathan,

The reason I mentioned notifyk.vpssm3_sva is that the error message you posted shows that the kernel notify driver is getting used (callstack has notify_shmdrv_isr_callback). So you're using the Linux PSP with kernel notify, but not setting the notifyk.vpssm3_sva. This is ok, and the SysLink notify (through kernel notify) should end up getting used.

But your issue seems to be that the default in SysLink build options for the version you are using (syslink-02.00.02.80) is USE_SYSLINK_NOTIFY is 1, i.e. the kernel notify would not get used, causing a clash between SysLink Notify and kernel notify. If your Linux includes kernel notify, then you need to build SysLink with USE_SYSLINK_NOTIFY=0.

See here: http://e2e.ti.com/support/embedded/linux/f/354/t/138501.aspx

Regards,
Mugdha

0 Jonathan Distler over 13 years ago in reply to MUGDHA ARORA

Prodigy 90 points

Thank you Mugdha.

I saw that post before, and i tried to recompile the linux kernel, but i thought it was related to POSIX options we enabled in it. You are describing a notify option that seems to be inherent inside the kernel, thus, i need to disable the notify inside syslink.

i will try to do that , and let you know what happend :)

thnx

Jonathan

0 Jonathan Distler over 13 years ago in reply to Jonathan Distler

Prodigy 90 points

Mugdha, you are right!

I've defined USE_SYSLINK_NOTIFY = 0 and now everything is fine,

but i am confused. Should we use the notify driver inside syslink or inside the kernel?

See, if I look here: http://processors.wiki.ti.com/index.php/DM816X_C6A816X_AM389X_VPSS_Video_Driver_User_Guide_PSP_04.00.00.12#Read_This_First

they say inside the kernel menu config "[*] Sys_Link ---> " should be ON

What does it mean? How do i turn the kernel notify OFF and leave the syslink?

Obviously the IPC module uses notify to communicate between processors. Which implementation should it use? syslink or kernel's?

Thnx

Jonathan

0 Chris Ring over 13 years ago in reply to Jonathan Distler

TI__Genius 17205 points

This may provide more background:

http://processors.wiki.ti.com/index.php/SysLink_Notify

While SysLink itself supports either setting, some drivers (e.g. the VPSS driver you referenced) may require the system integrator to select one or the other. From that VPSS User Guide, I think you need to configure notify in the kernel (as the doc describes), and therefore build SysLink with USE_SYSLINK_NOTIFY=0.

A final note, as the doc I mention above describes, newer SysLink releases "auto-detect" the setting used when building your kernel and will set USE_SYSLINK_NOTIFY appropriately.

Chris

Processors

Processors forum

firmware loader video.xem3 start - Kernel panic - DM8168