• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 200 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TM4C1294NCPDT: Do TM4C microcontrollers come preloaded with the TivaWare bootloader?

Christopher
Prodigy 20 points
Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: EK-TM4C1294XL

I am thinking of using the TivaWare booatloader but I would like to clarify the one thing.

In the introduction page (p.5) of the Tivaware Bootloader for C series user guide, the following paragraph is written.

It says that "The flash boot loader is a small piece of code initially loaded through the JTAG debug port.".  Does this mean that you have to initially load the bootloader using the JTAG port or is it possible for TM4C microcontrollers to come preloaded with the bootloader software so that you can program without having to use the JTAG?

Best Regards,

Christopher

  • +1
    TI__Guru**** 182656 points

    Hi,

      There is the ROM-based bootloader. In this case, the bootloader is already preloaded on ROM. For UART, I2C,and SSI, the ROM boot loader is fixed for UART0, I2C0, and SSI0, respectively. If the application requires the use any other instance of the peripheral, then a flash boot loader must be used. For example, if your application requires to bootload through UART5 then you must use the flash-based bootloader as it provides much more flexibility as to which interface to use. TivaWare library provides the flash bootloader and you can find the examples such as C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c1294xl\boot_serial which bootloads through the UART. The flash-based bootloader must be programmed through JTAG first. Once it is running it will download the application firmware through the communication interface (e.g. UART, SSI, I2C, CAN, Ethernet, USB) that you configure.