• State Resolved
  • Locked Locked
  • Replies 23 replies
  • Subscribers 101 subscribers
  • Views 1616 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.

Problem faced while running VC Demo on DM814x

Sudeep Hegde
Intellectual 660 points

Other Parts Discussed in Thread: PCF8575, PMP

Hi,

I am running the VC demo on DM814x .

The VC Daughter card is connected to DM814x EVM with HDMI input from the Blu-Ray player 1080P@60 fps,
as required for this VC demo package.

We are using SD card boot, The followingis the problem faced while running this demo package:
1. When we are loding HDMI support module (insmod TI81xx_HDMI.ko hdmi_mode=2) in 1080P60 mode, a segmentation fault is observed.
2. The loading of vc_a8host_debug.xv5T application loads the video module, but when loading the vpss module it hangs at:
   [t=0x006f0057] [tid=0x4001b000] ipc_support_desc: Doing Ipc_CONTROLCMD_STARTCALLBACK()
  
Please provide your inputs for resolving the same.

Boot Arguments Used:

mmc init
setenv bootargs 'console=ttyO0,115200n8 root=/dev/mmcblk0p2 rootdelay=2 rw rootfstype=ext3 mem=128M ip=10.1.115.199 vram=50M'
fatload mmc 1 0x81000000 uImage
bootm 0x81000000

Logs:

root@dm814x-evm:/ti814x-evm# insmod syslink.ko
SysLink version : 02.00.00.67_alpha2
SysLink module created on Date:Aug  9 2011 Time:19:13:06
Entered KnlUtilsDrv_initializeModule
traceMask value: 0x0
Leaving KnlUtilsDrv_initializeModule 0x0
root@dm814x-evm:/ti814x-evm# ./prcm_config_app s
/dev/mem opened.
Doing GEL setting...
CortxA8: Output:        PRCM for IVHD0 is in Progress, Please wait.....
             BW Phy Addr : 0x48180600 Data : 0x00000002
             AW Phy Addr : 0x48180600 Data : 0x00000002
             Phy Addr : 0x48180c04 Data : 0x00000037
             BW Phy Addr : 0x48180620 Data : 0x00070000
             AW Phy Addr : 0x48180620 Data : 0x00070002
             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 : 0xceda7c39
             AW Phy Addr : 0x58088000 Data : 0xeafffffe
             BW Phy Addr : 0x58098000 Data : 0xa1fd5a19
             AW Phy Addr : 0x58098000 Data : 0xeafffffe
             BW Phy Addr : 0x48180c10 Data : 0x00000003
             AW Phy Addr : 0x48180c10 Data : 0x00000000
             Phy Addr : 0x48180c14 Data : 0x00000007
CortxA8: Output:        PRCM for IVHD0 is Done Successfully
CortxA8: Output:        User Can Connect to ICONT1 & ICONT2 of IVHD0
CortxA8: Output:        Omx Initialization completed

root@dm814x-evm:/ti814x-evm# insmod TI81xx_HDMI.ko hdmi_mode=2
Unhandled fault: external abort on non-linefetch (0x1008) at 0xc8d3a008
Internal error: : 1008 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: TI81xx_hdmi(+) syslink ipv6
CPU: 0    Not tainted  (2.6.37-rc3 #1)
PC is at ti81xx_hdmi_lib_config+0x160/0xbc4 [TI81xx_hdmi]
LR is at 0x0
pc : [<bf180804>]    lr : [<00000000>]    psr: 40000013
sp : c4bb9e90  ip : 0000001c  fp : c4bb9edc
r10: 00000000  r9 : c4bb8000  r8 : bf182440
r7 : bf181ac7  r6 : bf182580  r5 : bf1825cc  r4 : bf1825ec
r3 : 000fffff  r2 : c8d3a000  r1 : bf182564  r0 : bf182694
Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 10c5387d  Table: 83e74019  DAC: 00000015
Process insmod (pid: 996, stack limit = 0xc4bb82e8)
Stack: (0xc4bb9e90 to 0xc4bba000)
9e80:                                     c4bb8000 00000400 c4bb9ecc c4bb9ea8
9ea0: c0044e84 c0197928 46c00400 00000002 00000002 bf181ac7 bf182440 000fffff
9ec0: bf182564 bf182564 00000000 00000002 c4bb9ef4 c4bb9ee0 bf181328 bf1806b0
9ee0: bf182564 00000000 c4bb9f14 c4bb9ef8 bf181798 bf181300 fa106000 00000000
9f00: bf182288 bf181ac7 c4bb9f44 c4bb9f18 bf185210 bf181724 bf181ac7 c4bb9f28
9f20: c0075218 00000000 bf182440 00012008 00012020 bf185000 c4bb9f7c c4bb9f48
9f40: c00333d8 bf18500c bf182440 00012008 00012020 c003df48 00000000 bf182440
9f60: 00012008 00012020 c003df48 00000000 c4bb9fa4 c4bb9f80 c00846d4 c0033314
9f80: c00af540 c00af458 00000000 00008000 00012020 00000080 00000000 c4bb9fa8
9fa0: c003dda0 c0084644 00000000 00008000 00012020 000043bb 00012008 00000001
9fc0: 00000000 00008000 00012020 00000080 00012008 00000000 00000003 00000000
9fe0: bef20ed9 bef20c6c 00008f5c 401d77d4 60000010 00012020 00000000 00000000
Backtrace:
[<bf1806a4>] (ti81xx_hdmi_lib_config+0x0/0xbc4 [TI81xx_hdmi]) from [<bf181328>] (ti81xx_hdmi_set_mode+0x34/0x38 [TI81xx_hdmi])
 r6:00000002 r5:00000000 r4:bf182564
[<bf1812f4>] (ti81xx_hdmi_set_mode+0x0/0x38 [TI81xx_hdmi]) from [<bf181798>] (ti81xx_hdmi_lib_init+0x80/0xbc [TI81xx_hdmi])
 r5:00000000 r4:bf182564
[<bf181718>] (ti81xx_hdmi_lib_init+0x0/0xbc [TI81xx_hdmi]) from [<bf185210>] (ti81xx_hdmi_init+0x210/0x2c4 [TI81xx_hdmi])
 r7:bf181ac7 r6:bf182288 r5:00000000 r4:fa106000
[<bf185000>] (ti81xx_hdmi_init+0x0/0x2c4 [TI81xx_hdmi]) from [<c00333d8>] (do_one_initcall+0xd0/0x1a4)
 r8:bf185000 r7:00012020 r6:00012008 r5:bf182440 r4:00000000
[<c0033308>] (do_one_initcall+0x0/0x1a4) from [<c00846d4>] (sys_init_module+0x9c/0x1bc)
[<c0084638>] (sys_init_module+0x0/0x1bc) from [<c003dda0>] (ret_fast_syscall+0x0/0x30)
 r7:00000080 r6:00012020 r5:00008000 r4:00000000
Code: e59f1a50 e59f3a54 e5912008 e50b3020 (e5923008)
---[ end trace 04dee5c34b794c90 ]---
Segmentation fault

root@dm814x-evm:/ti814x-evm# ./vc_a8host_debug.xv5T ./out
SDK VC Demo
===+=======
[t=0x00000003] [tid=0x4001b000] ipc_support_desc: Entering ipc_initialize: (void)

[t=0x000000c8] [tid=0x4001b000] ipc_support_desc: filePath = vc_m3video.xem3
[t=0x00000103] [tid=0x4001b000] ipc_support_desc: Doing ProcMgr_open()
[t=0x0000016c] [tid=0x4001b000] ipc_support_desc: Processor state is Unknown
[t=0x000001a4] [tid=0x4001b000] ipc_support_desc: Doing ProcMgr_attach()
[t=0x0000034e] [tid=0x4001b000] ipc_support_desc: Processor state is Powered
[t=0x00000392] [tid=0x4001b000] ipc_support_desc: Doing ProcMgr_load()
[t=0x000003c5] [tid=0x4001b000] ipc_support_desc: Loading Image vc_m3video.xem3

File name being loaded : vc_m3video.xem3
[t=0x00037397] [tid=0x4001b000] ipc_support_desc: Processor state is Loaded
[t=0x00037441] [tid=0x4001b000] ipc_support_desc: Doing Ipc_CONTROLCMD_LOADCALLBACK()
[t=0x0003e9e9] [tid=0x4001b000] ipc_support_desc: Processor state is Loaded
[t=0x0003ea5e] [tid=0x4001b000] ipc_support_desc: Processor state is Loaded
[t=0x0003eaa2] [tid=0x4001b000] ipc_support_desc: Doing ProcMgr_start()
[t=0x0003eb1d] [tid=0x4001b000] ipc_support_desc: Processor state is Running
Before  start cb enter key to continue.................

[t=0x0032bacb] [tid=0x4001b000] ipc_support_desc: Doing Ipc_CONTROLCMD_STARTCALLBACK()
[t=0x0032c914] [tid=0x4001b000] ipc_support_desc: Processor state is Running
SCB completed Running
Enter key to continue.................

[t=0x004705f4] [tid=0x4001b000] ipc_support_desc: Entering ipc_initialize: (void)

[t=0x0047072c] [tid=0x4001b000] ipc_support_desc: Entering ipc_initialize: (void)

[t=0x00470779] [tid=0x4001b000] ipc_support_desc: filePath = vc_m3vpss.xem3
[t=0x004707af] [tid=0x4001b000] ipc_support_desc: Doing ProcMgr_open()
[t=0x00470811] [tid=0x4001b000] ipc_support_desc: Processor state is Unknown
[t=0x00470849] [tid=0x4001b000] ipc_support_desc: Doing ProcMgr_attach()
[t=0x0047092d] [tid=0x4001b000] ipc_support_desc: Processor state is Powered
[t=0x0047096d] [tid=0x4001b000] ipc_support_desc: Doing ProcMgr_load()
[t=0x0047099f] [tid=0x4001b000] ipc_support_desc: Loading Image vc_m3vpss.xem3

File name being loaded : vc_m3vpss.xem3
[t=0x0059952c] [tid=0x4001b000] ipc_support_desc: Processor state is Loaded
[t=0x005995e1] [tid=0x4001b000] ipc_support_desc: Doing Ipc_CONTROLCMD_LOADCALLBACK()
[t=0x00599707] [tid=0x4001b000] ipc_support_desc: Processor state is Loaded
[t=0x00599750] [tid=0x4001b000] ipc_support_desc: Processor state is Loaded
[t=0x00599790] [tid=0x4001b000] ipc_support_desc: Doing ProcMgr_start()
[t=0x005997e8] [tid=0x4001b000] ipc_support_desc: Processor state is Running
Before  start cb enter key to continue.................

[t=0x006f0057] [tid=0x4001b000] ipc_support_desc: Doing Ipc_CONTROLCMD_STARTCALLBACK()

  • 0
    TI__Mastermind 20245 points

    Hi,

    You should load both firmware before doing insmod of hdmi.ko. I think you have loaded only one firmware.

     

    Regards,

    Hardik Shah

  • 0
    TI__Intellectual 2910 points

    Thanks for posting all the details, helps in resolving issues.

     

    Sudeep Hegde said:
    setenv bootargs 'console=ttyO0,115200n8 root=/dev/mmcblk0p2 rootdelay=2 rw rootfstype=ext3 mem=128M ip=10.1.115.199 vram=50M'
    fatload mmc 1 0x81000000 uImage
    bootm 0x81000000

    The mem variable has to be at most 80M. Please modify, reboot and try again.

     

    Archith

  • 0 in reply to HardikShah
    Intellectual 660 points

    Hi Hardik,

    Sorry i didn't get you, Please can you elaborate on the firmware that needed to be loaded before loading HDMI module.

    Regards,

    Sudeep

  • 0 in reply to Sudeep Hegde
    TI__Intellectual 2910 points

    What Hardik meant here is that the vpss m3 executable needs to be loaded before HDMI.ko is inserted. This 'loading' for this version of omx happens inside Omx_init call.

     

    For SDK 5.0.0.26, only off-chip HDMI via DVO2 display has been tested. 

    Archith

  • 0 in reply to Archith John Bency
    Intellectual 660 points

    Hi Archith,

    Thanks for your inputs.

    We had tried  also loading both the video and vpss module before loading the HDMI.

    ./procmgrapp 1 vc_m3video.xem3

    ./procmgrapp 2 vc_m3vpss.xem3

    But while loading on the vpss it hangs..

    Regards,

    Sudeep

  • 0 in reply to Sudeep Hegde
    TI__Intellectual 2910 points

    Sudeep Hegde said:

    ./procmgrapp 1 vc_m3video.xem3

    ./procmgrapp 2 vc_m3vpss.xem3

    You should not be doing this. As in my previous post, the OMX_init call internally proc-loads the slave core executables.

    Please follow the SDK userguide which comes with the installer on the steps to run VC demo and the features supported. From the details you have posted, there are two discrepancies:

     

    1. mem variable in bootargs has to be 80M.

    2. On-chip HMDI is not tested with this SDK release (5.0.0.26). Please use the Off-chip HDMI from the VC daughter card for display.

    Archith

     

     

  • 0 in reply to Sudeep Hegde
    Intellectual 660 points

    Additional Info:

     

    root@dm814x-evm:/ti814x-evm# ./prcm_config_app s

    /dev/mem opened.

    Doing GEL setting...

    CortxA8: Output:        PRCM for IVHD0 is in Progress, Please wait.....

                 BW Phy Addr : 0x48180600 Data : 0x00000002

                 AW Phy Addr : 0x48180600 Data : 0x00000002

                 Phy Addr : 0x48180c04 Data : 0x00000037

                 BW Phy Addr : 0x48180620 Data : 0x00070000

                 AW Phy Addr : 0x48180620 Data : 0x00070002

                 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 : 0xefca7c31

                 AW Phy Addr : 0x58088000 Data : 0xeafffffe

                 BW Phy Addr : 0x58098000 Data : 0xa1fd5a19

                 AW Phy Addr : 0x58098000 Data : 0xeafffffe

                 BW Phy Addr : 0x48180c10 Data : 0x00000003

                 AW Phy Addr : 0x48180c10 Data : 0x00000000

                 Phy Addr : 0x48180c14 Data : 0x00000007

    CortxA8: Output:        PRCM for IVHD0 is Done Successfully

    CortxA8: Output:        User Can Connect to ICONT1 & ICONT2 of IVHD0

    CortxA8: Output:        Omx Initialization completed

    root@dm814x-evm:/ti814x-evm# insmod syslink.ko

    SysLink version : 02.00.00.67_alpha2

    SysLink module created on Date:Aug  9 2011 Time:19:13:06

    Entered KnlUtilsDrv_initializeModule

    traceMask value: 0x0

    Leaving KnlUtilsDrv_initializeModule 0x0

    root@dm814x-evm:/ti814x-evm# ./procmgrapp 1 vc_m3video.xem3

    ProcMgrApp sample application

    Entered SysLinkSamples_startup

    SysLinkSamples_osStartup

    Entered ProcMgrApp_startup

    ProcMgr_attach status: [0x0]

    After attach: ProcMgr_getState

        state [0x1]

    ProcMgr_load status: [0x3046000]

    After load: ProcMgr_getState

        state [0x3]

    ProcMgr_start passed [0x6a85000]

    After start: ProcMgr_getState

        state [0x4]

    ProcMgr_close status: [0x0]

    Leaving ProcMgrApp_startup

    Press enter to continue and perform shutdown ...

    [1] + Stopped                    ./procmgrapp 1 vc_m3video.xem3


    root@dm814x-evm:/ti814x-evm# ./procmgrapp 2 vc_m3vpss.xem3

    ProcMgrApp sample application

    Entered SysLinkSamples_startup

    SysLinkSamples_osStartup

    Entered ProcMgrApp_startup

    ProcMgr_attach status: [0x0]

    After attach: ProcMgr_getState

        state [0x1]

    ProcMgr_load status: [0x3046000]

    After load: ProcMgr_getState

        state [0x3]

    ProcMgr_start passed [0x6a85000]


    it hangs here..

    Rgds,

    Sudeep

  • 0 in reply to Archith John Bency
    Intellectual 660 points

    Hi Archith,

    We tried with seeting it to 80M, but it didn't work.

    Rgds,

    Sudeep

  • 0 in reply to Archith John Bency
    Intellectual 660 points

    Hi Archith,

    We tried with setting it to 80M, but it didn't work.

    Rgds,

    Sudeep

  • 0 in reply to Archith John Bency
    Intellectual 660 points

    Archith John Bency said:

    ./procmgrapp 1 vc_m3video.xem3

    ./procmgrapp 2 vc_m3vpss.xem3

    You should not be doing this. As in my previous post, the OMX_init call internally proc-loads the slave core executables.

    Please follow the SDK userguide which comes with the installer on the steps to run VC demo and the features supported. From the details you have posted, there are two discrepancies:

     

    1. mem variable in bootargs has to be 80M.

    2. On-chip HMDI is not tested with this SDK release. Please use the Off-chip HDMI from the VC daughter card for display.

    Archith

     

     

    [/quote]Hi Archith,

    1. mem variable in bootargs has to be 80M.

    >> We had tried with 80M, but it didn't work.

    2. On-chip HMDI is not tested with this SDK release (5.0.0.26). Please use the Off-chip HDMI from the VC daughter card for display.

    >> We are using the off-chip HDMI only.

    Please let me know the link for the latest VC demo package on DM814x and also if you have the prebuilt binaries.

    Regards,

    Sudeep

     

     

     

  • 0 in reply to Sudeep Hegde
    TI__Intellectual 2910 points

    Please talk you your TI representative on how to get documentation which comes as part of SDK 5.0.0.26. This is an NDA customer release and is not in general availability.

     

    Archith

  • 0 in reply to Archith John Bency
    Intellectual 660 points

    Hi Archith,

     

    We have the required package, Please do let me the build steps..

    1. Build the uImage

    2. Syslink.ko

    3. VPSS

    4. OMX Binaries

     

    Please correct me if i am wrong.

     

    Regards,

    Sudeep

  • 0 in reply to Sudeep Hegde
    TI__Mastermind 20245 points

    Hi,

    You can refer to each components UserGuide and/or installGuide for build steps.

    Regards,

    Hardik Shah

     

     

  • 0 in reply to Sudeep Hegde
    TI__Intellectual 2910 points

    Can you please confirm that you have the document 'SDK_UserGuide.PDF' ? If you do please read the chapter 'INSTALLATION, BUILD AND EXECUTION '.

     

    If you dont have this doc, please contact your TI representative.

     

    Archith

  • 0 in reply to Archith John Bency
    Intellectual 660 points

    Hi Archith,

    We have built the binaries again referring to the 'SDK_UserGuide.PDF' - INSTALLATION, BUILD AND EXECUTION

    But again we saw that it hanged while loading VPSS.

    Same behaviour was observed while running .xv5t.

    Please let us know how to proceed on it.


    Logs:

    ====

    root@dm814x-evm:/binaries# insmod syslink.ko
    SysLink version : 02.00.00.67_alpha2
    SysLink module created on Date:Aug 12 2011 Time:11:19:59
    Entered KnlUtilsDrv_initializeModule
    traceMask value: 0x0
    Leaving KnlUtilsDrv_initializeModule 0x0
    root@dm814x-evm:/binaries# ./prcm_config_app s
    /dev/mem opened.
    Doing GEL setting...
    CortxA8: Output:        PRCM for IVHD0 is in Progress, Please wait.....
                 BW Phy Addr : 0x48180600 Data : 0x00000002
                 AW Phy Addr : 0x48180600 Data : 0x00000002
                 Phy Addr : 0x48180c04 Data : 0x00000037
                 BW Phy Addr : 0x48180620 Data : 0x00070000
                 AW Phy Addr : 0x48180620 Data : 0x00070002
                 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 : 0x8fca7c39
                 AW Phy Addr : 0x58088000 Data : 0xeafffffe
                 BW Phy Addr : 0x58098000 Data : 0xa1fd5a19
                 AW Phy Addr : 0x58098000 Data : 0xeafffffe
                 BW Phy Addr : 0x48180c10 Data : 0x00000003
                 AW Phy Addr : 0x48180c10 Data : 0x00000000
                 Phy Addr : 0x48180c14 Data : 0x00000007
    CortxA8: Output:        PRCM for IVHD0 is Done Successfully
    CortxA8: Output:        User Can Connect to ICONT1 & ICONT2 of IVHD0
    CortxA8: Output:        Omx Initialization completed
    root@dm814x-evm:/binaries# ./procmgrapp 1 /Whole_DebugJ
    /Whole_Debug/vc_a8host_debug.xv5T
    /Whole_Debug/vc_m3video_whole_program_debug.xem3
    /Whole_Debug/vc_m3vpss_whole_program_debug.xem3
    root@dm814x-evm:/binaries# ./procmgrapp 1 /Whole_Debug/vc_m3video_whole_program_
    debug.xem3
    ProcMgrApp sample application
    Entered SysLinkSamples_startup
    SysLinkSamples_osStartup
    Entered ProcMgrApp_startup
    ProcMgr_attach status: [0x0]
    After attach: ProcMgr_getState
        state [0x1]
    ProcMgr_load status: [0x3046000]
    After load: ProcMgr_getState
        state [0x3]
    ProcMgr_start passed [0x6a85000]
    After start: ProcMgr_getState
        state [0x4]
    ProcMgr_close status: [0x0]
    Leaving ProcMgrApp_startup
    Press enter to continue and perform shutdown ...
    [1] + Stopped                    ./procmgrapp 1 /Whole_Debug/vc_m3video_whole_program_debug.xem3
    root@dm814x-evm:/binaries# ./procmgrap/Whol/vc_
    /Whole_Debug/vc_a8host_debug.xv5T
    /Whole_Debug/vc_m3video_whole_program_debug.xem3
    /Whole_Debug/vc_m3vpss_whole_program_debug.xem3
    root@dm814x-evm:/binaries# ./procmgrapp 2 /Whole_Debug/vc_m3vpss_whole_program_d
    ebug.xem3
    ProcMgrApp sample application
    Entered SysLinkSamples_startup
    SysLinkSamples_osStartup
    Entered ProcMgrApp_startup
    ProcMgr_attach status: [0x0]
    After attach: ProcMgr_getState
        state [0x1]
    ProcMgr_load status: [0x3046000]
    After load: ProcMgr_getState0
        state [0x3]
    ProcMgr_start passed [0x6a85000]

  • 0 in reply to Sudeep Hegde
    TI__Intellectual 2910 points

    Please follow the steps within the section:

     

    'Steps to run VC in All cores mode'. All the steps required are described in detail.  I see here that you are trying to independently procload the slave executables and I re-iterate as in my previous post on not to attempt that.

     

    I would advice you to follow exact instructions from the SDK User Guide so that you can baseline your setup first and then start modifying according to your application.

     

    Archith

  • 0 in reply to Archith John Bency
    Intellectual 660 points

    Hi Archith,

    We tried to load directly after building "vc_a8host_debug.xv5T", but we are observing the same i.e it hangs at vpss.

    Please let us know if we are missing something..

    Logs:

    ===

    root@dm814x-evm:~# cd /Whole_Debug/
    root@dm814x-evm:/Whole_Debug# insmod syslink.ko
    SysLink version : 02.00.00.67_alpha2
    SysLink module created on Date:Aug 12 2011 Time:11:19:59
    Entered KnlUtilsDrv_initializeModule
    traceMask value: 0x0
    Leaving KnlUtilsDrv_initializeModule 0x0
    root@dm814x-evm:/Whole_Debug# ./prcm_config_app s
    /dev/mem opened.
    Doing GEL setting...
    CortxA8: Output:        PRCM for IVHD0 is in Progress, Please wait.....
                 BW Phy Addr : 0x48180600 Data : 0x00000002
                 AW Phy Addr : 0x48180600 Data : 0x00000002
                 Phy Addr : 0x48180c04 Data : 0x00000037
                 BW Phy Addr : 0x48180620 Data : 0x00070000
                 AW Phy Addr : 0x48180620 Data : 0x00070002
                 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 : 0xffca7c39
                 AW Phy Addr : 0x58088000 Data : 0xeafffffe
                 BW Phy Addr : 0x58098000 Data : 0xa1f95a19
                 AW Phy Addr : 0x58098000 Data : 0xeafffffe
                 BW Phy Addr : 0x48180c10 Data : 0x00000003
                 AW Phy Addr : 0x48180c10 Data : 0x00000000
                 Phy Addr : 0x48180c14 Data : 0x00000007
    CortxA8: Output:        PRCM for IVHD0 is Done Successfully
    CortxA8: Output:        User Can Connect to ICONT1 & ICONT2 of IVHD0
    CortxA8: Output:        Omx Initialization completed
    root@dm814x-evm:/Whole_Debug# ./vc_a8host_debug.xv5T ./
    SDK VC Demo
    ===+=======
    [t=0x00000004] [tid=0x4008c000] ipc_support_desc: Entering ipc_initialize: (void)

    [t=0x000000c0] [tid=0x4008c000] ipc_support_desc: filePath = vc_m3video.xem3
    [t=0x000000fa] [tid=0x4008c000] ipc_support_desc: Doing ProcMgr_open()
    [t=0x00000162] [tid=0x4008c000] ipc_support_desc: Processor state is Unknown
    [t=0x0000019c] [tid=0x4008c000] ipc_support_desc: Doing ProcMgr_attach()
    [t=0x0000033f] [tid=0x4008c000] ipc_support_desc: Processor state is Powered
    [t=0x00000382] [tid=0x4008c000] ipc_support_desc: Doing ProcMgr_load()
    [t=0x000003b4] [tid=0x4008c000] ipc_support_desc: Loading Image vc_m3video.xem3

    File name being loaded : vc_m3video.xem3
    [t=0x0002f1f8] [tid=0x4008c000] ipc_support_desc: Processor state is Loaded
    [t=0x0002f38f] [tid=0x4008c000] ipc_support_desc: Doing Ipc_CONTROLCMD_LOADCALLBACK()
    [t=0x0003acf3] [tid=0x4008c000] ipc_support_desc: Processor state is Loaded
    [t=0x0003ade0] [tid=0x4008c000] ipc_support_desc: Processor state is Loaded
    [t=0x0003ae28] [tid=0x4008c000] ipc_support_desc: Doing ProcMgr_start()
    [t=0x0003af0d] [tid=0x4008c000] ipc_support_desc: Processor state is Running
    Before  start cb enter key to continue.................

    [t=0x002bd813] [tid=0x4008c000] ipc_support_desc: Doing Ipc_CONTROLCMD_STARTCALLBACK()
    [t=0x002be439] [tid=0x4008c000] ipc_support_desc: Processor state is Running
    SCB completed Running
    Enter key to continue.................

    [t=0x003db235] [tid=0x4008c000] ipc_support_desc: Entering ipc_initialize: (void)

    [t=0x003db360] [tid=0x4008c000] ipc_support_desc: Entering ipc_initialize: (void)

    [t=0x003db3ac] [tid=0x4008c000] ipc_support_desc: filePath = vc_m3vpss.xem3
    [t=0x003db3e2] [tid=0x4008c000] ipc_support_desc: Doing ProcMgr_open()
    [t=0x003db444] [tid=0x4008c000] ipc_support_desc: Processor state is Unknown
    [t=0x003db47d] [tid=0x4008c000] ipc_support_desc: Doing ProcMgr_attach()
    [t=0x003db563] [tid=0x4008c000] ipc_support_desc: Processor state is Powered
    [t=0x003db5a1] [tid=0x4008c000] ipc_support_desc: Doing ProcMgr_load()
    [t=0x003db5d4] [tid=0x4008c000] ipc_support_desc: Loading Image vc_m3vpss.xem3

    File name being loaded : vc_m3vpss.xem3

    [t=0x004c6ff9] [tid=0x4008c000] ipc_support_desc: Processor state is Loaded
    [t=0x004c7145] [tid=0x4008c000] ipc_support_desc: Doing Ipc_CONTROLCMD_LOADCALLBACK()
    [t=0x004c7354] [tid=0x4008c000] ipc_support_desc: Processor state is Loaded
    [t=0x004c7411] [tid=0x4008c000] ipc_support_desc: Processor state is Loaded
    [t=0x004c7456] [tid=0x4008c000] ipc_support_desc: Doing ProcMgr_start()
    [t=0x004c7523] [tid=0x4008c000] ipc_support_desc: Processor state is Running
    Before  start cb enter key to continue.................
    [t=0x004c7613] [tid=0x4008c000] ipc_support_desc: Doing Ipc_CONTROLCMD_STARTCALLBACK()

  • 0 in reply to Sudeep Hegde
    TI__Intellectual 2910 points

    What this error means is that the HDVPSS M3 slave is not responding after being proc-loaded. This could be because it has asserted on some condition and A8 is just waiting for a response. One check on which assertion can happen is whether daughter card is connected properly or not. You can confirm this by changing the main () for HDVPSS and generating xem3 binaries for debug profile (Please look in UserGuide on how to build debug profile builds).

     

    You can  do this in :

    ti\omx\demos\dm814x\vc\src\m3vpss_main.c

    main ()

    {

    int i = 1;

    while (i);

    .

    .

    }

    So, after procload, you can connect via an emulator and CCS  to the HDVPSS-M3 core and you should be looping at this while statement. Modify the value of i to 0 to break out  in the watch window in CCS and then step through to see where exactly HDVPSS-M3 has asserted.

     

    Archith

  • 0 in reply to Archith John Bency
    Intellectual 660 points

    Hi Archit,

    Thanks for your inputs, we will try that out..

    Another input is whether we can run only the H.264 video encoder separately, Have TI provided any demo application for it in the package?

     

    Regards,

    Sudeep

  • 0 in reply to Sudeep Hegde
    TI__Intellectual 2910 points

    We currently dont have a standalone H.264 encode demo based on the SDK version you are using. We do have a relatively simpler capture+encode example in the latest EZSDK release.

    http://software-dl.ti.com/dsps/dsps_public_sw/ezsdk/latest/index_FDS.html

    Please note that that this is supported on the Base EVM +  Catalog Expansion I/O card. This also supports only Standard Non-Tunneled mode of communication vs Proprietary Tunneling mode in the SDK version that you have.

     

    Archith

  • 0 in reply to Archith John Bency
    Prodigy 30 points

    Hi,

    I am using the latest package present in the above package. However I am not able to boot up the board as it hangs. The boot args I have used is 

     

     

    mmc init

    setenv nfsserver 10.1.115.172

    setenv bootargs 'console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.1.115.172:/u/users/nfspt/users/adsouza/adsouza,nolock rw rootdelay=2 rootfstype=ext3 mem=80M ip=10.1.115.199'

    fatload mmc 1 0x81000000 uImage

    bootm 0x81000000

    I am getting the following while booting
    ## Booting kernel from Legacy Image at 81000000 ...
       Image Name:   Arago/2.6.37-psp04.01.00.05/dm81
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2457256 Bytes = 2.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 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Thu Sep 8 16:12:47 IST 2011
    CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: ti8148evm
    reserved size = 52428800 at 0
    FB: Reserving 52428800 bytes SDRAM for VRAM
    Memory policy: ECC disabled, Data cache writeback
    OMAP chip is TI8148 1.0
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 7520
    Kernel command line: console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.1.115.172:/u/users/nfspt/users/adsouza/ezsdk-dm814x-evm-rootfs,nolock rw rootdelay=2 rootfstype=ext3 mem=80M ip=10.1.115.199
    PID hash table entries: 128 (order: -3, 512 bytes)
    Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
    Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
    Memory: 30MB = 30MB total
    Memory: 24764k/24764k available, 57156k reserved, 0K highmem
    Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
        DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
        vmalloc : 0xc5800000 - 0xf8000000   ( 808 MB)
        lowmem  : 0xc0000000 - 0xc5000000   (  80 MB)
        modules : 0xbf000000 - 0xc0000000   (  16 MB)
          .init : 0xc0008000 - 0xc0037000   ( 188 kB)
          .text : 0xc0037000 - 0xc04a6000   (4540 kB)
          .data : 0xc04a6000 - 0xc04e9400   ( 269 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 GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    omap_mux_init: Add partition: #1: core, flags: 4
    registered ti814x_vpss device
    registered TI814x on-chip HDMI device
    pm_dbg_init: only OMAP3 supported
    Registered ti81xx_fb 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
    omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
    pcf857x 1-0021: gpios 128..143 on a pcf8575
    i2c i2c-1: Failed to register i2c client PCF_8575 at 0x21 (-16)
    i2c i2c-1: Can't create device at 0x21
    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
    registerd cppi-dma Intr @ IRQ 17
    Cppi41 Init Done
    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 c580c000 using DMA, IRQ 18
    musb-hdrc musb-hdrc.1: dma type: dma-cppi41
    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 c581e800 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: 1024 (order: 1, 8192 bytes)
    TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
    TCP: Hash tables configured (established 1024 bind 1024)
    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 48
    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
    ahci ahci.0: forcing PORTS_IMPL to 0x1
    ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
    ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
    scsi0 : ahci_platform
    ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
    omap2-nand driver initializing
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
    Creating 6 MTD partitions on "omap2-nand.0":
    0x000000000000-0x000000020000 : "U-Boot-min"
    0x000000020000-0x000000260000 : "U-Boot"
    0x000000260000-0x000000280000 : "U-Boot Env"
    0x000000280000-0x0000006c0000 : "Kernel"
    0x0000006c0000-0x00000cee0000 : "File System"
    0x00000cee0000-0x000010000000 : "Reserved"
    davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
    davinci_mdio davinci_mdio.0: detected phy mask fffffffd
    davinci_mdio.0: probed
    davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
    usbcore: registered new interface driver cdc_ether
    usbcore: registered new interface driver dm9601
    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
    qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
    qt602240_ts: probe of 1-004a failed with error -5
    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
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    usbcore: registered new interface driver snd-usb-audio
    asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
    ALSA device list:
      #0: TI81XX EVM
    TCP cubic registered
    NET: Registered protocol family 17
    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
    Detected MACID=0:0:0:0:0:0
    ata1: SATA link down (SStatus 0 SControl 300)
    mmc0: new high speed SDHC card at address b368
    mmcblk0: mmc0:b368 00000 7.51 GiB
     mmcblk0: p1 p2
    CPSW phy found : id is : 0x282f014
    IP-Config: Guessing netmask 255.0.0.0
    IP-Config: Complete:
         device=eth0, addr=10.1.115.199, mask=255.0.0.0, gw=255.255.255.255,
         host=10.1.115.199, domain=, nis-domain=(none),
         bootserver=255.255.255.255, rootserver=10.1.115.172, rootpath=
    Waiting 2sec before mounting root device...
    PHY: 0:01 - Link is Up - 100/Full
    VFS: Mounted root (nfs filesystem) on device 0:14.
    devtmpfs: mounted
    Freeing init memory: 188K
    request_module: runaway loop modprobe binfmt-0000
    request_module: runaway loop modprobe binfmt-0000
    request_module: runaway loop modprobe binfmt-0000
    request_module: runaway loop modprobe binfmt-0000
    request_module: runaway loop modprobe binfmt-0000
    Can somebody help me out in this?
    Thanks and regards,
    Amith
  • 0 in reply to Archith John Bency
    Intellectual 660 points

    Hi Archit,

    The problem is resolved.

    The problem was due to the connection of daughter card to the base EVM, as it needs to be tightly coupled - i2c bus connection not established correctly. After that the VPSS module was not hanging..

    Thanks for your inputs.

    Regards,

    Sudeep

  • 0 in reply to Sudeep Hegde
    Intellectual 660 points

    Hi Archit,

     

    One more problem we are observing, After loading the .xv5t the video and vpss module is loaded correctly.

    But we are seeing a white screen on the output connected to Tx HDMI port.. the Rx HDMI port is connected to Blu-Ray player.

    (Checked with both 720p and 1080p input to off chip HDMI)

    Please let us know your input on this..

     

    Logs:

    Wait for VM3 to to create the server first
    Entering : OMX_HDVPSS_MicroChain_Test
    You could Connect CCS Now:: Press any key to continue:
    VFCC:0
    VFDC:0
    VFPC_DEI:0
    VFPC_SCWB:0

     Encode: got the component handle
    OMX_IndexParamVideoProfileLevelCurrent Getparam done for enc!!
    OMX_IndexParamVideoProfileLevelCurrent Setparam done for enc!!
    OMX_TI_IndexParamVideoBitStreamFormatSelect Getparam done for enc!!
    OMX_TI_IndexParamVideoBitStreamFormatSelect Setparam done for enc!!
    OMX_TI_IndexParamVideoEncoderPreset Getparam done for enc!!
    OMX_TI_IndexParamVideoEncoderPreset Setparam done for enc!!
    OMX_TI_IndexParamVideoFrameDataContentSettings Getparam done for enc!!
    OMX_TI_IndexParamVideoFrameDataContentSettings Setparam done for enc!!
    OMX_TI_IndexParamVideoTransformBlockSize Getparam done for enc!!
    OMX_TI_IndexParamVideoTransformBlockSize Setparam done for enc!!
    Entering H264ENC_SetParamsFromInitialDynamicParams!!
    Exited H264ENC_SetParamsFromInitialDynamicParams!!
    VFPC_VENC_H264:0
    VFPC_VDEC_H264:0

     VFCC Component Transitioned to Idle state
     CTRLTVP Component Transitioned to Idle state
     VFPCDEI_0 Component Transitioned to Idle state
     VENC_0 Component Transitioned to Idle state
     VDEC_0 Component Transitioned to Idle state
     INDTXSC Component Transitioned to Idle state
     CTRLDC_0 Component Transitioned to Idle state
     VFDC_0 Component Transitioned to Idle state
     CTRLDC_0 Component Transitioned to Executing state
     VFDC_0 Component Transitioned to Executing state
     INDTXSC Component Transitioned to Executing state
     VDEC_0 Component Transitioned to Executing state
     VENC_0 Component Transitioned to Executing state
     VFPCDEI_0 Component Transitioned to Executing state
     CTRLTVP Component Transitioned to Executing state
     VFCC Component Transitioned to Executing state

     

    Regards,

    Sudeep