EK-TM4C123GXL: Flashing for debugging fails

Have you:

• Power Cycled your board
• Power Cycled your PC
• Attempted to Download your (last) KNOWN GOOD - WORKING PROGRAM  (free from your 'intvec_table' creation)

Should you have a (proper) 'J-Link' JTAG/SWD Probe - there is a facility to, 'Restore the MCU to its factory-released condition.'

It is suspected that your 'creation' altered one (or more) of the MCU's JTAG pins - which proves - NOT a good idea...

Greeting Charles,

Once again - the 'desire' to, "Create one's own" (which never/ever is explained or justified) has cast (another) poster into Hell...

BTW - I'm unsure if the 'altered intvec_table' - by itself - fully encompasses this poster's 'modifications.'     As you & I know - 'Total Recall' - post such Disaster - proves (often) suspect...

Often you/I note - poster's use of, "Known Good - Vendor Supplied Projects" - in which the 'heavy lifting' is DONE FOR the POSTER - proves a FAR SUPERIOR PATH!

Hi cb1 Charles and Peter

 Thanks for reply.

>    Attempted to Download your (last) KNOWN GOOD - WORKING PROGRAM  (free from your 'intvec_table' creation)

     I can't download the KNOWN GOOD - WORKING program any more. It is not clear to me why even this doesn't work. It seems something in MCU has been "destroyed" by the software.

     I changed my intvec_table somehow according to youtube course "Modern Embedded Systems Programming", just want to understand how it works.

What I can confirm is:

• Hardware on Tiva-C board hasn't been changed.
• The ICDI driver is OK

     Actually I would expect that the MCU can be stored to factory-release state, either by pressing a button + holding some seconds or other ways , but in the Tiva-C Launchpad User Manual, I can't find it.

Can TI gives me a hint how to achieve that ?

   Thx

    Xun

Hi Xun and Charles and (even) Peter,

In my opening post (first one here) I advised, 'There is a facility to, 'Restore the MCU to its factory-released condition.'     THAT IS - what you want - is it not?

That's the same advice as vendor's Charles provided - yet it (may) not be implemented w/in 'IAR' - but instead - w/in the (many) support programs - which are supplied by 'Segger' - specifically for use w/the extremely powerful 'J-Link" JTAG/SWD Probe.    Minus the 'J-Link' - I suspect that you may be forced to employ the 'link' which Charles thoughtfully provided.

Charles mention of "unlocking" is the same as my writing, 'Restore the MCU to factory-release state.'      There are (at least) TWO Paths - to the identical Destination - which is the, "Return of your MCU to its (earlier) Functional Capability."

Attempts at 'learning/improving' are commendable - but videos from 'unknown 3rd parties' - are (ahem)  not famed - for being  'WELL THOUGHT and CONSERVATIVELY IMPLEMENTED.'    Sad to note - poster Xun - has been among the most recent - to fall victim...

To friend Peter - your statement, 'non-RTOS example projects have a statrtup_ccs.c file' likely 'missed'  -  the fact that poster Xun is employing IAR  (first few words of his opening post) and that (most any) .ccs file is (unlikely) to provide comfort!     Indeed details, details - ALL of the facts must be identified - so that such 'mistakes' may be minimized.    (even prevented...)