• Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 819 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 demo codes encode and decode on a DM355

beardybloke
Prodigy 190 points

HI Folks,

first let me say thanks to any one  who has replied so far. I'm slowly working my way through it but the cod efrom TI never seems to run as it tells you in the manaul.

I've given up at the minute with encoding video. I did encode audio, brilliant and it did work as it says in the book. cool! I've now changed decoding video.

decoding sound worked as well as envoding it. brilliant.

Decoding video, the story so far....

eventually got the error list to one which was "unable to use 720x480x16"

So I changed my EVM setup to

setenv bootargs console=ttyS0,115200n8 noinitrd ip=dhcp root=/dev/nfs rw nfsroot=192.168.11.3:/home/david/workdir/filesys mem=116M video=davincifb:vid0=720x480x16,2500K:vid1=720x480x16,2500K:osd0=720x480x16,2025Kdavinci_enc_mngr.ch0_output=COMPOSITEdavinci_enc_mngr.ch0_mode=$(PAL)

from the manuals

video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576x16,2025K

setting

NOw I have another couple of errors appear which are

Rszcopy: failed to open device                                                                                               
Decode Error: Failed to create resize copy job                

Any one know what to do or where to look?

 

 

  • TI__Mastermind 41665 points

    This sounds like there is a problem initializing the resizer driver or one of its dependencies. The first thing that comes to mind is the loadmodules.sh file, I assume you are running this already, does it output any messages that could indicate a problem when you run it?

  • in reply to Bernie Thompson TI
    Prodigy 190 points


    I have had problems with the load modules before, I was told to install the latest versions of software.

    I'm now running DVSDSK_30_01_40

    When I run ./loadmodules.sh this is what I receive.


    ioremap_nocache(0x87400000, 12582912)=0xc7880000                               
    allocated heap buffer 0xc7880000 of size 0xce000                               
    cmem initialized 8 pools between 0x87400000 and 0x88000000                     
    mknod: `dm350mmap': File exists                      

    Now it could be that I am running it from the wrong place or may not have the correct paths loaded.

     

  • in reply to beardybloke
    TI__Mastermind 41665 points

    That is odd, it seems that dm350mmap is somehow already loaded, not sure if this will fix it but you could try running 'rmmod dm350mmap.ko' before running the loadmodules.sh script, that should reload the module, and ensure you are using the dm350mmap.ko that is associated with the loadmodules.sh.

  • in reply to beardybloke
    TI__Mastermind 37340 points

    How is your EVM configured to boot; if you load file system from HDD (as opposed to NFS) loadmodules.sh runs automatically.  This may explain why dm350mmap is already loaded.

  • in reply to Bernie Thompson TI
    Prodigy 190 points

    ran rmmod dm355mmap.ko

    answer was

    ERROR Module dm355mmap does not exist in proc/modules

    humph

  • in reply to Juan Gonzales
    Prodigy 190 points

    NFS root is via my network link to the PC

     

  • in reply to Juan Gonzales
    Prodigy 190 points

    So if I am booting via the HDD on the PC which I'm doing how do I tell if it has loaded ./loadmodules correctly?

    How would I go about removing the error

    RSzcopy: Failed to open

    and Decode error: failed to create resize job.

    The Image file and the DVSDK files should be a match as I very recently down loaded both new files. But again how would I be able to check that the two are compatibale.

     

     

     

     

  • in reply to beardybloke
    TI__Mastermind 41665 points

    If the ./loadmodules.sh script was successfull you should see only messages confirming that it was able to load the cmemk.ko and dm350mmap.ko files without error, if you see messages like 'version mismatch' than you may have a problem.

    Unfortunately there is not an easy way to check the version of the kernel image, if something fails or you get a warning or error when doing things like running the ./loadmodules.sh script that is a good indication that you may have a version incompatibility. Typically I would suggest using everything out of the same DVSDK install by doing a TFTP/NFS boot so you ensure that your kenel and your filesystem are coming from the same DVSDK.

    Another thought on the RSZcopy error is that it could indicate that your kernel does not have the resizer driver enabled for some reason (perhaps just an older kernel than your demo code). If you have not already you may want to go through the steps to rebuild the kernel and ensure that the resizer driver is enabled in your 'make menuconfig', than boot your new kernel via TFTP. The instructions for doing this are given in the getting started guide.