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.

TM4C1294KCPDT: Migrate existing LM3S4B92 design to TM4C1294

Part Number: TM4C1294KCPDT


  1.     My existing LM3S9B92 design is a key board, use 50 GPIO to control and receive data on the key board, receive touch screen data from the build in USB port, and send out the key board and touch screen data to a PC through the Ethernet port. The design use LM3S9B92 build in Flash, SRAM and ROM only (Internal ROM loaded peripheral Driver Library, bootloader and more), no external component are used.
  2.     Is the TM4C1294 a good MCU to replace the LM3S9B92 MCU? If TM4C1294 is used in the new design, do I need add an external EPROM?
  3.     May the existing StellarisWare firmware migrate to VivaWare for TM4C1294?
  4.     Any one may recommend a better solution, please? A block diagram is very much appreciated.  

  • Hi Wing,

    Wing Wong said:
    Is the TM4C1294 a good MCU to replace the LM3S9B92 MCU? If TM4C1294 is used in the new design, do I need add an external EPROM?

     Yes, the TM4C129 will be a good replacement for LM3S. TM4C129 contains on-chip EEprom but you are welcome to use external EEprom per your application requirement. Please do take take into consideration some errata associated with the internal EEprom during your design. 

    Wing Wong said:
        May the existing StellarisWare firmware migrate to VivaWare for TM4C1294?

    Please see below migration document from Tempest/Firestrom Stellaris devices to TM4C129 devices.