Difference between Stellaris LM4Fxxx and Tiva TM4C

Hi Sue,

Thanks for the response.

I found the documents in http://www.ti.com/product/tm4c1232h6pm.

Regards

Hemant

Hi Sue

Can we expect to be able to run our Stellaris firmware in the new parts? Correct if I'm wrong but in the case of LM4F232H5QD the silicon is the same, so we can think to just download our binaries and run?

Thanks

German

Yes German.  You can run existing LM4F binaries on the corresponding TM4C devices.

Regards,

Sue

Hello Sue,

I believe this was asked in another post but I can't find it now, but for the old LaunchPad, can the LM4F that is on there be replaced by the TM4C that is on the new LaunchPad?  Also, I haven't looked at the entire line of LM4F, but is there pin uniformity across the product line similar to the competting STM32F?  Can I design one board, have one basic layout and simply sub in a new TM4C with the features I need?

Thanks,

Hi Greenja,

Yes - you can replace the LM4F part on the Launchpad with the equivalent TM4C device.  In general, there is uniformity in pinout, with the exception of fixed signal pins that may or may not be on a device.  To be safe, it is always best to compare the pinouts of the 2 devices.

Regards,

Sue

I just want to get further clarification on this response to the previous posters question.  His question was can we remove the LM4F120H5 chip that is on the current Stellaris Launchpad and replace it with the TM4C123GH6PM that is found in the new Tiva Launchpad?  If this is possible, do we only need to replace the single chip that is the chip that gets programmed, or do both of the chips need to be replaced as there were two LM4F chips on the Stellaris Launchpad?  From what I read, it seems that I should at least be able to replace the single chip and have everything but perhaps the OTG mode of the USB not work.  Would this be a correct statement, or were there other changes that happened to the board layouts in the upgrade from the Stellaris to the Tiva Launchpads?  If there were no other changes, then I would gladly swap out the chips on my Stellaris boards for Tiva chips.

Adam

Hi Adam,

I'm sorry.  I didn't read the question correctly.  You can put the TM4C123GH6PM on the old LaunchPad boards, but you won't have access to the USB OTG feature.  But as I said, there's really no difference between the Stellaris device and the Tiva device, so there is no need to swap out the device at all.

Regards,

Sue

Sue,

Thank you for the response.  For some, there is not much of a difference, but for others, the hardware based PWM blocks make all the difference in the world.  I am not as worried about the USB OTG.

I also wanted to make sure that it I dropped in the new chip that I would still be able to use the onboard debugging that was provided without having to swap both chips off the board, as well as having it work with the Boosterpacks without having to do a bunch of code changes.

Adam

Hi Adam,

I understand.  The debug and boosterpack operation will not be affected if you change the chip to the Tiva device with PWM.  No need to mess with the debug MCU.

Enjoy!

Sue

Thank you Sue for your help on this.  It looks like I will be switching out the single Stellaris chip for a Tiva chip on my boards.

Adam

Hi Sue,

if I understand correctly, there aren't hardware differenze for both devices (LM4F vs TM4C), but only about chip software loaded that communicates with the usb ports.

Is it?

So, is there a way to update the oldest launchpad (LM4F) to newest software booloader Tiva (or what it is...)?

I have more LM4F launchpad that could be used, How I can migrate to the new platform? Could I use a launchpad to update another one? Or, is there a more simply manner?

Regards,

Cosimo

Cosimo Orlando said:

I have more LM4F launchpad that could be used, How I can migrate to the new platform? Could I use a launchpad to update another one? Or, is there a more simply manner?

 Hi Cosimo, I see you requested to me about migration question, my trouble is where to get new devices and missing of ENET peripheral, so As other WE still need LM3s9xxx part where obsoleted, ti still speak about NRND but no silicon exists and no public plan is announced about what is to be released soon.

 The two chip on launchpad perform different task:

   - the one parallel to board act as an ICDI inferface emulating FT2232 chip, you can leave this in place, it is fine for all family of tiva (birth dead)Stellaris and competitor too.

   - The slant one is the target you can use to develop code, this one can be swapped with 64pin TIVA parts when available and programmed by jtag or bootloader too. Still new TIVA launchpad are in backorder as TIVA samples too.

 At first look TIVAWARE and STELLARISWARE seems to be same on LM4F TM4C parts, just someone had a very bad idea to change name adding pain to NRND trouble too.... At datasheet compare also silicon appear at first glance to be same part with different name. Just a crazy operation again more worst than first one... Link, tons of forum and internal TI pages are pointing to null where it was stellaris.

 Again on Stellaris LM4S and TIVA new part I am still in test phase, I connected an 3.5 LCD to a launchpad Lx4f120, porting is working partially, flash is not large enough to fit all graph images and still not enough ram is in place. LCD display images and work forever, SPI and uart when graphics is in place both stop at first SD access...  Next step after fixing SPI trouble is to communicate with FPGA but for now experimental code was working on Stellaris is not ok on Lx4F.

I ported kitronic driver and it work on SD example or alone.

 I try'd GRLIB demo but doesn't fit, I removed some feature, fit but doesn't work.

 I ported SD_card example, access SD work alone but has trouble on subdir too....

 When I activate Kitronix driver SPI and UART Both stop work on first SD access.

 I am working on Linux environment and error locating files report searching c:\stellaris..... What is c:\ on linux???

 To replace LM3S9D95 I am redesigning all interface, none competitor has a direct drop in so I am experimenting some hybrid TIVA C2000 OMAP.... This is last attempt before to definitive switch out from TI stellaris_TIVA , if this fail within two week just expensive and time consuming definitive migration to Freescale or NXP or abort a two year development.

Dear madam,

May I know simply, stellaris Launchpad  ( LM4f120H5QR) TDO,TDI,TCK,TMS pins can used to Debug and Program TM4C1230H6PM microcontroller.

Hello Harsha,

These pins work the same way on all LM4F and TM4C devices.

Regards,

Sue

hello Sue

Im in big trouble...
I have two  Lm4f120 launchpad both are working properly,

using debug out i try to debug customer board (TM4c1230H6PM) more than 1000 times...but it not success. finally I thought there can be error in customer circuit board.

then i  remove one processor in Lm4f120 launchpad and replace by tiva processor ( even thou TM4c1230 is not a equivalent one, JATG , voltage, and other essential pins are same ).  but that effort  also NOT success. give same error....

i try to program using CCS, keil, energia and LM flash programmer..but it say 

< **ERROR**; cannot find target device ! > 

several time i try to unlock jtag port using LM flash programmer ..  sometime it say have to power cycle the board but sometime it say 

<**ERROR**>; Failed to unlock connected device! 
 

thank you

Hello Harsha,

Have you carefully followed the directions on how to configure the Launchpad fore Debug Out (http://processors.wiki.ti.com/index.php/Stellaris_LM4F120_LaunchPad_Debug_How_To)? Have you carefully compared the debug circuitry on the launchpad with the customer board?  I suspect you are correct that there is an error in the customer circuit board.

Regards,

Sue

Sue Cozart said:

 For software porting, please see this document.

That porting document link is broken.  I found another one here.

hi, Weather Stellaris program for PWM is work in C2000 launchpad or not?.,please clarify.

Thanks&best regards

Naresh.

Hi Naresh,

The C2000 and the Stellaris/Tiva products have different PWM modules, so the code will not run on the other architecture without modification.

Regards,

Sue