• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 99 subscribers
  • Views 256 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.

Problems with own ccdc driver

Martin9923
Prodigy 130 points

Hello,

at the moment I am writing a driver for DM355 for a specific capture sensor. I only implemented the ioctls which I need and now I am able to load the driver module. Then I wrote a little application to read data from the sensor and write it to a file. For that I oriented at the ipipe examples. The driver is initialized and streamon is done. Then I call CaptureFrame in an infinite loop and get the pointer to capbuf_phyaddr. This works and now I want to read the image data. This is my problem. Could someone give me any hints how I could do this? I attached my code and commented the area where I want to read data.

Thank you very much for help!

Martin

  • 0
    TI__Mastermind 37340 points

    Martin,

    The main problem I see is that it appears you are attempting to access physical memory address from user pace (a no-no in Linux).  You probrably want to use the virtual memory mapped address (.start); you can pass the pysical address to a lower level driver such as resizer, but your user application cannot access it directly.   I hope this helps.