tm4c1237h6pz

Hi Bala,

   TM4C1237H6PZ is a microcontroller IC. A microcontroller IC, is a part of a schematic or circuit diagram. See, more info regarding the chip from the link below. You can use the the schematic diagram at the User Guide of the Tiva Launchpad or Tiva Evaluation kit as reference for your design. Also, much better to post this at the appropriate Tiva forum.

   http://www.ti.com/product/tm4c1237h6pz

-kel

Hi Markel

Is TM4C1237H6PZ compatible with some of LM3S?

Best regards

Phuchit K.

@Puchit

What compatibility is being sought. Is it pin compatibility, feature compatibility, if latter which module/peripheral which feature

Amit

Hi Amit

Since I use CrossWorks for ARM version 2.3.4 which does not support for Cortex-m4. It will be soon but I would like start my project first.

The product is security system's board that needs:

1. USB OTG
2. UART
3. I2C
4. SPI
5. RTC
6. Watchdog
7. ADC

So what is the target cpu if I use only cortex-m3 feature on tm4c1237h6pz?

Best regards
Phuchit

Yes, you can find a Stellaris LM3S device which closely matches that peripheral list.  The LM3S3748 is where i would start.  It had a development kit EK-LM3S3748 which highlighted many of these features.  

You should know that LM3S devices are NRND (not recommended for new design).  My suggestion would be to migrate to an IDE tool chain that supports the M4 core.  TivaWare our software code libraries and examples ships with project support for Code Composer Studio, Keil, IAR, Mentor Sourcery CodeBench and command line GCC make files. TivaWare does not support LM3S devices.  StellarisWare is the LM3S equal of TivaWare.  StellarisWare is not being actively developed and maintained.  

In my opinion your best option is to use the TM4C device.  Availability and price for the TM4C should be better.

Dexter

Hello Dexter

Thank you for your suggestion, now we start to develop our security board with TM4C1237H6PZ.

We use CrossStudio and J-Link to debug our application. Then we switch build configuration from "THUMB Debug" to "THUMB Release", it always jump to HardFault_Handler when we try to run it.

Do you have any suggestion? Would we need to use another flasher software?

Best regards
Phuchit K.

You need to debug the code and find out what line(s) of code are causing the hard fault.  

When moving from Thumb Debug to Thumb Release the compiler/linker will often change the optimization settings. This can cause several different types of fault.  The most common cause is the that it takes three clock cycles after a SysCtlPeripheralEnable for the enable to take effect.  In debug mode there is a long enough delay between enable and use of the peripheral.  In release mode with optimizations on the compiler may inline the code and lose the needed delay cycles.

Regardless the issue is almost certainly in the subtle difference in the assembly/machine code generated in the different modes of the compiler.

Dexter

Hello Dexter

Thank you so much for your useful information. We already solved many modules, now it works.

Best regards
Phuchit K.