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.


Part Number: EK-LM4F120XL
Other Parts Discussed in Thread: TM4C123GH6PM, EK-TM4C123GXL


I am new to this one.  I started using Keil and LM4F120H5QR development board. I am following course of EDX. My question is on how to download code to board. When I hit "flash" button, it gives me below error.

"Error: Flash Download failed  -  Target DLL has been cancelled"

Also, while searching solution for this , I found two ways to download code one is using JTAG and other one is through stellaris ICDI. Does any one know what is the difference between these two. what setting should I change so that I want to use stellaris ICDI and transfer code to board.



  • Hi,

    The LM family of devices have been replaced with the TM4C family of devices. I will suggest you start your development with the TM4C development boards. The development boards starts at $12.99 plus you can get full support via e2e forum. See development board in this link. I'm not familiar with the LM series neither the ESX course.

    But to answer your question, the Stellaris ICDI is a JTAG/SWD based debug probe. You can use the ICDI debug probe along with the debugger (i.e. your Keil IDE) to debug the processor and program the flash.
  • Hello Charles,

    Thanks for Reply. So for flashing code on to chips, do I need to have another set of hardware or I can download code using USB connector.  Below is the screen shot what I am seeing on Keil.

    4380.New Microsoft Word Document.docx

  • May I encourage you to follow Charles' direction and acquire the much newer, more powerful, and better supported "TM4C MCU" family?

    The LX4F120 board you note (there were never any LM4Fs produced) was this vendor's first venture into the Cortex M4 - and that MCU was among the few to "bypass" the powerful, "PWM Module peripherals."    You may still generate PWM signals (via the MCU's Timer Module) but w/out the fine control & functionality offered by the full-fledged PWM Generators - which "failed to make it" into that particular MCU.      (Some say "Lucy" pulled away (more) than just the football)

    You may still be able to find (past) StellarisWare Ver 9453 - which was the only version to support LM3S (even older MCUs) and the LX4F series... It may be possible for you to run that (older) LX4F under TivaWare - you'll have to add the chip-descriptor code for that device (enter that w/in pin_map.h) - and carefully scan for the "missing bits & pieces" which "escaped" your device & are crammed w/in - TM4C...

  • Hello Cb1_mobile,

    Thanks for response. Actually I am following course of It was taught by professors from U .texas ,Austin. They recommended this board.MCU on this board is Tiva™ TM4C123GH6PM. and launch pad is stellaris LM4F120 series.

  • Hello back - palindrome user.
    It is doubful that you'll EVER find a TM4C on a Stellaris LPad - especially as (again) - if you look closely - your part is marked LX - not LM...

    Note that the good professors also, "recommend DRM - style coding" - which is "outside" of Vendor and Outsider approval - as some here have "time-schedules to meet" - and the endless scan of arcane Register bits was deemed inefficient - many moons ago...
  • Hello,

    My part is "LM" . As I didn't see "LM" in the drop down list I selected LX . From your discussions, I think my problem is "I am missing few things which are needed to download code in to board". I don't know how to configure Jtag/Stellaris ICDI so that I can download code in to board.

  • May I ask if you're (actually) able to read any "LM4F" marking on your chip? (I'm not speaking to any silk-screened, board marking - and/or print literature. Firm/I have many such MCUs (well over 2K left) and each/every one bears (indisputable) LX4F marking!

    It is unclear as to "What you have" also in terms of (either) the Stellaris (past) or Tiva (new) code library. You may note that I've (earlier) listed the exact Stellaris version which was intended for your LX4F MCU. (indeed - vendor and Keil list only LM4F - yet the part is (for sure) marked LX...) May I suggest that you re-read the early posts - and then identify what you have - and either Charles, myself or another (but never a professor) will attempt to assist further...
  • Hello Cb1,

    I don't see any "LM4F" marking on the the board. I see chip number as EK-TM4C123GXL and the board as Tiva C series launch pad.

    As I said, I am very new to this and learning this for first time .

  • We don't seem to be communicating - I've suggested that you "Read the markings upon the MCU chip." Never/ever would the MCU be marked "EK-/TM4C123GXL" ... the EK marking is that of an Eval board.

    It must be that there are (some) usable instructions w/the course particulars - perhaps starting "fresh" early tomorrow - proves best.

    I've advised you as best I can: listed the proper (past) version of StellarisWare (yet we remain uncertain as to what your board actually is!)

    Your initial posting here - listed most clearly "LM4F120" - yet now you report seeing "EK-TM4C123..." - that's "Crazy Making" (for your helpers) don't you agree? (Pardon but I've a gf who has mastered that skill - no fun to encounter it (here) ... too.)
  • Hello,

    To avoid further confusion, see attached document. It contains board I am using.



  • knr rnk said:
    professors from UT, Austin ... recommended this board Tiva TM4C123GH6PM ... launch pad is Stellaris LM4F120 series.

    Is it difficult to note the source of confusion?      The two parts just described - w/in your quote - are quite different - are they not?

    I've asked - several times now - if you'd assist by (simply) reading then reporting the chip markings (NOT board markings) on the board you (claim) to have.    (it is believed to be identical to the one I've just photographed.)    (shown below)     You may note that the MCU is indeed an "LX4F" not an LM4F - as NO LM4F devices were released to the general public.

    I specifically asked for you to make such chip identification to learn if we could (communicate) and if you'd be responsive to direction.     (Minus either - our time here would be unnecessarily long - and hard.)     If you wish to use (this) board - do note its limitation - which I outlined for you - far earlier.       The good professors MUST have provided the (Most Basic and Required) "Programming, Debug, and Downloading" instructions - is that not so?     Perhaps you'll have more success "following their direction."     Great attention to detail IS required in this field - and "failure to steer towards course" is unlikely to "end well."