• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 509 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.

OMAP-L138 Peripheral Header Files?

Judson Wilson
Intellectual 620 points
Other Parts Discussed in Thread: OMAP-L138, OMAPL138

I am looking for a good set of header files for the OMAP-L138 registers.

I have the "cslr" files that come packaged with the "PSP drivers".   These files are pretty difficult to use, whereas for all the C2000 microcontrollers I have used come with a great set of header files, complete with struct bit fields (rather than clunky macros), that are directly mapped to the registers via a linker config file.  Is there something like that out there, or in the works? It would make my life a lot easier.

Thanks.

  • 0
    TI__Genius 9490 points

    Judson,

    are you aware of the omapl138 starterware? It even includes non-OS examples for several key peripherals on the device.   http://software-dl.ti.com/dsps/dsps_public_sw/c6000/web/omapl138_starterware/latest/index_FDS.html

    Once you unzip it, you will find header files with the register definitions under the C:\Program Files\Texas Instruments\OMAPL138_StarterWare_1_10_00_00\include\driver\hw folder

    I hope this helps.

    regards,

    miguel

     

     

  • 0 in reply to Miguel A. Alanis
    Intellectual 620 points

    Thank you for the response.

    I took a look at the files you suggested, and they appear to be even worse than the "cslr" files I found originally.   The cslr files at least use some C structs, whereas the starter files are 100% macros and a layer of somewhat pointless functions on top of that.

    The files that TI writes for the C2000 are orders of magnitude better in terms of usability and benefit.  With those files I can simply add a few structs to my watch window and instantly expand the structure to see many registers, broken down into individual bit fields (so I don't have to decode hex in my head, a process that usually ends in failure).  The code then uses the same exact syntax to manipulate the registers.