• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 275 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.

dm6446 decode error with dvsdk_1_10

bei liu
Prodigy 210 points

root@192.168.0.84:/mnt/nfs/opt/dvevm# ./decode -v kang.264
Decode demo started.
AssertiUnable to handle kernel paging request at virtual address 93b8090d
on failed (poolId < MAX_Ppgd = c5b3c000
OO[93b8090d] *pgd=00000000LE
NTInternal error: Oops: 801 [#1]
Modules linked in: dsplinkk cmemk ipv6
CPU: 0
PC is at LDRV_MSGQ_Put+0x2c/0xe8 [dsplinkk]
LR is at PMGR_MSGQ_Put+0x10/0x14 [dsplinkk]
pc : [<bf00a2c8>]    lr : [<bf005788>]    Tainted: PF
sp : c54c7ef4  ip : c54c7f18  fp : c54c7f14
r10: 0002f114  r9 : c54c6000  r8 : c0027b24
r7 : 93b808ff  r6 : 00006f0a  r5 : 00008000  r4 : 00000000
r3 : 00000002  r2 : 00020000  r1 : c54c7ef4  r0 : 00000000
Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: 5317F  Table: 85B3C000  DAC: 00000015
Process decode (pid: 1339, stack limit = 0xc54c6198)
Stack: (0xc54c7ef4 to 0xc54c8000)
7ee0:                                              0000004a 4233a0e8 00008000
7f00: 00006f0a 4233a0e8 c54c7f24 c54c7f18 bf005788 bf00a2ac c54c7f3c c54c7f28
7f20: bf005344 bf005788 c59a9c60 ffffffe7 c54c7f5c c54c7f40 c0089584 bf0051d4
7f40: c59a9c60 4233a0e8 00000008 00000000 c54c7f84 c54c7f60 c0089890 c0089518
7f60: 00000000 00000000 c59a9c60 fffffff7 00006f0a 00000036 c54c7fa4 c54c7f88
7f80: c00898f0 c00895a8 00000001 412d0900 00000002 0002fad0 00000000 c54c7fa8
7fa0: c00279a0 c00898c0 412d0900 c002745c 00000008 00006f0a 4233a0e8 00032720
7fc0: 412d0900 00000002 0002fad0 4233a5a8 4233a40c befffc38 0002f114 4233a0e4
7fe0: 0002f1cc 4233a090 0001c1f4 401a0344 60000010 00000008 09665a01 03184ca3
Backtrace:
[<bf00a29c>] (LDRV_MSGQ_Put+0x0/0xe8 [dsplinkk]) from [<bf005788>] (PMGR_MSGQ_Pu
t+0x10/0x14 [dsplinkk])
 r7 = 4233A0E8  r6 = 00006F0A  r5 = 00008000  r4 = 4233A0E8
[<bf005778>] (PMGR_MSGQ_Put+0x0/0x14 [dsplinkk]) from [<bf005344>] (DRV_Ioctl+0x
180/0x34c [dsplinkk])
[<bf0051c4>] (DRV_Ioctl+0x0/0x34c [dsplinkk]) from [<c0089584>] (do_ioctl+0x7c/0
x90)
 r5 = FFFFFFE7  r4 = C59A9C60
[<c0089508>] (do_ioctl+0x0/0x90) from [<c0089890>] (vfs_ioctl+0x2f8/0x318)
 r7 = 00000000  r6 = 00000008  r5 = 4233A0E8  r4 = C59A9C60
[<c0089598>] (vfs_ioctl+0x0/0x318) from [<c00898f0>] (sys_ioctl+0x40/0x60)
 r7 = 00000036  r6 = 00006F0A  r5 = FFFFFFF7  r4 = C59A9C60
[<c00898b0>] (sys_ioctl+0x0/0x60) from [<c00279a0>] (ret_fast_syscall+0x0/0x2c)
 r6 = 0002FAD0  r5 = 00000002  r4 = 412D0900
Code: e3540001 e1a02800 e24b1020 e1a00004 (e1c730be)
 RIES). File : drv_pool.c Line : 154
Assertion failed (poolId < MAX_POOLENTRIES). File : drv_pool.c Line : 154
Segmentation fault

  • 0
    Prodigy 210 points

    I have a davinci DM6446 Platform.there are encodedecode,decode.and deocde demos in disk,and there is no problem when I run them .But when I run demos in DVSDK_1_10 through NFS.The above error occur.I know there is difference in MEM map between them.does  the above error arise from MEM map????how to correct it?

    thanks for response!!!

  • 0 in reply to bei liu
    TI__Mastermind 37340 points

    DVSDK_1_10 is a really old release; actually, if I recall correctly, back then we used to call the release DVEVM_1_10.  However, this build did work correctly as I used it quite frequently myself. 

    I suspect that the issue you are seeing may be due to not having all of the software pieces (ubl, uboot, uimage, or file system)  from the same DVSDK software version.  Since some of the software can reside in multiple places (e.g. uImage can be either in NOR flash, NAND flash, or TFTP), it is very easy to overlook upgrading all software components together. 

  • 0 in reply to Juan Gonzales
    Prodigy 210 points

    Thanks for your response!

    All my softwares installed are get from authorized sales。Here are all the softwares when I install them all：

    bios_5_30           dsplink_1_30_08_02            Rules.make
    cg6x_6_0_3          dvtb                          sprue66a.pdf
    cmem_1_01           evm_davinci                   sprueg8.pdf
    codec_engine_1_02   examples                      u-boot-upgrade.html
    codec_servers_1_00  framework_components_1_00_03  _uninst
    data                index_manuals_dvevm.html      _uninst2
    data.tar.gz         index_manuals_dvsdk.html      xdais_5_00
    davinci.jpg         Makefile                      xdctools_1_21
    demos               release_notes_dvevm.html
    doc                 release_notes_dvsdk.html

    Are they match each other？And the uImage is in NOR flash，the MV linux is V4。but I do not know which version is my file system ？do you mean NFS？Does it matter？

  • 0 in reply to bei liu
    TI__Mastermind 37340 points

    In the past, you would normally register your DM6446 EVM via www.ti.com/davinciregistration , and use the username and password setup during registration process to access the software update site (www.ti.com/davincisoftwareupdates ).  From the software update site, you could navigate your way to the dvsdk_1_10 release found at https://www-a.ti.com/extranet/cm/product/dvevmsw/dspswext/general/v1_10_00.shtml; the software found at this last URL is what you appear to have (release notes match versions of the software components you listed above).  However, this is just your host side components, you still need to make sure that your u-boot (should come from same URL above) and your uImage (resulting from installing the software per Getting Started Guide) and your file-system (also results from following Getting Started Guide) all come from this same URL. 

    It does not matter if your file system in on the hard-drive or NFS mounted; no matter where you load these software components from, you need to ensure the version you are loading are from the same software release.  For example, say you have your u-boot in NOR flash, your uImage is loaded via TFTP and your file-system via NFS.  You need to make sure that the u-boot that is in NOR flash is the one found at the URL above, you need to make sure that the uImage found in the host's 'tftpboot' directory is the one that you built using the software from this URL, and you need to ensure the file system being NFS loaded (check u-boot bootargs and your hosts /etc/exports file) comes from this software installation.