• State TI Thinks Resolved
  • Locked Locked
  • Replies 13 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 1800 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.

TM4C123GH6PM: Looking for example codes for the peripherals

sonMEE
Intellectual 460 points
Part Number: TM4C123GH6PM

Is there sample/ example codes to test every peripheral ?

Thanks

  • 0
    Guru 117855 points

    If you're willing to "Search FAR" ... C:\T_Ware\Examples\Peripherals ... (unleashes  12  MCU  Peripheral-based,  Example Sets - in my installation...)

    You must have (already) installed T_Ware - for such to occur.

    Note too:  The "(Peripheral)  Driver Library User Guide" (found w/in T_Ware\docs\) - provides exacting DETAIL - and is  MOST EFFECTIVELY ORGANIZED - on a,  "Peripheral by Peripheral BASIS!"     (vendor - on occasion - CAN get things right... [when not banning "LIKE" and AVOIDING the eased correction of  R9/R10 "Plague-Istors."])    

    At the rear of each "Peripheral Section" - a "reasonable" code example appears - aiding client-user practice & understanding...

    Now you ask for code "To TEST" each/every Peripheral - and such is RARELY Provided!     Are there not differing standards of  "Test?"    Who is to decide - to govern - what constitutes a "Fair & Proper" such test?    Devil in those details - ALWAYS LACKING...

  • 0
    TI__Guru*** 135355 points

    Hello Shamson,

    Just two comments to add to cb1's detailed and accurate reply,

    His mentions of T_Ware refers to our TivaWare library software downloaded from: http://www.ti.com/tool/SW-TM4C

    Further, additional examples for peripherals not found in the "Peripherals" folder may also be found in the TivaWare examples folders under "Boards" rather than "Peripherals", and then you can select your TI EVM and find further examples for USB, DMA, etc.

  • 0
    Genius 3850 points
    The data sheet is the best place to start.

    Others code could help as well. I wrote quite a few of those modules myself and can post a link.

    You can also look into tivaware to see how it is done. However it can be taunting to go through the code, especially if you are a newbie.
  • 0 in reply to Danny F
    TI__Guru*** 135355 points
    Hello Danny,

    The datasheet doesn't have example code. It will help with understanding the code when Shamson is ready for that, but he didn't request as such.

    Also please don't contradict our advice that TivaWare is the primary source for example code... it is what 1000's of customers use, and that is what we provide support for. Using other code bases would cut Shamson from TI's ability to support them. Anyone evaluating TM4C should start with TivaWare unless they intend to 'fly solo' without TI's guidance and support.
  • 0 in reply to Ralph Jacobi
    Genius 3850 points
    Coding to the device data sheet is an essential skill for any embedded programmer, in my view.
  • 0 in reply to Ralph Jacobi
    Guru 117855 points

    Ralph Jacobi said:
    Using other code bases would cut Shamson from TI's ability to support them.

    And - would cut them from, "outsiders' ability"  (and/or desire) - to "Support & Guide" - as well.

    Some concern remains due to poster's, "Non-detailed mention of Testing, the  MCU's Peripherals."       Proper detail must be provided to secure a (properly) illuminating response...

  • 0 in reply to cb1_mobile
    Intellectual 460 points
    Thanks. I found it
  • 0 in reply to cb1_mobile
    Intellectual 460 points
    Hi. The matter is, for many years I was using Microchip MCUs, that's my back ground. There, the data sheet gives an example to clarify and the explanation doesn't jump from page to page. I used two computers to follow the data sheet, one for reading and the other for jumping when it requires from the current page to that page. It would be nice if the documentation's way is similar to Microchip. When I comprehend the data sheet, then I'll start applying . The problem is when something is unclear, it blocks me for some time. Either I figure it out or I put a question mark. When I read, I write my own comment on the pdf data sheet, thanks to adobe. How ever long it takes, I have to comprehend the structure and functionality of this Processor M4. Thanks for everyone input.
  • 0 in reply to sonMEE
    Guru 117855 points

    Wow - the detail - which may have, "escaped" earlier - has arrived (now) in force!       So very rare - and so helpful - most impressive.

    Long ago - firm/I used that brand - their "refusal" to, "Bend to ARM" caused my firm - surely many others - to flee.     And - during the (very) early days here - that vendor brought a lawsuit against the developers of these (original) Cortex M3, "LM3S" MCUs.     (that firm - "LMI.")

    As one who (past) was charged w/producing such "manuals" - I don't find convincing evidence that, "One and only one vendor"  (to include your favored)  - has a "lock" on clear & compelling manual creation.    Is it not true that the ARM MCU - being far more complex - necessarily must "weave substantially more technical detail?"     And - never have I been asked to, "Confine close-in (related) facts - to a "clustered" appearance - locked (just) to a single page...

    It is both "rare" - and (I believe) quite good - that you have (seriously) considered how you may, "tease out" the highest value data - from (even) "less than" your favored data sheet.     What may enhance your (and others') understanding - is to "highlight key portions of the .pdf" - and possibly to, "Add your own Key "tech fact" summary - especially as regards those areas which "challenge."

    Our group finds it best to, "Integrate our learning" - this achieved via the "Open Data Manual, Significant use of the API,  Much Example Code - loaded into one/several Eval Board(s) - and (reasonable) instrumentation."     (so that you can "quickly/easily" confirm operation.)

    May I note that your "Interest in Test" - unless test was, "meant as understanding" - remains  elusive...     Very good overall job though!

  • 0 in reply to sonMEE
    Genius 3850 points
    "It would be nice if the documentation's way is similar to Microchip."

    Microchip has some of the best datasheets in the business. Freescale and NXP are also up there.

    TI's isn't bad - if you want, check out some of the older Luminary datasheets. I do think some code pieces in the datasheet, as Atmel did, would have been helpful.
  • 0 in reply to Danny F
    Guru 117855 points

    Danny F said:
    I do think some code pieces in the datasheet, as xxxxx did, would have been helpful.

    Agreed - yet - as earlier noted - little prevents client-users from, "Adding to the pdf - to their unique desires" - which (rarely) could be anticipated by the datasheet authors...

    Is not (always) the BEST HELP ...  "SELF HELP?"

  • 0 in reply to cb1_mobile
    Intellectual 460 points
    Thanks for your time