I am working on DM368 , mt9p031 with DVSDK 4.0.2.
how to get TI 2A lib ? the sales said they don't have this lib.
I can't understand why TI doesn't publish its 2A lib and its doc which is the essential files for development.
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.
The 2A lib is shipped as part of our DM368 IPNC reference design. You can order that from http://www.appropho.com/NewWeb/Product_DM368MT5.php#a.
Otherwise, please contact your local TI FAE or sales person to get the SW.
Regards,
Xiangdong
No, Appro's IPNC is not under DVSDK 4.0.2 yet. But you can get 2A lib from that and port it to your IPNC SW. 2A is not dependent on DVSDK or Linux kernel version at all. In fact, we highly recommend customers to start from the IPNC reference design since it is a lot more rebost and feature rich than the standard DVSDK.
Hi Fu,
thanks for your quicky reply.
We have got our IPNC working, it uses the kernel 2.6.32 and h264 encode on DVSDK 4.0.2. no more needed.
The IPNC works fine with some sensors with 2A built-in.
Now, we want to use mt9p006 ( mt9p031 ), this sensor needs 2A.
I have got TI 2A lib and header files, but no document. I dont' know how to use them.
Who is the local FAE? The sales of TI chips ?
Hi, Xiangdong
Are you sure the 2A lib can work in DVSDK4.0.2? We have the same question to HM Yang. We've a IPNC all work now except 2A.. But the local sales ask us to drop it and re-construct our IPCN from APPRO's referrence design, because the 2A lib cannot run in DVSDK. If that is not the truth, does anyone else succeed to use TI's 2A in DVSDK?
Hi Yang
Thanks for your reply. Can you tell us more detail about the wrong result of TI's lib? and how did you write the lib for your own, does TI provide reference code for the 3A driver? Thanks!