• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 33 subscribers
  • Views 1865 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TM4C1231H6PM: Code Integration

yacine ould
Prodigy 130 points
Part Number: TM4C1231H6PM

Hello everybody, 

i've made my own card with a TM4C1231H6PM MCU, and after soldering all component ,

i would like to know how implement my code ?

  • 0
    TI__Guru**** 191886 points
    Hi Yacine,
    The first thing for you to do is to download the latest TivaWare from http://www.ti.com/tool/sw-tm4c. There are many examples included under <TivaWare_Installation>\examples. You can import these examples into CCS and get started very quickly.
  • 0 in reply to Charles Tsai
    Prodigy 130 points

    Hi Charles,

    the software is ok, i've already make my program tested and it's work on the tm4c123gxl eval kit .

    after that i've made my own card with the MCU and some component .

    Now i would like to know how put my code on the MCU   without the JTAG . 

    Regards

  • 0 in reply to yacine ould
    Guru 117855 points

    yacine ould said:
    Now i would like to know how put my code on the MCU   without the JTAG . 

    Might that (specific) question have (better) appeared w/in your FIRST post?       (impossible for Vendor's Charles to know (that) was your real (yet well HIDDEN) desire!)

    Your "rejection" of JTAG can be expected to place "Added & Great demands" upon you.     (and "helpers" here)        You should - at minimum - have that awareness...

  • 0 in reply to cb1_mobile
    TI__Guru**** 191886 points
    Hi Yacine,
    There are several bootloader examples in TivaWare that you can reference to download your code via a non-JTAG interface, such as UART, SPI, Ethernet or USB. The boot loader is a small piece of code that you program at the beginning of flash to act as an application loader. Note that the bootloader still needs to be programmed via the JTAG interface. After reset, the bootloader starts to run and will configure your desired communication port and read your application image. The application image will be programmed to the flash by the bootloader. You can use the LM Flash Programmer GUI to download an application via the boot loader. Please refer to www.ti.com/.../spmu301d.pdf for details.
  • 0 in reply to Charles Tsai
    Guru 92251 points

    Charles Tsai said:
    Note that the bootloader still needs to be programmed via the JTAG interface.

    Isn't it also possible to use the ROM boot loader, without having to program anything via JTAG?

  • 0 in reply to Chester Gillon
    TI__Guru**** 191886 points
    Hi Chester,
    You are very correct. There is both ROM based as well as Flash based bootloader. The poster asked for "how to implement my code?" and I hence gave the flash based bootloader method if he is interested to learn how bootloader works using the TivaWare examples. The poster can ignore the Bootloader Usergide and instead refer to the Boot Loader section of the ROM User's guide www.ti.com/.../spmu367.pdf.
  • 0 in reply to Charles Tsai
    Guru 117855 points

    May it be noted that, "Provisioning for a JTAG Header, pull-up & protective series resistors, & JTAG trace routings" serve as a most excellent, "Insurance Policy" - both during development and long into the future.

    At times - Only "Rescue via JTAG/SWD" - proves the safest, easiest & most direct course...

  • 0 in reply to cb1_mobile
    Guru 10570 points
    Agree with cb1 here. Making no provision for JTAG seems foolhardy.

    Robert

    Actually, I'd view using the bootloader as your first/ primary programming method a bit quixotic.
  • 0 in reply to Robert Adsett72
    Guru 117855 points

    Robert Adsett72 said:
    Actually, I'd view using the bootloader as your first/ primary programming method a bit quixotic.

    Just a "bit?"     Your earlier mention of, "Rejecting JTAG" (i.e. FOOLHARDY) bubbles up (very) quickly/forcefully!

    As ALWAYS - posters fail to present (doubtful they even "consider") (any) justification for, "Inviting Complications" which are almost guaranteed to seriously delay (even jeopardize) their projects.

    Encouraging such, "too early, door-opening to complexity" is unlikely to best serve any vendor...      Some "new-user CAUTION" (Attention to Detail required) would appear warranted - would it not?