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.

Support requied for TIVA C

Other Parts Discussed in Thread: TM4C123GH6PM

Hello everyone,

I am new to ti community. Now i am designing my new board using TM4C123GH6PM. There are some grey area for which i need support from experts. Questions are as bellow.

1) In my application i need a battery backed RTC to read and set date/month/year & time. Is the on chip RTC is sufficient for this purpose or i should use an external RTC chip? Is there any software library to convert tmr0 values to calender?

2) What tool is required to download program to flash in my own board? Can i use Lunchpad and LM Flash programmer to download program into new chip in my own board using 4 JTAG lines?

I will be very obliged if someone answers my questions.

Regards,

Asish

  • For question 1), yes, the on chip RTC should be sufficient, assuming that you have provided an accurate 32.768KHz external clock.  For utility routines, refer to the utils/ustdlib.c module, specifically the ulocaltime function, which will convert seconds to date/time.

    For question 2), the Launchpad is not designed with JTAG out support for an external device.  I would recommend using one of the TI emulators (for example, XDS-100) and the TI Uni-Flash program.

    --Bobby

  • Thank you Bobby very much for your answers.

    I still have some doubt regarding on board flash programming. I am not going to use my target board as a development platform. Then can i use some other easy method to program the new TM4C cheap flash memory of my board?  Is program loading is possible using UART0 as available in LPC1768?

    Regards

    Asish

  • Yes, you may use UART0 as an option for programming the device in your system.  I would recommend that you refer to section 8.2.2 of the data sheet (Boot Loader Overview), as well as the "TivaWare Boot Loader for C Series User's Guide .. SPMU301).  These documents are available on the product page for the device you are using (http://www.ti.com/product/TM4C123GH6PM).

    --Bobby

  • Almost sounds as if you seek to avoid any/all use of JTAG/SWD.  

    Is this especially wise - ideal?   Debug is a critical aid in program development - and is best handled via JTAG/SWD.

  • Thanks for your advice. I will incorporate JTAG/SWD in the board.

  • Thanks for your reply.  Can you please give some idea on the bellow points.

    1) Does TI ship TM4C chip with a boot loader loaded?

    2) If not then then how i can download program to a new chip during production?

    3) is there any guideline/document/schematic  available to guide a new board design. Especially which pins to be used for program downloading.

    Regards,

    Asish

  • Question 1 - Yes, the TM4C device ships with the boot loader in the ROM.

    Question 2 - N/A, since question 1 is yes.

    Question 3 - First, refer to the ROM / Boot Loader section in the data sheet.  It will provide basic details about the boot loader, which peripherals and pins are used, etc.  It will also provide pointers to additional documentation that can be download with more details.  Also, you may wish to refer to the design guide for Tiva C Series Microcontrollers, which may be found here (http://www.ti.com/lit/an/spma051/spma051.pdf)

    --Bobby

  • In addition to Bobby's sound guidance - note that PC0-PC3 classically serve as JTAG pins for this series (and predecessor) MCUs.   We/others often find it far better/safer to employ external pull-up Rs - on each JTAG pin.  (0.15 USD "savings" quickly dissipates/devalues when your board will not, "come up!")

    If  (when, really) squeezed for pins you may consider more mainstream IDE - which enables SWD.  This enables "saving" of 2 of the JTAG pins - and allows their "re-purposing" for your application...

    The boot loader program process is not entirely intuitive nor automatic - to many users.  JTAG/SWD is far easier - and your development time/effort/productivity may rise with its use - at least initially...  Adding complications (i.e. bootloader) - usually not, "best practice" when starting w/a new device/system...

  • Thank you Bobby and cb1_mobile very much for your valuable advice. 

    Regards,

    Asish