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.

Delay in loading VPSS firmware

Other Parts Discussed in Thread: AM3874

I am trying to emulate (as closely as possible) the AM3874 part on my TI8148 EVM, which is running the latest 5.04 EZSDK.  Therefore I commented out the section of load-hd-firmware.sh which loads the firmware for the HDVICP.  However if I do this when the load_firmware command for the VPSS executes it takes about 5 seconds to complete.

Is there something else you have to change to make loading the VPSS by itself run quicker?  The latest syslink (2.10.05.26) mentions in its release notes that a bug was fixed that seemed relevant "Ipc_control start callback takes too long".  Using strace on load_firmware seems to point to this section of code being the place where the delay occurs but when I upgraded syslink the delay still exists.

If this delay doesn't occur on the actual AM3874 part then it isn't a big deal but since I don't have one of those I thought I would ask.  Thanks for the help.

  • Adam

    As per my understanding the ducati side code never work if you commented out the section of load-hd-firmware.sh which loads the firmware for the HDVICP (video _M3).  There will be Ipc attach with each core and it will be waiting for  this to happen with Video M3 and that never happen as you did not load video M3 binaries.  To get your app working properly we need to modify the ducati side code to exclude the video-M3 from IPC attach.  As I am not very familiar with the modified proc loader used in EZSDK, Velan might be the right person here to help you on this

     

    Velan,

    Can you please help Adam on this query?

     

    Regards, shiju

  • To add to Shiju's point, when the firmware is loaded, it will try to perform handshake to each of the other cores in the SoC by invoking Ipc_attach. Control of which cores to handshake is determined by _build_ time configuration. From your description it looks like firmware is trying to perform Ipc_attach with video_M3 and timesout. As far as I know timeout is usually FOREVER so it is surprising that you get a callback after 5 mins. This points to a S/W configuration issue rather than a device issue. Shiju and I are not familiar with the EZSDK configuration  .Probably Velan can comment on whether Ipc_attach with Video M3 is enabled by default in the build. To debug this issue further we would need logs on the firmware side to confirm what is stalling VPSS M3. Would it be possible to enable logs on VPSS M3 and send the trace. If you have the abilty to connect JTAG/CCS that would be the quickest way to determine what is stalling VPSS M3.

  • Jason,

              The point mentioned by Shiju & Badri are correct. The VPSS-M3 binary by default does IPC_attach with Video-M3. So it mandates Video-M3 also to be loaded.

              You will have to modify VPSS-M3 to remove this & modify load-hd-firmware.sh in order not to load Video-M3.

              The other option is to look at the HDVPSS-M3 standalone firmware, present in HDVPSS driver component if you are not using any of the OMX components.

    Thanks & Regards,

    Velan

  • Hi Velan ,

    I am trying to debug  HDVPSS capture driver to solve some issue in the OMX application . For debugging in CCS setup ,i am loading the both HDVICP and HDVPSS firmware using firmware_loader binary ,while the system is booting . I have included a while loop in the main function of HDVPSS firmware for debugging .

    When i connect VPSS-M3 in CCS and load the symbols ,i see that VPSS-M3 is going into Load_idleFxn()  and its not coming out of that . Debugging more i found out it enters into DomxCore_procAttach() and trying to do ipc_attach() with the other cores .

    What should i do to make the VPSS-M3 core not to do ipc_attach() with the other cores ? Should i comment out the code where its doing ipc_attach () with the other cores or connect the Video-M3 core also .

    I am confused who is the master core in this case ? Can you help me to understand the problem clearly ?

    Thanks,

    Siva .

  • Siva,

           I do not think comment out ipc_attach() is the right solution, without understanding the impact. But in case Video-M3 or DSP not running, it is right to remove IPC_attach with those cores.

           Details on IPC_attach behavior is documented in section "Ipc Module Configuration" in document component-sources\ipc_<Rel-Id>\docs\IPC_Users_Guide.pdf

           The other thing we must be aware in this regard is the MultiProcId which is documented in section "MultiProc Module" in the same doc

    Thanks & Regards,
    Velan

  • Hi Velan ,

    Thanks for the reply . I am loading only VPSS-M3 firmware but not Video-M3 firmware while the board is booting . I have included a while loop in the main function of VPSS-M3 firmware for debugging .

    Loading HDVPSS Firmware
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments===
    <Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
    <Location of Firmware> firmware binary file
    <start|stop>           to start/stop the firmware
    ===Optional arguments===
    -mmap                  input memory map bin file name
    -i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
    *** Platform_startCallback: Ipc_attach timeout
            Error [0xffffffff] at Line no: 2828 in file /home/siva/ezsdk_5_04/component-sources/syslink_2_10_03_20/packages/ti/sc
    *** Ipc_control: Platform_startCallback failed!
            Error [0xffffffff] at Line no: 852 in file /home/siva/ezsdk_5_04/component-sources/syslink_2_10_03_20/packages/ti/syc
    Assertion at Line no: 301 in /home/siva/ezsdk_5_04/component-sources/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Ld
    FIRMWARE: Ipc_CONTROLCMD_STARTCALLBACK Error: ProcMgr status 0xffffffff
    FIRMWARE: Could not start: -1
    notify_shm_drv_sendevent failed! status = 0xfffffff0
    notify_send_event failed! status = 0xfffffff0
    notify_shm_drv_sendevent failed! status = 0xfffffff0
    notify_send_event failed! status = 0xfffffff0
    notify_shm_drv_sendevent failed! status = 0xfffffff0
    notify_send_event failed! status = 0xfffffff0

    I see the Ipc_attach timeout error in the dump . I understand A8 is the master core here ,but who is actually calling Ipc_attach() here ,as the VPSS-M3 firmware has not yet started . As per the Docs VPSS-M3 fiemware (MultiProc ID 2) has to do Ipc_attach() first with the A8(Multiproc Id 3) .

    When I maually step into the VPSS-M3 source code in the CCS environment ,I see that VPSS-M3 calls DomxCore_procAttach() which in turn calls Ipc_attach() function .

    The Ipc_attach() calls ti_sdo_ipc_Ipc_procSyncStart() ,this function returns Ipc_E_NOTREADY  and once again the Ipc_attach() func is called after 100 msec . In this way VPSS-M3 is looping in the Ipc_attach() function .

    What is making the VPSS-M3 to loop in Ipc_attach() function in this scenario ? Can you help me out where i have to look for to make the VPSS-M3 to come out of Ipc_attach() function .

    Thanks,

    Siva .

  • Hi Velan ,

    We were able to solve the above issue . Now we have an issue in firmware loading in our Custom Board . In our Custom Board we don't have Watchdog reset logic circuit ( i.e  we are not using watchdog Out Pin ) ,However when Watchdog is triggered in software ,board resets but HDVICP and HDVPSS firmware loading fails . I know this is because of software Watchdog reset won't call stop scripts . This may be due to HLT condition of two M3 Processors . Can you suggest us how we can bring the M3 Processors out of HLT condition after Watchdog reset in Software .I tried resetting RM_DEFAULT_XXX registers in U-boot but i am getting the IPC_ATTACH failed error and the board hangs . Any help is appreciated .

    Log without doing anything :

    PRCM Initialization completed 
    SysLink version : 2.10.03.20
    SysLink module created on Date:Sep 23 2012 Time:20:24:41
    
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id>Unhandled fault: Precise External Abort on non-linefetch (0x1808) at 0xf9020000
     <Location of FiInternal error: : 1808 [#1]
    last sysfs file: /sys/kernel/uevent_seqnum
    Modules linked in: syslink ipv6
    CPU: 0    Not tainted  (2.6.37 #3)
    PC is at DM8168DUCATIMMU_enable+0xc0/0x124 [syslink]
    LR is at DM8168DUCATIMMU_enable+0x2c/0x124 [syslink]
    pc : [<bf06b208>]    lr : [<bf06b174>]    psr: 20000013
    sp : cb4c0fe8  ip : 00000000  fp : cb4c1004
    r10: 00000000  r9 : 00000000  r8 : cb4c1ea4
    r7 : d4e45000  r6 : d4e3c000  r5 : bf1447b0  r4 : d4e3f000
    r3 : 00010000  r2 : f9020000  r1 : 00050000  r0 : bf0e35b5
    Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
    Control: 10c5387d  Table: 8b71c019  DAC: 00000015
    Process firmware_loader (pid: 1060, stack limit = 0xcb4c02e8)
    Stack: (0xcb4c0fe8 to 0xcb4c2000)
    --------------------------------------------------------------------------------------------------------
    Backtrace: 
    [<bf06b148>] (DM8168DUCATIMMU_enable+0x0/0x124 [syslink]) from [<bf069e1c>] (DM8168DUCATIPWR_on+0x250/0x2d4 [syslink])
     r5:00000000 r4:d4e3f000
    [<bf069bcc>] (DM8168DUCATIPWR_on+0x0/0x2d4 [syslink]) from [<bf050c20>] (PwrMgr_attach+0xfc/0x180 [syslink])
     r6:00000008 r5:097d2000 r4:d4e3c000
    [<bf050b24>] (PwrMgr_attach+0x0/0x180 [syslink]) from [<bf04ff08>] (ProcMgr_attach+0x190/0x3b0 [syslink])
     r5:cb4c0000 r4:d0af4000
    [<bf04fd78>] (ProcMgr_attach+0x0/0x3b0 [syslink]) from [<bf051790>] (ProcMgrDrv_ioctl+0x984/0x1c38 [syslink])
    [<bf050e0c>] (ProcMgrDrv_ioctl+0x0/0x1c38 [syslink]) from [<c00d1db4>] (vfs_ioctl+0x28/0x44)
     r8:beeb5ae8 r7:00000008 r6:00000008 r5:ccbc4000 r4:00000000
    [<c00d1d8c>] (vfs_ioctl+0x0/0x44) from [<c00d24c4>] (do_vfs_ioctl+0x500/0x540)
    [<c00d1fc4>] (do_vfs_ioctl+0x0/0x540) from [<c00d255c>] (sys_ioctl+0x58/0x7c)
    [<c00d2504>] (sys_ioctl+0x0/0x7c) from [<c0044e00>] (ret_fast_syscall+0x0/0x30)
     r8:c0044fa8 r7:00000036 r6:00008d74 r5:00000000 r4:000458f4
    Code: e3130010 0afffffc e5942010 e3a03801 (e5823000) 
    rmware> <start|s---[ end trace 889997bb4df8c042 ]---
    top> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments=== 
    <Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3 
    <Location of Firmware> firmware binary file 
    <start|stop>           to start/stop the firmware 
    ===Optional arguments=== 
    -mmap                  input memory map bin file name 
    -i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3 
    FIRMWARE: isI2cInitRequiredOnM3: 0
    FIRMWARE: Default memory configuration is used
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1

    Log when we do the resetting RM_DEFAULT_XXX registers :

    MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
    Assertion at Line no: 301 in /home/tellumat/project/build_env/vp4000/ti-ezsdk_dm816x-evm_5_04_00_11/component-sources/syslind
    FIRMWARE: Ipc_CONTROLCMD_STARTCALLBACK Error: ProcMgr status 0xffffffff
    FIRMWARE: Could not start: -1
    Loading HDVPSS Firmware
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
    Assertion at Line no: 301 in /home/tellumat/project/build_env/vp4000/ti-ezsdk_dm816x-evm_5_04_00_11/component-sources/syslind
    FIRMWARE: Ipc_CONTROLCMD_STARTCALLBACK Error: ProcMgr status 0xffffffff
    FIRMWARE: Could not start: -1

    Thanks

  • I'm experiencing the same issue where HDVPSS firmware fails to load after a watchdog reset.  Has anyone resolved this issue or have any ideas of how to go about fixing this issue?

    In my case I have a DM8168 board running the standard TI Linux and I have enabled the hardware watchdog.  I intentionally allow the watchdog to timeout to test system recovery from a watchdog reset.  On start-up I get the following error:

    Loading HDVPSS Firmware
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loadeUnhandled fault: external abort on non-linefetch (0x1808) at 0xf9020000
    r <Processor Id>Internal error: : 1808 [#1]
    last sysfs file: /sys/kernel/uevent_seqnum
    Modules linked in: syslink ipv6
    CPU: 0 Not tainted (2.6.37 #13)
    PC is at DM8168DUCATIMMU_enable+0x48/0x6c [syslink]
    LR is at DM8168DUCATIPWR_on+0xc0/0xec [syslink]
    pc : [<bf05a03c>] lr : [<bf0599d0>] psr: 20000013
    sp : cb143020 ip : cb143030 fp : cb14302c
    r10: 00000000 r9 : cb142000 r8 : cb143eac
    r7 : bf0943cc r6 : d4d9e000 r5 : 00000000 r4 : d4da1000
    r3 : 00010000 r2 : f9020000 r1 : c0336698 r0 : d4da1000
    Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
    Control: 10c5387d Table: 8bcc0019 DAC: 00000015
    Process firmware_loader (pid: 1252, stack limit = 0xcb1422e8)
    Stack: (0xcb143020 to 0xcb144000)
    3020: cb14304c cb143030 bf0599d0 bf05a000 d4d9e000 ccb75d00 d4da7000 bea1eae8
    3040: cb143064 cb143050 bf04b8c4 bf05991c cb143eac ccb75d00 cb143e64 cb143068
    3060: bf04b470 bf04b88c cb143000 0000010f 08100073 cb1431d4 cb143124 ccb7a6fc
    3080: cb143080 cb143080 00000000 00000000 cb143090 cb143090 ccba5580 c0342388
    30a0: 0000000b ccb6f680 00000000 00000000 cb143058 400e5000 40102000 cb143108
    30c0: cb143058 0000030f 08000875 cb143125 00000000 00000000 cb1430d8 cb1430d8
    30e0: 00000000 00000000 cb1430e8 cb1430e8 00000000 c0342388 00000000 ccb6fe00
    3100: 00000000 00000000 cb1430b0 40109000 4010a000 cb143160 cb1430b0 0000010f
    3120: 08100871 cb143075 cb14317c cb1430cc cb143130 cb143130 00000000 00000000
    3140: cb143140 cb143140 ccba50d0 c0342388 0000001c ccb6fe00 00000000 00000000
    3160: cb143108 4010a000 4010b000 cb1431b8 cb143108 0000010f 08100873 cb143125
    3180: 00000000 00000000 cb143188 cb143188 00000000 00000000 cb143198 cb143198
    31a0: ccba5e00 c0342388 0000001d ccb6fe00 00000000 00000000 cb143160 4010b000
    31c0: 40228000 cb143210 cb143160 0000030f 08000075 ccb7a1d5 cb143334 cb143074
    31e0: cb1431e0 cb1431e0 00000000 00000000 cb1431f0 cb1431f0 00000000 c0342388
    3200: 00000000 ccb6f880 00000000 00000000 cb1431b8 40228000 4022f000 cb143268
    3220: cb1431b8 0000000f 08000070 cb143285 00000000 00000000 cb143238 cb143238
    3240: 00000000 00000000 cb143248 cb143248 00000000 c0342388 0000011d ccb6f880
    3260: 00000000 00000000 cb143210 4022f000 40231000 cb1432c0 cb143210 0000010f
    3280: 08100071 cb143335 cb1432dc cb14322c cb143290 cb143290 00000000 00000000
    32a0: cb1432a0 cb1432a0 ccba5560 c0342388 0000011c ccb6f880 00000000 00000000
    32c0: cb143268 40231000 40232000 cb143318 cb143268 0000010f 08100073 cb143285
    32e0: 00000000 00000000 cb1432e8 cb1432e8 00000000 00000000 cb1432f8 cb1432f8
    3300: ccba5940 c0342388 0000011e ccb6f880 00000000 00000000 cb1432c0 40232000
    3320: 40235000 cb143370 cb1432c0 0000010f 00100073 cb1431d4 cb1433e4 cb143284
    3340: 00000000 00000000 00000000 00000000 cb143350 cb143350 ccba5ff0 00000000
    3360: 00040232 00000000 00000000 00000000 cb143318 40275000 40288000 cb1433c8
    3380: cb143318 0000030f 08000075 cb1433e5 00000000 00000000 cb143398 cb143398
    33a0: 00000000 ccb57c60 cb1433a8 cb1433a8 00000000 c0342388 00000000 ccb6fd80
    33c0: 00000000 00000000 cb143370 40288000 4028f000 00000200 cb14343c cb1433e8
    33e0: c0279388 c02788ac cb143494 cb14338c cb1433f0 cb1433f0 00000000 ccb57ec8
    3400: cb143400 0000007e cc812080 00000001 00000013 cc812060 8b11d600 00000200
    3420: 00000000 d0828d20 d0828d20 000000ba cb143464 cb143440 c02794d0 c027916c
    3440: cb1434a4 cb143450 cbdd8980 cc812060 cc84e3ac cc812000 cb143494 cb143468
    3460: c0272730 c02793c8 000000ba 0000007e 000000ba 00000090 cc812060 cb261780
    3480: cc84e0f4 00000002 cb14352c cb143498 c0272f4c c02726c4 00000000 000000ba
    34a0: c02794d0 c027916c 00000000 ccb57898 cbdd8980 cc812060 cc84e3ac 00000200
    34c0: cb143524 cb1434d0 c0279388 c02788ac c0279388 c02788ac c0279388 c02788ac
    34e0: cc84e3ac 00000200 cb14354c 0000007e cc812080 00000001 cc812080 cc812060
    3500: 8b11d200 00000200 00000000 d0828d20 d0828d20 000000be cb14354c cb143528
    3520: c02794d0 c027916c 8b11d200 00000200 cbdd8080 cc812060 cc84e3ac cc812000
    3540: cb14357c cb143550 c0272730 c02793c8 000000be c02793c8 000000be 00000090
    3560: cc812060 cb140380 cc84e0f4 00000002 cb143614 cb143580 c0272f4c c02726c4
    3580: 00000000 000000be cc812060 cb140380 cc84e0f4 00000002 cb14363c cb1435a8
    35a0: c0272f4c c02726c4 00000000 cb140380 00000000 000000be d0828c00 cbdd8080
    35c0: cb11d200 00000000 cc84e3ac 0000ffff 00000200 cc84e3ac d0828c00 cc812060
    35e0: cc812000 00000001 cb11d200 cb140380 cc84e3ac 00000000 00000003 cbdd8080
    3600: 00000008 cc84e0f4 cb143674 cb143618 c027473c c02729d4 cc84e3ac 00000000
    3620: cc84e000 cb14038c 00000000 cbdd8080 00000002 cc84e478 cb140380 60000093
    3640: 00000000 00000010 cbdd8080 8b11d200 cca47c00 00000020 cbdd8080 cbdd8088
    3660: 20000013 cc84e000 cb14372c cb143678 c0260f90 c0274264 cca47c00 00000020
    3680: cbdd8080 cbdd8088 20000013 cc84e000 cb143754 cb1436a0 c0260f90 c0274264
    36a0: 000000be fffffffc 00000096 000000ba c0350698 cb11d200 000000be c02a7c34
    36c0: ccb04b28 ccadbf00 cb1436ec cb1436d8 c02a937c c02a8d1c ccb04b28 ccadbf00
    36e0: cb143704 cb1436f0 c02a8ae8 c02a936c ccb04b28 ccadbf00 cb143734 cb143708
    3700: c00c89dc cc8f9b98 cca47c00 00000002 00000020 cc967800 20000013 c0350ba4
    3720: cb14374c cb143730 c026191c c02607d4 ccadbf00 cc967b40 000000be cbdd8080
    3740: cb143784 cb143750 c024c414 c02616a8 c026191c 000000be ccadbe40 ccad3900
    3760: ccb04b28 00000000 cc967800 cc967800 c0350698 ccad3900 cb1437c4 cb143788
    3780: c02b1b5c c024c2a8 ccb04b28 00000000 cc967800 cc967800 c0350698 ccad3900
    37a0: ccad8c00 ccad8c00 ccb04b28 cc967800 ccb44480 ccad3900 cb1437ec cb1437c8
    37c0: c02c2efc c02b16b4 000edea0 00000000 ccad8c00 cc967800 000edea0 00000000
    37e0: cb14381c 0000000c 00000005 00000005 bea1e908 cb14384c bf0c6ef8 bf062804
    3800: cb14384c 00000000 00000013 00000001 bea1e718 bea1e718 00000024 00000000
    3820: cb14384c bf08b20c 000ab394 00000000 ccb04b28 00000000 bea1e718 cb143848
    3840: c02d1a64 c02d1730 ccb04b28 00000000 00000000 00000000 cb14387c cb143868
    3860: c02cf84c c02d19ec ccbfa0a4 ccb44480 cb14390c cb143880 c02d12fc c02cf828
    3880: cb1438a4 cb143890 c02cf84c c02d19ec ccbfa0a4 ccb44480 cb143934 cb1438a8
    38a0: c02d12fc c02cf828 cb14390c cb1438b8 c0279890 ccb04a80 ccb04b28 ccb04a80
    38c0: ccb44480 ccb04a80 cb1438f4 cb1438d8 ccbfa0b8 00000098 ccbfa0b8 cca76b00
    38e0: ccbfa0b8 ccbfa0b8 ccb44480 ffff951a ffff951a ccb04b28 ccb04b40 000005a8
    3900: cb143964 cb143910 c02e3350 c02d1024 ccb44480 ffff951a ffff951a ccb44480
    3920: ea24cc57 0000fa80 cb14394c cb143938 c02a447c c007bf0c ccb44480 ea24cc57
    3940: cb143964 cb143950 c044b500 cc8285c0 25994fe9 00000001 cc8285b8 cc812814
    3960: cb143994 cb143970 c006d7d4 c01cbcf4 cbe7e044 cc8778c0 c044b4b8 00000001
    3980: cc8778f0 00000070 cbe7e000 cc8778f0 cbe7e030 c044b4b8 cbe7e000 cc8778f0
    39a0: cb1439d4 cb1439b0 c006d31c c006b728 c044b4b8 c0337748 cbe7e000 00000000
    39c0: 40000193 cc812814 cb1439f4 cb1439d8 cb1439f4 cb1439e0 c0084a84 c00879ac
    39e0: 00000001 cc8778c0 cb143a1c cb1439f8 c006eaa0 c0084a7c cbe7e030 a0000193
    3a00: c044cea0 cc812814 c044cea0 c044cea0 cb143a2c cb143a20 c006eafc c006ea24
    3a20: cb143a3c cb143a30 c0082a10 c006eaf0 cb143a5c cb143a40 c0082a70 c00829fc
    3a40: 00000000 c044cea0 cc803c00 c044cea0 cb143a8c cb143a60 c0082d48 c0082a20
    3a60: 00000001 00000000 60000193 cc812000 00000002 cc812814 ccb40000 ccb3748c
    3a80: cb143aa4 cb143a90 c0082db4 c0082bb4 cc812094 cc812044 cb143ab4 cb143aa8
    3aa0: c0082dfc c0082d8c cb143ac4 cb143ab8 c0082e1c c0082dec cb143b1c cb143ac8
    3ac0: c0279890 c02788d4 00000001 00000000 cb143b08 cc812000 00000000 00000000
    3ae0: ccb40000 00000000 cb143b0c d08247e0 c0082db4 20000193 00000000 00000000
    3b00: 00000002 00000000 ccb40000 ccb3748c cb143b4c cb143b20 c0277f58 c027950c
    3b20: 00000000 cb143b94 c0279890 cc88dc40 00000000 00000000 00000011 cbdd8c80
    3b40: cb143b5c cb143b50 c0057a38 c00579b4 cb143b6c cb143b60 c00a1fa4 c0057a18
    3b60: cb143b84 cb143b70 cb143b84 cb143b78 c0076248 c006c88c cb143b9c cb143b88
    3b80: c003f080 c0076200 ffffffff fa200000 cb143c2c cb143ba0 cbe7e000 cbe7e000
    3ba0: 00000000 00000000 fffffffd 00000000 cb143be4 cb143bc0 c0332e8c c00451c4
    3bc0: cc96001c cbe7e000 00000017 cc8778c0 cb142000 c031858c cb143bfc cb143be8
    3be0: c0332eec c0332e64 00000000 cb143bf8 cb143c14 cb143c00 00007e7f 000000bb
    3c00: ccbf818c ccbf81a4 ccbf8174 ccbf817c ccbf8188 ccbf81a0 cb143c90 00000000
    3c20: cb143d90 ccb37488 ccbf8164 c0155ab8 00000024 145dc5ff 00000000 1429004e
    3c40: cc829600 00000001 cb143c8c cb143c58 c006dd98 c006dac8 cc829600 00000001
    3c60: cb143ca4 cb143c70 c006dd98 00000000 00000001 00000014 bea1e714 bea1e714
    3c80: 00000028 00000000 c028f352 bf08a214 cc829600 bea1e714 cb143cc4 00000001
    3ca0: 00000000 00000000 c044b4b8 cc829600 cb143cdc cc9e8400 00000000 00000080
    3cc0: 000000d2 003fffff cb143d3c cb143cd8 c00aa4c0 c00a8064 00000041 c006bd20
    3ce0: 00000000 000200d2 c046c170 00000000 00000000 ffffffff 00000001 00000000
    3d00: 00000001 c06ab0a8 000000d2 c046b8b4 cb143d84 000000d2 003fffff 000000d2
    3d20: bf062a14 ffffffff cb142000 00000000 cb143dbc cb143d40 c00aa934 c00aa440
    3d40: 00000001 00000041 c046b8b4 00000000 00000000 cb140180 000000cf d4dc2000
    3d60: 00000001 cb143dcc cb140280 000000d2 bf062a14 ffffffff cb142000 000000cf
    3d80: cb143da4 cb143d90 c00c3464 c00c32d4 c0622bc0 00693ce1 cb143dcc cb143da8
    3da0: c00aa068 c00b7b14 00000000 c0622ba0 00000000 c0622ba0 00000000 00000001
    3dc0: cb143df4 cb143dd0 c00aa1d0 c00a813c 00000000 d4dc0000 cb140280 00000001
    3de0: bea1ead0 cb142000 cb143e0c cb143df8 00000002 d4dc0000 cb140280 00000001
    3e00: cb143e2c cb143e10 c00c31c0 c00c8ee8 00000000 00000000 d4dc0000 bea1ead0
    3e20: cb143e3c cb143e30 c00c3254 c00c3108 cb143e4c cb143e40 bf062830 cb143eac
    3e40: cb143eac ccb75d00 cb142000 bea1eae8 bea1eae8 00000000 cb143ef4 cb143e68
    3e60: bf04c178 bf04b3e8 00000000 cb143e78 00000097 00094a90 d4da7000 00094a90
    3e80: 00000060 c00c3220 cb143eac cb143e98 bf05db80 bf06281c 00000000 cb143fb0
    3ea0: cbe7e000 ccb04300 cb143ec4 00000000 00000000 c01cc744 cb143efc cb143ec8
    3ec0: c0332d0c c008c640 bea1eafc 00000000 d4da7000 00000000 00000000 ccb75d00
    3ee0: 00000008 00000008 cb143f04 cb143ef8 c00d8824 bf04ba20 cb143f74 cb143f08
    3f00: c00d8f34 c00d8808 00000000 00000100 00000000 00000000 00000014 00001003
    3f20: 00000000 cbda9680 cbc04a84 cb142000 ccb02d80 cc55d400 c00e05cc 00000014
    3f40: ccb34000 00001002 00000001 00000000 bea1eae8 c00ce0a0 00000008 ccb75d00
    3f60: cb142000 00000000 cb143fa4 cb143f78 c00d8fcc c00d8a40 c00d85a0 00000001
    3f80: 00000014 000458f4 00000000 00008d74 00000036 c0049fa8 00000000 cb143fa8
    3fa0: c0049e00 c00d8f80 000458f4 00000000 00000008 c00ce0a0 bea1eae8 00000008
    3fc0: 000458f4 00000000 00008d74 00000036 00000000 00000000 400a3000 bea1eacc
    3fe0: 00000000 bea1eaa8 000380b4 40251aec 60000010 00000008 6e617473 695f6563
    Backtrace:
    [<bf059ff4>] (DM8168DUCATIMMU_enable+0x0/0x6c [syslink]) from [<bf0599d0>] (DM8168DUCATIPWR_on+0xc0/0xec [syslink])
    [<bf059910>] (DM8168DUCATIPWR_on+0x0/0xec [syslink]) from [<bf04b8c4>] (PwrMgr_attach+0x44/0x54 [syslink])
    r7:bea1eae8 r6:d4da7000 r5:ccb75d00 r4:d4d9e000
    [<bf04b880>] (PwrMgr_attach+0x0/0x54 [syslink]) from [<bf04b470>] (ProcMgr_attach+0x94/0x1bc [syslink])
    r5:ccb75d00 r4:cb143eac
    [<bf04b3dc>] (ProcMgr_attach+0x0/0x1bc [syslink]) from [<bf04c178>] (ProcMgrDrv_ioctl+0x764/0x1410 [syslink])
    [<bf04ba14>] (ProcMgrDrv_ioctl+0x0/0x1410 [syslink]) from [<c00d8824>] (vfs_ioctl+0x28/0x44)
    r7:00000008 r6:00000008 r5:ccb75d00 r4:00000000
    [<c00d87fc>] (vfs_ioctl+0x0/0x44) from [<c00d8f34>] (do_vfs_ioctl+0x500/0x540)
    [<c00d8a34>] (do_vfs_ioctl+0x0/0x540) from [<c00d8fcc>] (sys_ioctl+0x58/0x7c)
    [<c00d8f74>] (sys_ioctl+0x0/0x7c) from [<c0049e00>] (ret_fast_syscall+0x0/0x30)
    r8:c0049fa8 r7:00000036 r6:00008d74 r5:00000000 r4:000458f4
    Code: e3130010 0afffffc e5902010 e3a03801 (e5823000)
    <Location of Fi---[ end trace 2714cc9251c2b364 ]---

    Any help would be appreciated.

    Thanks,

    Ossian

  • To answer my own question, it looks like the following link has the needed information:

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/242515.aspx

    I have not tested the information provided in the link, but it looks like this should provide the answers I was looking for.

    Ossian

  • Sivaramkrishna Neeruganti said:
    FIRMWARE: Ipc_CONTROLCMD_STARTCALLBACK Error: ProcMgr status 0xffffffff
    FIRMWARE: Could not start: -1

    How did you solve this issue? hope to share.