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.

EK-TM4C1294XL debugging IAR

Other Parts Discussed in Thread: EK-TM4C1294XL

Hello everybody!!

I am planning to buy EK-TM4C1294XL board and I need to be shure that this board alone is capable of download and debugging actions with IAR. I have been reading the documentation of this board and I think that it is possible, but I want to be sure. Somebody could help?

                            Thanks in advance!!

  • Hello Perico

    I can confirm it works with IAR... Examples also would not be released for an supported tool-chain

    Regards
    Amit
  • Hello Amit Ashara.
    Thank you very much for your answer. Sorry, but I do not understand "Examples also would not be released for an supported tool-chain". Could you explain it to me?
    Regards.
  • Pardon - if I may - vendor's (sole) rep has huge workload - suspect that writing may have intended, "Examples would not be released for an unsupported tool-chain!"  (I had same reaction as you - reading the earlier reply...)

    As multiple code examples appear w/in the IAR format - such indicates that IAR is supported by vendor's code examples - your targeted MCU...

  • Yes, that is what I suppose that Amit wanted to say, but as I was not sure, I decided to ask to be sure...
  • There exists yet another means to, "calm your fear/uncertainty."  Open IAR - then, "Projects > Options "Select Device"" should list supported MCUs by vendor.  

    Two precautions:

    a) we always use this vendor's supplied code examples - not IARs.   (and ours is multi-seat, paid IAR)  This due to the fact that this vendor's examples are (always) more current/up to date - and may be more extensive, too.

    b) your 129x device requires several (multiple) variations in long-standing system clock and peripheral set-up/configuration.  (especially I2C)  Note that the system clock frequency now requires a different function - and that "SysCtlClkGet()" is error-laden.)   These are "some" - not all - of the "gotchas" - your job entails more forum & MCU errata read/review.

    Might this (extra care/effort) warrant your "Verified Answer" tick?