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.

About Framebuffer on dm355

Other Parts Discussed in Thread: TMS320DM355

 Hi All,

Now I have added the support of 1680x1050 resolution on dm355, I have measured the signal (HSYNC,VSYNC etcs) using oscilloscope. But when I set the size of framebuffer using "fbset -fb /dev/fb/1 -xres 1680 -yres 1050 -vxres 1680 -vyres 2100 -depth 16" ,

I can not get the right display for 1680x1050 resolution, It only displayed a small part about 27 lines. If I set the framebuffer as 1680x1023, It can work well. It seemed that the height of framebuffer can not be more than 1024. Please give me some help. Thanks.

 

Best Regards

Jeff 

  • This is probably a limitation in the driver since this part is not marketed towards HD market; the hardware appears to be capable of vertical resolution up to 2048 lines of height.

  • As Juan mentioned this part is not meant for the 1080 HD type of applications (really more only up to 720p) so this is likely just because of how the driver was written. One thing I can suggest is that you try video window 0 instead of video window 1, as the VPBE manual suggests using video window 0 for HD and to have video window 1 turned off when displaying HD. Beyond this, you may have to modify the display driver software to support a 1050 resolution.

  • Jeff,

    When you say you added support, does this mean you modified the display driver?

    Another thing to keep in mind is that some aspects of the driver are initialized once during boot-up according to u-boot 'bootargs' settings; therefore, if these settings are not correct, it may not matter much what you pass via fbset command.

  • Hi jeff,

    I am working on dm355 linux platform.

    following getting started guide tms320dm355 dvevm v1.30, i got the kernel and root file system, got success Booting via TFTP using NFS file system.

    but unable to run the demo, getting osd display output but no video display and error as shown below.

    root@10.10.10.242:/opt/dvsdk/dm355# ls
    cmemk.ko decode.txt encode encodedecode.txt log.txt web
    data dm350mmap.ko encode.txt interface mapdmaq
    decode dvevmdemo encodedecode loadmodules.sh thirdpartydemos

    root@10.10.10.242:/opt/dvsdk/dm355# ./decode -v data/videos/davincieffect_pal.mpeg4

    Decode demo started.
    CMEM Error: init: Failed to open /dev/cmem: 'No such file or directory'
    Decode Error: Failed FBIOPUT_VSCREENINFO on /dev/fb/3 (Invalid argument)
    Decode Error: Failed to open video decode algorithm
    root@10.10.10.242:/opt/dvsdk/dm355#


    kindly do the needfull.

    Thanks and regards,

    Mohammed asif.