• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 536 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.

DM8168 dvrrdk_03 decode 1600x1200 H264 stream report exception

Eric Mao
Genius 4330 points
Other Parts Discussed in Thread: SYSBIOS

Hi all

   The exception message:

   

1976890:!!!SLAVE CORE [VIDEO-M3] DOWN!!!
SystemLink_copySlaveCoreExceptionContext:120
mmap of [0xbe9c0000:36864]
mmap virt addresss:0x2ab31000
munmap of [0x2ab31000:36864]
SystemLink_copySlaveCoreExceptionContext:127
SystemLink_handleSlaveCoreException:149


1976917:!!!SLAVE CORE DOWN!!!.EXCEPTION INFO DUMP

!!HW EXCEPTION ACTIVE (0/1): [1]

!!EXCEPTION CORE NAME : [VIDEO-M3]

!!EXCEPTION TASK NAME : []

!!EXCEPTION LOCATION : []

!!EXCEPTION INFO : [H/W EXCEPTION]

!!EXCEPTION CCS CRASH DUMP FORMAT FILE STORED @ ./CCS_CRASH_DUMP_VIDEO-M3.txt
SystemLink_handleSlaveCoreException:154

The CCS_CRASH_DUMP_xx.txt and xem3 file is hard to insert to post ,so i upload them to a web storage, the download address is list in the attachment.

Fullscreen 1512.xem3_download_address.txt Download 
http://cd.ctfs.ftn.qq.com/ftn_handler/0a5a84d189083c993d801d6972b79d1e73bb6c6f7dd05e2c3b0b27afa81ed6b87c495170070cd220a70f09d27c3400266ad8f41bebfe4ea0cc7b26bd4344c533/?fname=dvr_rdk_m3vpss.rar&k=72326639737ce19de72131554064054d03565f095f5c0607185607005049035003064b005154064f0503555804020f5756530700667637064340394b020f680f0644164a154a450347325b&fr=00&&txf_fid=00000000e933c51bcbcc458f92481a08bedd2f60&xffz=2746347
http://cd.ctfs.ftn.qq.com/ftn_handler/14915f54e49ca1bd7c2440f85756d613801cb94fed6958010c6ee595ff6fe1edc611cbdc040899650513417939e2b9aecfd28868edfeac1004090cba994c57e3/?fname=dvr_rdk_m3video.rar&k=29396533331dbb9ab32a325f1161574a58585d52005852074c01040b064c515c075a480b55050348530e510302070151035b500437726501174b3a41530a3a08524f0c57520e4b17004b650e&fr=00&&txf_fid=000000002064a818336a4903a5226741d778b2cd&xffz=2196476
http://cd.ctfs.ftn.qq.com/ftn_handler/90fa883c2a3883eb23a094ab8bfc43f656e6a198eca2f412a87544ec8a03c9d5e037ba079c08dff16dfd18c84135975eba1c7c3eb8b3d2ec82e4c6e01894c072/?fname=CCS_CRASH_DUMP_VPSS-M3.txt&k=7e64396132499999e3776e0d1334564907515805025206531c050c0500195002060014030555544b0401585700005152555c0f54352e6425723766226775372e6e206c2c656b32366237142c061a101e456404&fr=00&&txf_fid=000000002690cf8510b949b9a675e16d40ecefc7&xffz=164601
http://cd.ctfs.ftn.qq.com/ftn_handler/81ecfb795f2f4eae15edb35fcd54207e6082e128c20fb3382effb077f16b1527913b23e7c3dffb98e4d1944efa657b510f9b3ec49fc3aa9b788383887e3ecca0/?fname=CCS_CRASH_DUMP_VIDEO-M3.txt&k=6038616394dfc6cae22b360f10630a1a095c545404520a031d0802500f4e0c5303014c0205010e18025e525402505d04000a545b36783876736b3e2064226b7d6f7c342e663c6e7c747d2e4e7b501641484c615e&fr=00&&txf_fid=00000000f85deba4b7ff4d6dacc8233765d61153&xffz=82782

  • 0
    TI__Guru 59700 points

    Below is the backtrace for the exception logs you shared:

    M3Video

    =======

    0 ti_sysbios_utils_Load_swiBeginHook__E(struct ti_sysbios_knl_Swi_Object *) at /home/eric/mrsh/ti_tools/bios/bios_6_33_05_46/packages/ti/sysbios/utils/Load.c:202 PC = 0x9D22448E FP = 0x3DDCE408
    1 ti_sysbios_knl_Swi_run__I(struct ti_sysbios_knl_Swi_Object *) at /home/eric/mrsh/ti_tools/bios/bios_6_33_05_46/packages/ti/sysbios/knl/Swi.c:106 PC = 0x9D21A18C FP = 0x3DDCE418
    2 ti_sysbios_knl_Swi_restoreHwi__E(unsigned int) at /home/eric/mrsh/ti_tools/bios/bios_6_33_05_46/packages/ti/sysbios/knl/Swi.c:392 PC = 0x9D223AEE FP = 0x3DDCE458
    3 ti_sysbios_family_arm_m3_Hwi_dispatch__I() at /home/eric/mrsh/ti_tools/bios/bios_6_33_05_46/packages/ti/sysbios/family/arm/m3/Hwi_asm.sv7M:208 PC = 0x9D21D57E FP = 0x3DDCE468
    4 ti_sysbios_knl_Swi_run__I(struct ti_sysbios_knl_Swi_Object *) at /home/eric/mrsh/ti_tools/bios/bios_6_33_05_46/packages/ti/sysbios/knl/Swi.c:106 PC = 0x9D21A18D FP = 0x3DDCE468
    5 <symbol is not available> PC = 0x00000000 FP = 0x3DDCE4A8

     

    M3VPSS

    ========

    0 Vcore_secUpdateDesc(void *, struct unknown *, struct unknown *, unsigned int) at /home/eric/mrsh/ti_tools/hdvpss/hdvpss_01_00_01_37_patched/packages/ti/psp/vps/core/src/vpscore_secPath.c:1845 PC = 0x9DEFE1A4 FP = 0x3EFD9D18 1 vpsMdrvScUpdateDescList(struct VpsMdrv_ScHandleObj_t *, struct VpsMdrv_ScQueueObj *) at /home/eric/mrsh/ti_tools/hdvpss/hdvpss_01_00_01_37_patched/packages/ti/psp/vps/drivers/m2m/src/vpsdrv_m2mSc.c:2360 PC = 0x9DEADE42 FP = 0x3EFD9D30 2 VpsMdrv_scProcessFrms(void *, struct FVID2_ProcessList *) at /home/eric/mrsh/ti_tools/hdvpss/hdvpss_01_00_01_37_patched/packages/ti/psp/vps/drivers/m2m/src/vpsdrv_m2mSc.c:712 PC= 0x00426152 FP = 0x3EFD9EA0 3 FVID2_processFrames(void *, struct FVID2_ProcessList *) at /home/eric/mrsh/ti_tools/hdvpss/hdvpss_01_00_01_37_patched/packages/ti/psp/vps/drivers/src/fvid2_drvMgr.c:851 PC = 0x00428364 FP = 0x3EFD9EC8 4 SwMsLink_DrvProcessFrames(struct SwMsLink_Obj *) at /home/eric/mrsh/dvr_rdk/mcfw/src_bios6/links_m3vpss/swMs/swMsLink_drv.c:2885 PC = 0x0040F286 FP = 0x3EFD9ED0 5 SwMsLink_drvDoScaling(struct SwMsLink_Obj *) at /home/eric/mrsh/dvr_rdk/mcfw/src_bios6/links_m3vpss/swMs/swMsLink_drv.c:3137 PC = 0x00410D24 FP = 0x3EFD9F60 6 SwMsLink_tskMain(struct Utils_TskHndl *, struct Utils_MsgHndl *) at /home/eric/mrsh/dvr_rdk/mcfw/src_bios6/links_m3vpss/swMs/swMsLink_tsk.c:62 PC = 0x00411952 FP = 0x3EFD9F88

     

    As you can see from backtrace there is no memory corruption but h/w exception occurred. This indicates issue with your board. Check the things I mentioned previously related to DDR and AVS.

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/250529/878774.aspx#878774

    Also try reducing the M3 frequency to 250 Mhz and check is stability improves. Also measure the 816x junction temperature and ensure it does not exceed 95 C as per spec. Try improving ventilation and ensure you have fan on top of 816x and also ventilation on the board to clear out the heat.

     

  • 0 in reply to Badri Narayanan
    Genius 4330 points

    Hi Badri Narayanan

      Thank you for reply, I will recude the M3 freq and retry!

      But i still have a question.  Why no problem when decode 1080P h264 stream.   In my application, need decode 1080P and UXGA h264 stream,  the application decode 1080P stream run over 24 hours still OK, but when decode UXGA stream, it always export exception.  The application i've tested ok on evm borad.

       And can you tell me how to Analysis the xem3 and DUMP_core.txt to get the error message?

      


  • 0 in reply to Eric Mao
    TI__Guru 59700 points

    Issue looks to be related to power , so failure will be random based on instantaneous power requirement of the stream. Probably the stream characteristic of UXGA causes more power to be drawn. RUn the exact same usecase on UDworks DVR and check if you see exception. The reference design board is deisgned correctly and does not have board design issues. If it is s/w issue you will see failure on UDwork DVR board as well.

    For analysis of crash dump refer this link:

     
    Also attached are the files for crash dump analysis for your reference.
     
    To generate crash dump output you should use <CCS_Install>\ccs_base\scripting\bin\dss.bat AnalyzeCrashDUmpM3.js as mentioned in the link above.