• State Answer Suggested
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 442 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.

DM365: /dev/fb directory is missing.

Ritesh Nagpal
Prodigy 20 points


Dear Members,

I have tried following bootargs but still the /dev/fb directory is missing. Do I need to execute any other command? or am I missing something in bootargs?

bootargs 'mem=60M console=ttyS1,115200n8 root=/dev/ram0  rw initrd=0x82000000,12M video=davincifb:vid0=720x480,1350K@0,0:vid1=off:osd0=720x480,1350K@0,0:osd1=720x480,1350K@0,0 ip=dhcp eth=$(ethaddr)'

bootargs 'mem=60M console=ttyS1,115200n8 root=/dev/ram0  rw initrd=0x82000000,12M video=davincifb:vid0=OFF:vid1=OFF:osd0=720x576x16,4050K davinci_enc_mmgr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=ntsc vpfe_capture.bufsize=4147200 ip=dhcp eth=$(ethaddr)'

bootargs 'mem=60M console=ttyS1,115200n8 root=/dev/ram0  rw initrd=0x82000000,12M video=davincifb:vid0=off:vid1=off:osd0=720x480,1350K@0,0:osd1=720x480,1350K@0,0 davinci_enc_mmgr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=ntsc vpfe_capture.bufsize=4147200 ip=dhcp eth=$(ethaddr)'

 

Any help or pointer is appreciated.

Regards,

Ritesh Nagpal

  • 0
    TI__Mastermind 37340 points

    VID0 and VID1 windows can be controlled by V4L2 driver (/dev/videox type devices) or frame buffer driver (/dev/fb/x type devices); this is determined by your bootargs settings (e.g. vid0=OFF suggests use of V4L2); however, the OSD0 and OSD1 windows are always controlled by frame buffer driver as these are primarily used for graphics purposes; therefore you should always see at least one or two /dev/fb type devices (e.g. /dev/fb2 for example is the attribute window).  If you are not even seeing these than there may be something else wrong (aside from bootarg settings).

    Can you try setting bootargs per the Getting Started Guide (e.g. 'mem=64M' and removing '@0,0' )?  Also, if you can post your boot log, we may be able to identify what went wrong during the boot process.

     

  • 0 in reply to Juan Gonzales
    Prodigy 20 points

    Dear Juan,

    Many thanks for your reply. There was some problem with the uImage we were using. After selecting appropriate frame-buffer options from menuconfig, and creating a new uImage, /dev/fb/ directory is showing up.

    Regards,

    Ritesh Nagpal