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.

What are the OMAP4 specific Native APIs available to OMAP4 developers apart from Android APIs?

 We have an OMAP4 customer using Android ICS 4AI.1.7 who is trying to understand if additional APIs are available through TI or is it only the regular Android APIs?

Customer is familiar with what is available through Dalvik JVM. What they are trying to understand here is whether the omap platform provides them with additional APIs (besides the regular Android ones).

 

I understand that apart from Android APIs, we also support some native APIs to access OMAP4 specific HW capabilities. Do we have a documentation with the list of those APIs? Any app note on how to use them?

Thanks

 

  • Harini

    I had found next information when checking the code, it is the same folder organization for ICS and JB releases.

    http://omapedia.org/wiki/Sensors_for_OMAP

    accessible from sensors code

    /mydroid/device/ti/blaze/libsensors

    /mydroid/device/ti/common-open/sensor_test_app

    /mydroid/device/ti/blaze/liblights


    there is code to access OMAP features or values

    /mydroid/device/ti/blaze_tablet/dumpstate

    /mydroid/device/ti/common-open/board_identity

    I read that this can be accessed from apk in the same folder than library is.

    there is a s3d code that is used

    /mydroid/device/ti/common-open/s3d

    next post has some more information about S3D

    http://e2e.ti.com/support/omap/f/849/t/224466.aspx



    Next link I think is used by init.rc changing chmod or user and then writing directly to /sys, but to use them from an APK it will require to add some extra code in Android plus some permissions.

    http://omapedia.org/wiki/GPIO

    The other day I was thinking that it could be something like the code used for leds from sensor's library.

  • Manuel, Harini,

    I am most interested in the board_identity information.  However my understanding is that with an android dalvik app that an additional add on package must be offered to expose these new API's to the application.  Does TI offer an addon package that I just don't know about?  

    This page doesn't reference any addon package available:

    http://www.omappedia.org/wiki/4AI.1.7_OMAP4_Icecream_Sandwich_Release_Notes

    I don't think (since I am only an application) that I should have to build the entire android stack to expose a new API.  

    Perhaps you can show some reference dalvik code I can run on the tablet / STB device?

  • The code is just reading a "/sys/board_properties" value from the system that is available with normal user. It is not directly accessing a HW or System service for it.

    Check next file,

    ./mydroid/device/ti/common-open/board_identity/src/daemon/Identity_daemon.c

  • Manuel,

    I finally have a blaze tablet basically up and running and I went into the /sys/board_properties directory I next descended into the soc/ and board directories.  Nothing in there seems to be a unique identifier for this INDIVIDUAL board or SOC.  the only thing that might have been close with the production_id value, but I can't tell if this is unique to this board or to all the blaze tablets.

    Can you identify for me the entry in the sys/board_properties that shows a unique identifier for this particular unit?

    Thank you.

  • You may be referring to next file

    ./4ai17/kernel/android-3.0/arch/arm/mach-omap2/board-44xx-identity.c

    this file contains information about different board that are described by /sys/board_properties

    by using regular 4AI.1.7 release and doing a cat and ls to /sys/build_properties I can see next files

    shell@android:/ $ cat /sys/board_properties/soc/*                              
    die_id          family          production_id   revision        
    dpll_trimmed    max_freq        rbb_trimmed     type            

    they are the ones referred by next file

    ./mydroid/device/ti/common-open/board_identity/src/daemon/Identity_daemon.c

    Another way to read this information is using OMAPCONF

    https://github.com/omapconf/omapconf/wiki

    Print CPU details (revision, type, fab, DIE ID, ...):
    # ./omapconf --buildinfo

    By searching in Google.com I found next post in Google's forum site

    https://groups.google.com/forum/?fromgroups=#!topic/pandaboard/hveEs19Uekw