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.

Frame Buffer Problem with DM6446



Hi,

I am trying to run Angstrom file system for my DM6446x+ purchased from TI.

I downloaded their file system and managed to get their 2.6.32-davinci-rc2 kernel from the arago git tree.

I configured the kernel with the default davinci_dm644x_defconfig configuration.

I configured my uboot to load the kernel through tftp and NFS while DHCP enabled.

My boot args are:

"setenv bootargs video=davincifb:vid0=0,2500K:vid1=0,2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=10.130.201.55:/home/amrali/Angstrom/random-d526768f-image-dm6446-evm,nolock mem=120M"

 

Whenever I boot the kernel, I get the message

"davincifb davincifb: dm_osd0_fb: 720x576x16@0,0 with framebuffer size 2025KB
davincifb davincifb: dm_vid0_fb: 0x0x16@0,0 with framebuffer size 2500KB
davincifb davincifb: dm_osd1_fb: 720x576x4@0,0 with framebuffer size 2025KB
davincifb davincifb: dm_vid1_fb: 0x0x16@0,0 with framebuffer size 2500KB
davincifb davincifb.0: dm_osd0_fb: Failed to obtain ownership of OSD window.
"

Any clues about why it is failing to open the frame buffer? I can't get any application with GUI working on my screen as well as I do not see the boot logo.

--

Amr Ali

Embedded Systems Developer

www.embedded-tips.blogspot.com

  • Hi,

    I have used the following bootargs with 2.6.32 Kernel on DM644x EVM successfully.

    setenv bootargs ......video=davincifb:vid0=720x576x16,2500K@0,0:vid1=720x576x16,2500K@0,0:osd0=720x576,2025K@0,0:osd1=720x576,2025K@0,0.....

    May be you can give a try with this.

    Regards, Sudhakar

  • Hi,

    I got the problem fixed with similar bootargs.

    I guess that version of the arago kernel has a bug.

    I can't see the boot logo.

    The only way to see a graphics on the screen is to have the Xorg work then close it or not then use any GUI application.

    I think the Xorg calls some driver functions the kernel does not call during initialization.

    You aware of anyway I can find some patches applied to that tree.

    I am sorry for that question but I m not that familiar with git systems.

    --

    Amr Ali Abdel-Naby

    www.embedded-tips.blogspot.com