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.

TM4C1230H6PM: What do i need to do when moving my project from TM4C1294 to TM4C1230D5PM?

Part Number: TM4C1230H6PM
Other Parts Discussed in Thread: TM4C1230D5PM, EK-TM4C1294XL, EK-TM4C123GXL

My current project is done on TM4C1294, now I am asked to down scale to TM4C1230D5PM, with fewer features, of course. Any pointer on how to do it properly? thanks

  • Hi David,

      We don't really have a migration document from TM4C129 to TM4C123 per se. Both MCUs shares the same TivaWare library. The most important things when migrating from TM4C129 to TM4C123 would be the pin mux configuration as the two MCU are not pin to pin compatible. The clock configuration will also be different. Other than that, porting from one to another should be straight forward. You do need to take into account some features that are available on TM4C129 may not be on TM4C123. Just to give an example, if you use QSSI on TM4C129 for its advance features (e.g. Bi and Quad SSI functions) then they are not available on TM4C123. If you use only the legacy SPI mode then the code can be reused. It really depends on which peripheral and what features you are using. If you use uDMA then the channel assignment will be different. 

      With that said, I will suggest you take a look at the TivaWare examples for TM4C129 as well as TM4C123. Peripheral examples under C:\ti\TivaWare_C_Series-2.2.0.295\examples\peripherals are written to support both MCUs. You can see that they are mostly common between the two except the clock and pin configuration. You can also look at the CCS examples under C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c123gxl for TM4C123 and compare to the examples in C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c1294xl. The difference for each example will be quite minimal. 

      Lastly, please also be aware of the TM4C123 errata.