• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 2002 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Basic code examples for TM4C micro controller

Josue Pareja
Expert 1605 points

Hello every one, I was working with the msp432 and I recently obtained a TM4C129E, i have downloaded Tiva Ware, but I only found code examples using the DriverLib library, are there any basic example codes (ADC, PWM, TIMER, USB, UART) that dont use DriverLib librarie?. Maybe some examples like the ones that the MSPware have (very simple and well explained)???

Thanks!!!!!!!!!!!! 

  • 0
    Guru 117855 points

    May I suggest that the, "DriverLib" IS your friend? And not to be avoided.

    DriverLib is: Tried/True/Extensively Tested - and has been used successfully by thousands! (even moi)   So - to reject this resource - is NOT w/in your best interest.

    Indeed it is vast - but you may, "divide & conquer" - and succeed - by examining, "One Peripheral at a time."    You should note, "Examples/Peripherals" which exposes many, many code examples - again each organized by peripheral.

    This effort is vastly eased by your search & find - then read/review of, "Peripheral Library User Guide."   Again this detailed guide will prove immensely helpful to you - and is divided by MCU peripheral.

    ARM MCUs are complex - you must allow sufficient time for your learning - this vendor's vast code examples & supporting documentation are quite good and have enabled many to succeed.   (even (sometimes) moi)

  • 0 in reply to cb1_mobile
    Guru 11940 points

    Again, I would like to second cb1 on this point.

    I think I recognize the OP from the MSP430/432 "parallel" forum. That might explain his request. Older 8-bit and 16-bit MCUs were less complex, and are often managed with "direct register access" code. This method is still the prevalent one on the MSP430 forum, even with code suggestions from gurus.

    However, as cb1 noted, the complexity has grown, and DRM code becomes unmanageable (and has always been hardly readable) with this MCUs. Having a tested and robust library saves you much effort and time. And, with the quality of modern compilers, much more can be achieved by "playing" with optimization levels than with trying to beat the compiler with hand-optimized code...

    This effort is vastly eased by your search & find - then read/review of, "Peripheral Library User Guide."   Again this detailed guide will prove immensely helpful to you - and is divided by MCU peripheral.

    The datasheet, with a detailed description of all relevant peripheral registers (and their function) will always be a recommended read, too.

  • 0
    TI__Guru**** 244380 points
    Hello Josue,

    I would 2nd cb1's point as well. The use of DRM from MSP43x devices while supported on TM4C129x is not very efficient in terms of code development, debug and long term maintenance. And we do not encourage users on the use of DRM.

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Guru 47900 points

    Amit Ashara said:
    And we do not encourage users on the use of DRM.

    Quite good, that!   Poster should not "fear" the driverlib - in time he will grow to appreciate its vastness.   (and pre-tested, correctness)

    One (new) forum member demands ASM (and ONLY ASM) - is that equally discouraged?