"What's Unclear" forum thread tops 20K (views/visits!)

For the record - "Best Ever - Boot-Loader App Note - w/Code Examples" had 521 "views/visits" when the above post was created/launched...

Hello cb1

528 between the last update and now. Also its been 1 month since the Application Note came online and it has registered 123 downloads/views (almost 2 a day). With room to improve the application note further, critical feedback has started coming....

Regards
Amit

Hi Amit,

That many downloads in so short a time-frame IS impressive.   But the quality & scope of your note deserves that - and beyond.

As stated - the logic & explanations serve to build & reinforce key/critical MCU "insight & mechanisms." 

The sticky, "Best Ever Boot-Loader App Note w/Code Examples" provides much of great value to this forum community...

I'd like to note that forum users (really) should take advantage of the special opportunity which Amit's "Boot-Loader" forum-thread supplies.   Do be sure to include adequate info - so that Amit (& others) have the best chance to fully/properly assist.   Having "all" Boot-Loader guides, questions, suggestions & recommendations - in "one central (and notable) place" - makes immense sense.  

Full forum response is the best means to insure that this "extra vendor effort" continues - even expands - please do participate & contribute...

Hello cb1-

Appreciate your suggestions and feedbacks. The next Application Note is going to be on JTAG and the nuances of JTAG when connecting devices (beyond just TM4C would be the flavor)

Regards
Amit

Hi Amit,

As you bring JTAG (and SWD - hopefully sooner rather than later) to the forefront - the forum sticky calls out an, "XDS100 JTAG Emulator."   Yet it's not really an Emulator - instead it is generating signals in compliance w/the JTAG standard - is it not?    (thus it's a JTAG Pod or Probe!)

In days past - when JTAG was not yet implemented - we (actually) purchased such, "Emulators" - and it was our "Target MCUs" which were being "emulated."   

The new JTAG standard was expressly developed to "remove the need" for the cost/size & complexity of, "Emulators."  

The subject line of that sticky post (which "What's Unclear" has recently surpassed in hits - (and far faster)) should strike the word "Emulator!"    (such usage is (both) archaic & improper - and too often repeated - spreading confusion...)  

Hello cb1

Yes, while the debug probe came into existence, the word emulator kind of stuck on to them blurring the line which defined each specific hardware. Debug Probe or Emulators or Debuggers, all seem to mash up together.

Regards
Amit

Hi Amit,

Recall our friend & valued poster "Robert" who emphasized the difference between, "Accuracy & Precision." Should such incorrect word usage be continued - thus "rewarded & greatly propagated" - here? (i.e. it is very hard to "miss" that (top of page/sticky) subject line - thus the "repetition of the incorrect "Emulator" tends to embed - that cannot be good!)

If we allow that - bow to that - encourage that - aren't we ADDING to the problem? (does the "style guide" frown on "correcting" a thread's "subject line" - even when - and especially when - that thread is nearing 20K views/visits?

Do not a few (excess) or missed semi-colons (also) "seem to mash up, together?" When does (or should) such mash up become ok?

I actually missed that app note, I have to go check it out.

Hi Luis,

You're not alone. Promotion (when handled by Engineering) never quite, "Blips the Needle..."

This new thread - started this morning - has logged over 400 views/visits! Poorly promoted post (yet of terrific value) was bit over 500 - after nearly 30 days! I launched this thread in the attempt to (better) promote the (excellent) "Boot-Loader" thread - and its added (almost) 100 views/visits - today alone...

I'm afraid changing the name at this date will be as likely as getting people to stop referring to synchronous AC motors as DC motors.

It might be worth an occasional charge but a fulltime quest would be quixotic.

You nudge occasionally on emulation, I'll do the same on the AC motors. Let neither of us be obsessed.

Robert

Robert Adsett72 said:

Let neither of us be obsessed.

Might that be - just a lttle LATE - for this reporter - friend Robert?    And who's obsessed?   Just because you & I had NO choice but to employ (real) emulators - let's give up - let's dumb-down - after all - everything is a, "mash-up" - is it not?  

I looked up the derivation of the word - used it as noun, verb & adjective (in the same sentence) and copy/pasted it multiple times - to the horror of crack staff.

Who's obsessed?

Obsessed? Us? Perish the thought.

As far as accepting, we pretty much have to. English is a pretty fluid language.

One of the irritating changes for me has been the devolution of the phrase "the proof of the pudding is in the eating" to "the proof is in the pudding". I blame the Americans and the earlier shift in the meaning of pudding to be something exclusively sweet.

Robert

Robert Adsett72 said:

I blame the Americans

Who does not?    Yet - while imperfect (despite cb1's best efforts) this fruited plain has been - & remains - top, "Port of Call" for the world.

As noted here - when the "Improper word Usage" is "crammed down each reader's throat" (via Sticky placement) that "misuse" is propagated - thus expanded!

If we are to accept any/all such, "mish-mash" - why bother w/(few) misplaced semi-colons?   (surely they qualify)

If 99 lines of my firm's program proves fine - and 1 line is in error - we are "bums!"   (and must retreat to Mom's basement - and (God forbid) pay Rent!)  

Should not the new, "anything goes, all hail mish-mash" result in this - and other - forums' closing?  Does not programming and work w/MCUs demand clear-cut, "Blacks & Whites" - w/out gray?    Somewhere we're told, "Be careful in what you wish for."   (that's bad grammar)   I (ain't) wishing for more (any) "mish-mash.")

Hello All,

The TivaWare 2.1.2.111 has driverlib bug fixes, suggestions for DRM taken out of example blinky, example additions-corrections, document updates for driverlib and boot loader. This includes unifying the enable and wait for ready functions. Also DRM is downgraded in the documentation. May we use this as a starting point while us at TI work on making changes as per the original thread.

Regards
Amit

Hi Amit,

May I make the (gentle) suggestion of "new tag" listed below?   Somehow seems fitting/proper.  (in light of your use of this "highly viewed" brand new thread)

Never Answered:  "Why ALL of your MCU Data Manuals/sheets AVOID any/all mention of the API?"

Does that make sense?   Many who "follow" cb1 ask me - yet I'm (somewhat) removed from, "Horses mouth."   (and closer to another portion of the horse's anatomy - some suggest...)

This is beyond curious - and has never been explained...

I think it's more along the lines of following accepted uses. Human languages are a lot more malleable and accepting of variation than computer languages.
Robert

And just in case it wasn't clear, blame here was entirely in jest

Robert