• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 543 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Running VC3 application in 8168 New SDK 5_02_01_59

Nitish James
Intellectual 480 points

Hi all,

We are  trying run vc3 application using new SDK version 5_02_01_59.

Steps used for running:-

./prcm_config_app s
insmod syslink.ko
./firmware_loader 1 vc3_m3video_debug.xem3 start mm_dm81xxbm_vc3.bin
./firmware_loader 2 vc3_m3vpss_debug.xem3 start mm_dm81xxbm_vc3.bin
insmod vpss.ko sbufaddr=0xbfb00000 i2c_mode=1
insmod ti81xxhdmi.ko
insmod ti81xxfb.ko
./vc3_a8host_debug.xv5T 127.0.0.1 2000 60

We are getting a kernel crash and the log is attached.4073.vc3_log.txt

The kernel crash that I mentioned is happening after loading Video-M3 image.
It is crashing in notify_shmdrv_isr_callback() when called from notify_shmdrv_video_isr.
This is because the notify_shm_drv_create(which internally gets called from notify_attach()) is not getting called for Video-M3.
 
notify_shm_drv_create is getting called with the following condition and notify_map_info[i].actualAddress in the following conditional check

is always 0 for Video-M3 since we are not giving any value to notifyk.videom3_sva in the kernel parameter. But for VPSS-M3 it is getting called since notifyk.vpssm3_sva=0xbf900000 is given in bootargs.
                if (i != multiproc_self()
                        && notify_map_info[i].actualAddress != 0) {

Interestingly Mailbox event is coming only for Video-M3 when loading the firmware. There is no such event for VPSS-M3
Is this the expected behaviour?
 
When I am giving an extra parameter in bootargs to initialize notifyk.videom3_sva to 0xbf900000 firmware loading is happening without any crash.
In this case application is hanging in omx_ilclient_utl_comp_create.
 
It looks like VPSS-M3 is not giving notification to the OMX command.
 
We have done all the step as the document and rebuild all the images(kernel image, modules, syslink, vc3 binaries).
 
Please suggest how we can proceed.
 
Thanks and Regards,
Nitish James

  • 0
    TI__Mastermind 18260 points

    Just a guess here...

    Have you built your syslink.ko SysLink kernel module with the parameter USE_SYSLINK_NOTIFY=0?

    I ask because you have the Linux kernel 'notify' module enabled, and SysLink contains its own Notify module which clashes with the Linux one.  Your kernel crashes look similar to the crash that occurs when both Linux's and SysLink's "notify" functionality is enabled simultaneously.

    But I'm just "guessing" because I see that you have Linux 'notify' errors during your bootup, before syslink.ko is even installed, so perhaps you just have a general Linux 'notify' problem.

    Either way, please ensure that you built syslink.ko with USE_SYSLINK_NOTIFY=0 on the 'make' command line.  By default it is 1, causing the clash if the Linux 'notify' module is enabled.

    Or, you could upgrade to SysLink 2.03.00.82 which contains automatic detection of the Linux 'notify' module and configures SysLink accordingly.

    Regards,

    - Rob

     

  • 0 in reply to Robert Tivy
    Intellectual 480 points

    Rob,

    It works with that change.

    Thank you very much for your proactive support.

    Regards,

    Nitish James