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.

DM365 - encode demo - "Operation mode doesn't match with current hw mode"

Hi,

I am working on a video integration project with a DM365 board but am having a problem with the 'encode' demo software. I have followed the getting started instruction page and have successfully built and installed the filesystem (loaded via ntfs) and kernel (via tftp) and modules etc. The example applications etc all build and install without issue also.

However when I run the 'encode' demo application I get the following output

root@ti-board:/opt/dvsdk/

dm365# ./loadmodules_hd.sh
root@ti-board:/opt/dvsdk/dm365# ./encode -v test.mpeg4
Encode demo started.
Error: Failed to create capture device
root@ti-board:/opt/dvsdk/dm365# ./encode -v test.264 
Encode demo started.
Error: Failed to create capture device

I have tried all combinations of options etc loading different drivers but always with the same results, unless I remove the video source in which case I get the 'failed to detect video' message so I know video is being detected. At the same time as I get the 'capture device' error message above (via a ssh session) I get this message on the console

davinci_resizer davinci_resizer.2: Operation mode doesn't match with current hw mode

I have read through the code of the various modules and the encode demo itself but at this stage in my learning curve I am not really able to fathom what it is trying to do in the depths of the drivers and the error message isn't enormously helpful.

I wonder if anyone is able to shed any light on why this error message is occurring, what it means, and how I can fix it? The curious thing is that I am sure (well 95%!) that I did have the encode demo working a couple of weeks ago but going through my saved command history and repeating those commands just generates the failure message above, and nothing else appears to have changed. I have tried rebuilding the dvsdk and kernel etc but that seems to make no difference.

Any suggestions about what this error means and also how to correct it would be much appreciated.

Philip Coombes
  • Hi Philip,

    The error message is related to the operation mode of resizer. Looks like you are setting resizer to "one shot mode" in the bootargs where as encode demo might be opening resizer device in "continuous mode".

    Can you tell the bootargs for your hardware?

    You need to look at  "dm365_imp.oper_mode" in your bootargs. Ideally for encode demo it should be set to 0, but you can toggle between 0 and 1 and rerun the demo again.

     

    Regards,

    Anshuman

  • Hi Anshuman,

    Thanks for the quick reply, these are my bootargs and the rest of the boot environment. Basically taken from the TI Getting Started guides

    bootdelay=4
    baudrate=115200
    ethaddr=00:0e:99:02:ca:62
    rootpath=/home/stan/work/ubiquiti/embedded/filesys
    nfshost=192.168.2.44
    rootserver=192.168.2.44
    serverip=192.168.2.44
    bootfile=uImage
    bootcmd=dhcp;bootm
    bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.168.2.44:/home/stan/work/ubiquiti/embedded/filesys,nolock mem=76M video=davincifb:vid0=OFF:vid1=OFF:osd0=7206de=0 davinci_capture.device_type=4
    stdin=serial
    stdout=serial
    stderr=serial
    ver=U-Boot 1.3.4 (Mar  2 2009 - 11:50:39)

    Regards

    Phil

  • do you have an 720p input video source connected to component video input connectors?  I used a blueray DVD player as my video inputs source

  • No, we have no component video inputs. Ultimately it is only digital video that is likely to be used anyway.