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.
Amit has announced that updates are being prepared for the "DriverLib User Guide." (well...not really!)
Vendor experts have prepared - yet the voice of user-clients offers a broad perspective - and may serve to enhance and/or speed this effort.
May make sense to attempt to "prioritize" any listing of such updates. Goal may be, "Most good for the greatest number."
As some (equally critical) gatherings advise, "Speak now - or (forever) hold your peace."
[edit 12:05 CST, 16 May 2015 Title changed from, "Call for User Inputs"]
cb1- "Speak now - or (forever) hold your peace."
Ok already - this reporter (instigator in this case) rises to the bait. (99 first day views - not a single bite - headline writer needs, "talking to.")
Follows several suggestions to strengthen the "DriverLib User Guide."
a) Far more detail aimed at, "Care/Handling of the (external, user supplied) analog circuitry." Again - this is (external) to the MCU - it describes the user's treatment of the analog signals (prior) to their presentation to the MCU! Too often - as well noted here - user's allow the analog pins to "float" - and then "protest" when ADC readings seem (outside) their expectations. ADC pins need to be properly connected/terminated - existing ADC "input specs" (rear of the manual) appear too complex for many, here. Suspect that sample schematics - w/"general" part values - will go far to improve.
b) uDMA was among the last peripherals added to these MCUs. And - if memory serves - the written descriptions, number, and variety of (properly) detailed uDMA examples must be increased. There are many "hooks" and sometimes even the sequence of uDMA set-up/config proves vital - especially when the uDMA manages & coordinates multiple MCU peripherals - running at high speed. Suggest the "most likely peripherals" to benefit from the uDMA be well represented - w/detailed, application-ready examples.
c) Interrupts - due to their inherent complexity and demanding requirements - require more detailed description & illustrative examples. The (usual) requirement to define/detail the interrupt handlers w/in the "start-up" file is too often missed - signalling the need for greater emphasis. And it cannot hurt to (gently) suggest that the (near) universal trend of placing, "Calls to the UART" w/in interrupt handlers (which should be quickly executed so as not to prove disruptive) should be resisted. Simple toggle of test Leds far better confirms interrupt entry - w/out over-burdening the program. (not a word to this guide exists...)
d) JTAG - though not a "prime MCU feature" - when, "MCU cannot connect" - users are pretty much, "Dead in the water." Indeed laundry list of, "What to do, now" exists - but forcing frustrated & already delayed users into google or site search - appears not the best/brightest method of advisement.
I can list more - yet the richest response results from varied User Input - which Amit has invited. (after just a "bit" of arm twisting)
Here's a (rare) chance to, "Post your greatest, "DriverLib Update needs." Pity if your key need is "missed" - which may be prevented - with your brief listing here!
Should this thread remain, "empty/under-served" - a strong message that, "Users do (not) really care" seems sent - does it not? Even a quick, single item is likely to "blip" this vendor's radar - this is our chance to gain, "some voice" in vendor's actions...
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to cb1_mobile:
Hi Amit, As gleaned from, "Advertising 101" - if readers don't note & respond - change the "Headline!" "Monster ate my Tiva" (unfortunately - already taken) so I updated my past, "Call for Updates" w/"Tell T.I."
And now note that the "sticky" lost its adhesive properties in that process. (may not be all bad - response was not what I had wished for/anticipated...perhaps "drift into obscurity" has been earned...)
In reply to cb1:
Silence deafens - does everyone landing here have absolute mastery/understanding of each/every element of MCU's Bootloader?
That one "left open" so that "youse guys" could request.
It's long said that we, "Get the G'ovt we deserve." Might a similar fate await this updated DriverLib User Guide - minus any forum-user input?
For more reply options press "Use rich formatting" on the bottom right.
I have a blog that i am making to help some colleagues with learning Tiva: https://sites.google.com/site/luiselectronicprojects/homeI have here now example codes for the Tiva more organized: https://github.com/LuisAfonso95
In reply to Robert Adsett72:
Indeed Robert - indeed. Some here have suggested that ALL such data be immediately "clickable" from the red bar - atop this forum. That bar holds the (uber) critical, "Blogs, Groups, Videos" - clearly: "MCU data, App Notes, & vital DriverLib Guide" should be there too!
Unclear, "How, when & why" the obscuring of vital data has resulted - and been (apparently) "cast in stone!"
Not manual but the library itself
(u)int32_t is over used. Some of the uses should be replaced with other types. Obvious examples are
There should also probably be more general use of types rather than using the (near) bare compiler types for everything.
In reply to Robert Adsett:
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.