• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 716 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.

OMAP4 Blaze Board Framebuffer Capture Problem

Astro Wu
Prodigy 30 points

Hi,

  When boot to android, blaze board framebuffer capture image is not the android window surface image.

Using Panda or Blaze Tablet board has no such issue.

  To duplicate this problem, you can use either Eclipse IDE with DDMS or issue command lines to dump /dev/graphics/fb0 and convert the raw image.

I am using 27.g.x , actually all blaze code has same issue.

Thanks

Astro

  • 0
    TI__Intellectual 1300 points

    Astro,

    Yes, this is correct for the blaze. How were you able to determine that it does not occurr on panda or tablet? L27.g does not run on either hardware platform?

  • 0 in reply to Matthew Kiser
    Prodigy 30 points

    You may simply run ddms to capture framebuffer or do it in command line by :

    $ adb pull /dev/graphics/fb0 fb0  (or you can surf internet for how to grab framebuffer)

    If you still doubt on question that I asked months ago, then do it yourself on pandaboard.

    -astro


  • 0 in reply to Astro Wu
    TI__Intellectual 1300 points

    Well, the fact is: L27.G does not run on Panda. Android on Panda is very limited as a whole.

    But more to the point - why do you consider this a problem? What you are describing is correct - the framebuffer is not where the datastructure for the Android window surface is stored. I don't understand what the problem is that you are trying to identify, can you be more specific? What you describe above is correct.