• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 166 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.

TM4C1294NCPDT: Which Programming Method / Tool supports faster Programming speed of MCU - TM4C1294NCPDTT3

Arunasri K
Prodigy 90 points
Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi Team,

We are using TM4C1294NCPDTT3 MCU in our design and TPS3813K33MDBVREP watchdog also. Watchdog Window frame time - Max = 0.3 s

We are trying to flash the MCU using Uniflash Version: 8.3.0.4307 but when we tried flashing its taking some 15seconds to 20seconds after doing setup. Watchdog is trying to reset the MCU after 0.3s.

We are in testing phase, so we couldn't modify the design at this moment. Is there any other ways to flash the MCU faster to avoid the MCU getting reset after 0.3s.

Kindly check and revert back to us 

Thanks,

Arunasri,

Hardware Design Engineer,

Sanmina Tech Services Pvt Ltd, India

  • 0
    TI__Guru**** 191906 points

    Hi,

      Are you loading a .out file or a .bin file? A .bin file will be smaller than a .out file as it has no symbols in it. Therefore, flashing the MCU will be quicker.  How big is your program? If your program is close to 1MB then I'm not surprised it is taking quite a few seconds to complete the flashing. The programmer needs to first erase the flash and then program the firmware. For a large program, it will take seconds to complete. You can refer to the datasheet for flash memory program/erase timing and calculate approximately the amount of time needed based on your program size. 

    What debug probe do you use? A faster debug probe will also increase the speed. The bottom line is that it is unlikely to complete the firmware flashing in 0.3 seconds unless you have a very small program. You will need to somehow increase your WD reset time or temporarily disable it during development. 

  • 0 in reply to Charles Tsai
    Prodigy 90 points

    Hi Charles sir,

    Thanks for your valuable feedback,

    Our program code is 800KB and we are using .bin file only.

    As per our rough calculation: 

    => 300ms (for erasing the flash) + (100us* 6400000/64) => around 10.3 seconds

    800KB = 6400000 bits, in formula added in bits

    Also the debugger we use is XDS110 debug and programmer. 

    But we couldn't extend the watchdog reset time beyond 3seconds, Is there any other tool options for faster programming before 3seconds/ debugger options. please suggest

  • 0 in reply to Arunasri K
    TI__Guru**** 191906 points
    Arunasri K said:
    But we couldn't extend the watchdog reset time beyond 3seconds, Is there any other tool options for faster programming before 3seconds/ debugger options. please suggest

    The programming time is dominated by the intrinsic flash program/erase time as you calculated (e.g. 10.3s). A faster debug probe will not help to reduce below 10.3s.