Stellaris® ARM® LM3S Microcontrollers Forum - Recent Threads

LCD 3'2" TFT SSD1289 BOOSTERPACK port to tiva

Daniel Rebollo — Sun, 19 May 2013 01:38:59 GMT

Hello! i built LCD BOOSTERPACK http://danirebollo.blogspot.com/2013/05/ssd1289-boosterpack-32-320x240-tft.html for stellaris and i like to know if fits in tiva launchpad. Looking at schemas i think there isnt any problem but today i havent tiva and i dont know if there is problem in code composer studio or some

thanx

configuring boot loader for ethernet update fpr lm3s9b92

Janani Neelakantan — Tue, 20 Sep 2011 13:07:06 GMT

I want to use my bootloader for the ethernet flash update.

I configured the bl_config.h for the ethernet update and flashed the boot_eth into my board.

Then using the ethernet interface tried my application but the flash is not able to connect to the board.

Can anyone tell me what would be the problem???

Re:Bootloader for LM4F232 kit

Santosh PG — Thu, 09 May 2013 18:01:42 GMT

Hi,

I am using LM4F232 evk and LM Flash programmer.

I tried the steps given in the below links to set up the serial bootloader to work but was not successful, getting error when tried to load code via serial

port 'Failed to establish communication with the board ', so please help to get the appropriate steps

http://e2e.ti.com/support/microcontrollers/stellaris_arm/f/471/t/242473.aspx

http://e2e.ti.com/support/microcontrollers/stellaris_arm/f/471/t/85249.aspx

Best Regards,

Santosh.

Problem loading my program on stellaris launchpad flash

Sergio Cruz Perez — Fri, 17 May 2013 23:34:26 GMT

Hi,

I'm evaluating stellaris microcontrollers using a stellaris launchpad. I've debugged the examples for my board included in StellarisWare with out any problem. I've created a new project, copied the code of the examples (including the startup_css.c file), genearated the .bin file and loaded on flash using LM Flash Programmer with success.

The problem is when I want to load a program I built. I can debug the project and works OK. I can generate the bin file but when I load it on flash, the microcontroller seems to do nothing. I've copied all the properties of the StellarisWare examples to my project, but I think I'm missing something else.

Any idea?

Thanks

How to use RTC based on I2C with LM3S6911

print — Wed, 02 Jul 2008 06:10:01 GMT

Hi
I am using RTC IC FM31/256 which is connected at I2C0 on portB of my LM3s6911 board. I have enabled the RTC oscillator , then make Read reg 1 to enable read and then make it 0 to transfer RTC. Then I am trying to read the RTC reg 7bit for sec,min,hour,day,date,month and year.
My RTC slave address is 0xD6.
But I am not able to read the RTC registers. Will you plz help me out with my coding...

Code:



 #include "hw_sysctl.h"
#include "hw_ints.h"
#include "hw_memmap.h"
#include "hw_types.h"
#include "hw_gpio.h"

#include "i2c.h"
#include "interrupt.h"
#include "sysctl.h"
#include "systick.h"
#include "flash.h"
#include "gpio.h"
#include "LCD_LM.h"
#include "timer.h"

static volatile unsigned long g_ulState = STATE_IDLE;
static unsigned char *g_pucData = 0;
static unsigned long g_ulCount = 0;

void I2CIntHandler(void)
{

// Determine what to do based on the current state.
   switch(g_ulState)
   {
   
   // The idle state.
      case STATE_IDLE:
      {
      // Clear the I2C interrupt.
         I2CMasterIntClear(I2C0_MASTER_BASE);
         
      // There is nothing to be done.
         break;
      }
   // The state for the middle of a burst write.
      case STATE_SET_NEXT:
      { 
      // Write the next byte to the data register.
         I2CMasterDataPut(I2C0_MASTER_BASE, *g_pucData++);
         g_ulCount--;

      // Continue the burst write.
         I2CMasterControl(I2C0_MASTER_BASE, 
                                   I2C_MASTER_CMD_BURST_SEND_CONT);
                    
      // If there is one byte left, set the next state to the final write state.
         if(g_ulCount == 1)
         {
             g_ulState = STATE_SET_FINAL;
         }
           
      // This state is done.
         break;
      }
   // The state for the final write of a burst sequence.
      case STATE_SET_FINAL:
      {
      // Write the final byte to the data register.
         I2CMasterDataPut(I2C0_MASTER_BASE, *g_pucData++);
         g_ulCount--;

      // Finish the burst write.
         I2CMasterControl(I2C0_MASTER_BASE,
                                 I2C_MASTER_CMD_BURST_SEND_FINISH);
                    
      // The next state is to wait for the burst write to complete.
         g_ulState = STATE_SEND_ACK;

      // This state is done.
         break;
      }
           
    // Send a read request, looking for the ACK to indicate that the write
    // is done.
       case STATE_SEND_ACK:
       {
       // Put the I2C master into receive mode.
          I2CMasterSlaveAddrSet(I2C0_MASTER_BASE, 0x6B, true);
                
       // Perform a single byte read.
          I2CMasterControl(I2C0_MASTER_BASE, I2C_MASTER_CMD_SINGLE_RECEIVE);

       // The next state is the wait for the ack.
          g_ulState = STATE_WAIT_ACK;

       // This state is done.
          break;
       }
            
    // Wait for an ACK on the read after a write.
       case STATE_WAIT_ACK:
       {
       // See if there was an error on the previously issued read.
          if(I2CMasterErr(I2C0_MASTER_BASE) == I2C_MASTER_ERR_NONE)
          {
          // Read the byte received.
             I2CMasterDataGet(I2C0_MASTER_BASE);

          // There was no error, so the state machine is now idle.
             g_ulState = STATE_IDLE;

          // This state is done.
             break;
          }
        }
    
   // The state for a single byte read.
      case STATE_GET_ONE:
      {
      // Put the I2C master into receive mode.
         I2CMasterSlaveAddrSet(I2C0_MASTER_BASE, 0x6B, true);
            
      // Perform a single byte read.
         I2CMasterControl(I2C0_MASTER_BASE, I2C_MASTER_CMD_SINGLE_RECEIVE);
     
        delay();
      // The next state is the wait for final read state.
         g_ulState = STATE_GET_WAIT;

      // This state is done.
         break;
      }

   // The state for the start of a burst read.
      case STATE_GET_FIRST:
      {
      // Put the I2C master into receive mode.
         I2CMasterSlaveAddrSet(I2C0_MASTER_BASE, 0x6B, true);
           
      // Start the burst receive.
         I2CMasterControl(I2C0_MASTER_BASE,
                             I2C_MASTER_CMD_BURST_RECEIVE_START);
         delay();
      // The next state is the middle of the burst read.
         g_ulState = STATE_GET_NEXT;

      // This state is done.
         break;
      }

   // The state for the middle of a burst read.
      case STATE_GET_NEXT:
      {                  
      // Read the received character.
         *g_pucData++ = I2CMasterDataGet(I2C0_MASTER_BASE);
          g_ulCount--;

      // Continue the burst read.
         I2CMasterControl(I2C0_MASTER_BASE,
                             I2C_MASTER_CMD_BURST_RECEIVE_CONT);
         delay();
      // If there are two characters left to be read, make the next
      // state be the end of burst read state.
         if(g_ulCount == 1)
         {
            g_ulState = STATE_GET_FINAL;
         }

      // This state is done.
         break;
      }

   // The state for the end of a burst read.
      case STATE_GET_FINAL:
      {
      // Read the received character.
         *g_pucData++ = I2CMasterDataGet(I2C0_MASTER_BASE);
          g_ulCount--;

      // Finish the burst read.
         I2CMasterControl(I2C0_MASTER_BASE,
                             I2C_MASTER_CMD_BURST_RECEIVE_FINISH);
         delay();
      // The next state is the wait for final read state.
         g_ulState = STATE_GET_WAIT;

      // This state is done.
         break;
      }

   // This state is for the final read of a single or burst read.
      case STATE_GET_WAIT:
      {
      // Read the received character.
         *g_pucData++ = I2CMasterDataGet(I2C0_MASTER_BASE);
          g_ulCount--;

      // The state machine is now idle.
         g_ulState = STATE_IDLE;

      // This state is done.
         break;
      }
   } 
}

// Write to RTC
void
Write(unsigned char *pucData, unsigned long ulOffset,
           unsigned long ulCount)
{
// Save the data buffer to be written.
   g_pucData = pucData;
   g_ulCount = ulCount;
   
// Set the next state of the interrupt state machine based on the number of
// bytes to write.
   if(ulCount != 1)
   {
      g_ulState = STATE_SET_NEXT;
   }
   else
   {
      g_ulState = STATE_SET_FINAL;
   }
  
// Set the slave address and setup for a transmit operation.
   I2CMasterSlaveAddrSet(I2C0_MASTER_BASE, 0x6B | (ulOffset >> 8), false);
   
// Place the address to be written in the data register.
   I2CMasterDataPut(I2C0_MASTER_BASE, ulOffset);

// Start the burst cycle, writing the address as the first byte.
   I2CMasterControl(I2C0_MASTER_BASE, I2C_MASTER_CMD_BURST_SEND_START);
   
// Wait until the I2C interrupt state machine is idle.
   while(g_ulState != STATE_IDLE)
   {
   }
   
}

// Read from RTC
void
Read(unsigned char *pucData, unsigned long ulOffset,
          unsigned long ulCount)
{
// Save the data buffer to be read.
   g_pucData = pucData;
   g_ulCount = ulCount;
   
// Set the next state of the interrupt state machine based on the number of
// bytes to read.
   if(ulCount == 1)
   {
      g_ulState = STATE_GET_ONE;
   }
   else
   {
      g_ulState = STATE_GET_FIRST;
   }

// Start with a dummy write to get the address set in the EEPROM.
   I2CMasterSlaveAddrSet(I2C0_MASTER_BASE, 0x6B | (ulOffset >> 8), false);
   
// Place the address to be written in the data register.
   I2CMasterDataPut(I2C0_MASTER_BASE, ulOffset);
  
// Perform a single send, writing the address as the only byte.
   I2CMasterControl(I2C0_MASTER_BASE, I2C_MASTER_CMD_BURST_RECEIVE_START);
   
// Wait until the I2C interrupt state machine is idle.
   while(g_ulState != STATE_IDLE)
   {
   }
}

int main(void)            
{

    unsigned char pucData[16];
    int i=0;

// Set the clocking to run directly from the crystal.
    SysCtlClockSet(SYSCTL_SYSDIV_1 | SYSCTL_USE_OSC | SYSCTL_OSC_MAIN |
                   SYSCTL_XTAL_6MHZ);

// Enable the peripherals used by this example.
    SysCtlPeripheralEnable(SYSCTL_PERIPH_I2C0);
    SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOB);
    
// Enable Port B of GPIO
//  SDA 0        Bit 3   Output
//  SCL 0        Bit 2   Output
    GPIOPinTypeI2C(GPIO_PORTB_BASE, GPIO_PIN_2 | GPIO_PIN_3);
    
// Initializes the I2C Master block with clock
       I2CMasterInitExpClk( I2C0_MASTER_BASE, SysCtlClockGet(), false); 
       
// Enable the I2C interrupt.
    IntEnable(INT_I2C0);         

// Registers a function to be called when an interrupt occurs in I2C
    I2CIntRegister(I2C0_MASTER_BASE, &I2CIntHandler);
           
// Enable the I2C Master Interrupt
       I2CMasterIntEnable(I2C0_MASTER_BASE);    
     
    LCD_Init();

   pucData[0] = 0x00;
   Write(pucData, 1, 1);    //osc en
   
   pucData[0]=0x01;
   Write(pucData, 0, 1); //RTC READ=1
   
   pucData[0]=0x00;
   Write(pucData, 0, 1);//RTC READ=0
    
   Read(pucData[2],0x02,7);// READ TIME
   
   for(i=2;i15;i++)
   { 
       LCD_DIS(pucData[i], 1, i);
   }   
}

Post edited by: print, at: 2008/07/02 01:11

Stellaris Launchpad LM4F120XL vs Kentec -L35 display example

Ken Grant — Sun, 12 May 2013 18:58:09 GMT

I using the workbook examples and labs from the website with the specified hardware.

Stellaris Lauchpad LM4F120 & KentecEB-LM4F120-L35

CCS Version: 5.2.1.00018, Stellarisware from SW-LM3S-9453.exe

Things have gone well upto the Kentec example "grlib_demo" project and

I'm stopped over the following error which I have no clue as to what to do to resolve; the console message as follows;

CORTEX_M4_0: GEL: Encountered a problem loading file: C:\Users\KenG\workspace_v5_2\grlib_demo\Debug\grlib_demo.out Could not open file.

I got smart here and created an empty file in the location requested on the build the file message went away but;

Problems window has the following;

Description Resource Path Location Type gmake: *** No rule to make target `C:/StellarisWare/boards/MyLaunchPadBoard/utils/ustdlib.c', needed by `utils/ustdlib.obj'. grlib_demo Unknown C/C++ Problem

I fussed around reloading Stellarisware and also downloading the example from Kentec, with out any results.

Any clues would be appreciated.

Ken

Driver Library Linking Error

Ankur Bhanu — Sat, 18 May 2013 13:01:56 GMT

Can any help me to solve this linker Problem. I am getting following linker Error.

"C:\\ti\\ccsv5\\utils\\bin\\gmake" -k all
'Building file: ../Walkin.c'
'Invoking: ARM Compiler'
"C:/ti/ccsv5/tools/compiler/arm_5.0.1/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 --abi=eabi -me -g --include_path="C:/ti/ccsv5/tools/compiler/arm_5.0.1/include" --include_path="C:/StellarisWare" --include_path="C:/StellarisWare/boards/ek-lm4f232" --diag_warning=225 --display_error_number --preproc_with_compile --preproc_dependency="Walkin.pp" "../Walkin.c"
"../Walkin.c", line 24: warning #225-D: function declared implicitly
"../Walkin.c", line 33: warning #225-D: function declared implicitly
'Finished building: ../Walkin.c'
' '
'Building file: ../startup_ccs.c'
'Invoking: ARM Compiler'
"C:/ti/ccsv5/tools/compiler/arm_5.0.1/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 --abi=eabi -me -g --include_path="C:/ti/ccsv5/tools/compiler/arm_5.0.1/include" --include_path="C:/StellarisWare" --include_path="C:/StellarisWare/boards/ek-lm4f232" --diag_warning=225 --display_error_number --preproc_with_compile --preproc_dependency="startup_ccs.pp" "../startup_ccs.c"
'Finished building: ../startup_ccs.c'
' '
'Building target: WalkInBBR.out'
'Invoking: ARM Linker'
"C:/ti/ccsv5/tools/compiler/arm_5.0.1/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 --abi=eabi -me -g --diag_warning=225 --display_error_number -z --stack_size=2048 -m"WalkInBBR.map" --heap_size=0 -i"C:/ti/ccsv5/tools/compiler/arm_5.0.1/lib" -i"C:/ti/ccsv5/tools/compiler/arm_5.0.1/include" --reread_libs --warn_sections --display_error_number --rom_model -o "WalkInBBR.out" "./startup_ccs.obj" "./Walkin.obj" -l"libc.a" -l"C:\StellarisWare/driverlib/ccs-cm4f/Debug/driverlib-cm4f.lib" "../walkin_CCS.cmd"
<Linking>

undefined first referenced
symbol in file
--------- ----------------
ROM_FPULazyStackingEnable ./Walkin.obj
ROM_SysCtlClockSet ./Walkin.obj

error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "WalkInBBR.out" not built

>> Compilation failure
gmake: *** [WalkInBBR.out] Error 1
gmake: Target `all' not remade because of errors.

Trying to compile eflash

Jules Petit — Sat, 18 May 2013 09:24:35 GMT

Hi,

iam trying to generate an eflash.exe using cygwin. I installed the gcc compiler and the make package but get the output below. I have got the files eflash.c, eflash.h, boot_server.c, boot_server.h and the Makefile. Later I want to update my Stellaris Eval Board lm3s8962, without using the lm flash programmer.

Maybe I do s.th. materially wrong. Has someone suggestions what might be missing or wrong?

Jules

$ make eflash
cc Makefile.c -o Makefile
Makefile.c:28: Error: Error while parsing »:«-Symbol
cc eflash.c -o eflash
/tmp/ccA6bGzE.o:eflash.c:(.text+0x4bb): undefined reference to `_AbortBOOTPUpdat e'
/tmp/ccA6bGzE.o:eflash.c:(.text+0x57a): undefined reference to `__imp__WSAStartu p@8'
/tmp/ccA6bGzE.o:eflash.c:(.text+0x5b0): undefined reference to `__imp__WSACleanu p@0'
/tmp/ccA6bGzE.o:eflash.c:(.text+0x5cd): undefined reference to `__imp__gethostby name@4'
/tmp/ccA6bGzE.o:eflash.c:(.text+0x636): undefined reference to `_StartBOOTPUpdat e'
/tmp/ccA6bGzE.o:eflash.c:(.text+0x650): undefined reference to `__imp__WSACleanu p@0'
/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: /tmp/ccA6bG zE.o: bad reloc address 0x4 in section `.data'
/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: final link failed: Invalid operation
collect2: ld gave back 1 as exit status
<builtin>: recipe for target `eflash' failed
make: *** [eflash] Error 1

Re:Error connecting to the target: (Error -5005 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver. (Emulation package 0.0.0.0)

Santosh PG — Fri, 17 May 2013 18:16:06 GMT

Hi Everyone,

Using LM4F232 Kit, CCSV5., XDS100V2 and connected the OTG connector from PC to kit and jumper settings for powering up accordingly.

Connected TMS, TDI,TCK,TDO,VCC,GND between XDS and kit and when trying to program from CCS getting the below error,

Error connecting to the target: (Error -5005 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver. (Emulation package 0.0.0.0)

I am able to load code through ICDI on the board so what may be the problem, does all the 14 pin connections required?? or anything else has to be configured.

Best Regards,

Santosh.

Stellaris EKS-LM4F232 Evaluation Kit with CCS5 lost ability to connect debugger through USB ICDI

Jon Yutkowitz — Wed, 08 May 2013 17:45:15 GMT

Hello,

I have been using the stellaris EKS-LM4F232 for a few months now with CCSv5, and have had no problems and began developing an application that uses the USB as a generic bulk device, and communicates on the 8 UARTs.

Recently our company purchased a second eval kit and connected the UARTs to an external device to continue with my development which has also been productive for a few weeks with no problems. Last week I began to have connection issues in code composer and was unable to connect the debugger and the error was "Frequency out of range". In searching the TI forums I was able to see that this was an indication that there may be a problem with the ICDI drivers. In device manager these drivers no longer displayed at all. The generic bulk device driver was fine, but the FTDI and ICDI did not appear at all. Also, there was an unknown device appearing in the Universal Serial Bus controllers list.

I spent a great deal of time trying to update the CCS software as well as the stellaris downloads available on the website. The current version of software that I have been using comes from EKS-LM4F232-DVD-733, which includes CCS 5.2.1.00018. I have also attempted using a download from your website of CCS5.3.0.00090 with no improvement. My system is a Windows7 64 bit. After many installs and uninstalls I was able to get the drivers to re-appear by uninstalling everything from my system, all drivers, CCS, etc... I also had to uninstall from device manager the unknown device for each board. After doing this, rebooting the PC and plugging in the EVAL board I was able to get the drivers to re-appear in device manager. I then proceeded to re-install CCSv5 but after doing that when I attempt to connect to the debugger for any of the sample programs CCS hangs and must be aborted from task manager.

I have also had no success connecting with LM Flash programmer either. When that loads and I attempt to use any of the flash utilities, most of the text boxes show non-standard ASCII characters and none of the buttons work, the error being Unable to find a target.

On both of the boards the last program to successfully be programmed to flash remains, and the USB generic bulk capability functions correctly, as does the communication on the UARTs. On one of the boards I also attempted to use the "Unlock" utility which did nothing, and the ICDI firmware update briefly connected but then failed.

I do not know if the boards are damaged or if my computer has become corrupted. Any help would be greatly appreciated.

Also, a co-worker has a third eval board that has never loaded anything other than the default qs-logger program that comes with the eval board.

LM3S9B96 How many USB endpoints?

dave tasker — Sun, 27 Feb 2011 22:38:30 GMT

Hi all

I'm creating a Composite USB Device using a LM3S9B96. I can create two virtual COM ports, or I can create a single virtual COM port and a single Bulk Device.

What I want to create is at least two Virtual COM ports and a single Bulk Device. However, when I configure these three devices, the LM3S9B96 debugger hits the FaultISR interrupt handler during the install of the first USB device in Device Manager. I'm running Windows XP SP3

Am i exceeding the available number of USB endpoints?

Where is this documented?

Thanks

Dave

Where is the Stellaris PinMux Utility?

rgl — Fri, 17 May 2013 08:46:24 GMT

Hi @all,

i'm trying to find the Stellaris PinMux Utility for Tiva C processors. At http://www.ti.com/tool/lm4f_pinmux i can download the documentation and watch a video of someone using the tool but i don't find a download link for the tool itself?!

Could also be me being to stupid to use a browser...anyhow please tell me where to get the tool.

Best regards,

Ralf

HID + HID Interface on DK-LM3S9B96 Stellaris

Vinicius Hubner — Wed, 15 May 2013 18:48:51 GMT

Hello,

I'm trying to use the LM3S9B96 kit as two interfaces at the same time, but I can only use as 1 HID interface.

Are there any program to create descriptors like the msp430?

I need to make a mouse and keyboard at the same time. HID+HID Interface (1 mouse and 1 Keyboard).

Thx

How to set a charactermap?

Bart Remans — Thu, 16 May 2013 19:57:08 GMT

Hi,

I'd like to draw text on my oled i²c display but don't now how to implement the charactermap? I've read about using std::map to map values to keys but when I use this in the CCS it gives me an error syntax.

for example:

include <map>
include <iostream>

map<string, char*> charMap;
charMap['!']= {'0x00', '0x00', '0x5F', '0x00', '0x00'};

but this doesn't seem to work.

Any ideas how to approach this would be very appreciated!

LM3S9B96 Rev C5 USB Library

Jay Boyce — Mon, 13 May 2013 19:28:49 GMT

Hello,

I have been having trouble with migrating the USB Serial Device example from the development board to my custom board.

I can run the USB Serial Device example from the development board with no problems, it enumerates as a virtual serial comm port. I have doen this using the internal 16 MHz clock and the external crystal.

On my custom board it recognizes that a device is connected but does not finish enumerating PID 0000 VID 0000

All connections to USB have been verified from the cable to the microcontroller.

At steady state the VBus is 5.06V at the microcontroller.

1. Do I have to recreate the USBlib library using the TARGET_IS_TEMPEST_RC5 under the preprocessor options?

2. Should I also do this for the driverlib and graphicslib?

3. Can the USB run from the internal 16 MHz or is it too unstable (I know that it can change by 3% due to temperature and the USB spec calls out 1%)

Any other suggestion on what to look for?

Thanks,

Jay

DFU external flash write

Peter Šamperl — Wed, 20 Jul 2011 12:20:41 GMT

I have modified bootloader so i can program my external SPI flash over sflash.
If I pass address 0x8000000 my bootloader knows it is for external flash and it uses different page size and write functions.

Now I would like to implement this over DFU.

What would be the best approach to write/read/erase data on external SPI device using dfu?

Regards

LM3S9D96 Decision Time - continue or go to STM32F4

Vito Casa — Tue, 14 May 2013 22:40:39 GMT

Dear Texas Instruments,

I'm about a third of the way through developing a product on the LM3S9D96 and need to make a decision at this stage between:

1) Get assurance from Texas Instruments that the LM3S9D96 will be "available" for the next 10 years (yes, long product life)

2) Do a life time buy of LM3S9D96 devices (going to be hard to convince management on this one)

3) Use an upcoming Tiva chip with integrated PHY (but this would need to be out within 4 months)

4) Make the switch to STM32F4 devices (relearning, but then maybe best in the long run)

My preferred option is Number 1, so I'm seeking assurance from Texas Instruments that the LM3S9D96 will be "available" for the next 10 years. I know that Texas Instruments have stated that the LM3S devices will continue to be produced as long as there is demand, but that is a useless statement. The price can increase dramatically or the lead time become prohibitive. Not only will this kill off demand, but make it makes the micro effectively not available even when it is "available".

So, here are my direct questions to Texas Instruments regarding the "availability" of LM3S9D96 devices:

1) Will the LM3S9D96 continue to be sold for the next 10 years?

2) Will the price remain as it is today (or up to a maximum of twice as expensive as today)?

3) Will the lead time remain below 6 weeks for the duration of the 10 year period (barring any unforeseen circumstance like a tsunami hitting the factory)?

All three would have to be a YES for me to be able to continue with the LM3S9D96. If I haven't heard from Texas Instruments in a week I'll assume that at least one of the questions would have to be answered in the negative and will then purchase a STM32 development board and make the transition. The STM32F4 Discovery looks good at first glance, even if I do need to add an Ethernet PHY chip.

I'm asking this question in a public forum since many others are facing the same dilemma. It will also be interestign to see the level of interest in this question.

Regards,

Vito

What about the smaller LM3S processors?

Shawn Aikey — Thu, 16 May 2013 15:09:21 GMT

I just learned of the new NRND status... and the god awful supply issues with the LM3S parts. The majority of the comments I have seen are focused on the larger devices with on chip ethernet. But what about smaller devices like the LM3S628???

I just finished a design cycle, and have my device approved with my customer, about to go into full production and then you obsolete your whole product line!!!! Are you guys on crack? Seriously, are you? Do you have any idea how time consuming and expensive it is to get designed into a medical device? Now I have to re-design my product, and go back to my customer to tell them that TI screwed us both over and we have to re-design a part that isn't even in production yet. Like I don't have enough real problems without you creating new ones for no apparent reason other than maybe NIH syndrome.

Honestly, what do you recommend that I do here? There is no stock on the alleged TIVA parts, at least not parts that I would be interested it (I didn't look at larger more complex parts). I could switch to MSP430 I guess, but those data sheets are just physically painful to decipher (one datasheet to cover 20 random options in a given "family" of MSP430, trying to figure out which sections apply to your use case). I actually pushed for the CortexM3 so I wouldn't have to deal with MSP430 on this project. So what is the "official" recommendation? Or was this so poorly planned that you don't even have a reasonable recommendation to give?

-Shawn

LM3S8962 Build Fail

Matthew Kenneday — Thu, 19 Apr 2012 08:15:42 GMT

Gday all,

Just bought a Luminary Micro LM3S8962 evaluation board and was hoping to make some programs in Labview and download/run them, as I have read you can do.

Ive installed Labview 2011 with the 'Embedded Module for ARM Microcontrollers., with Keil uVision 4.

However, whenever I attempt to build a project, whether its one I quickly made, or an example, during the build phase it comes up with the following error:

[9:37:41 PM] Status: Error

Build target 'LabVIEW'
compiling RTX_Config.c...
C:\Keil\ARM\RV31\INC\RTX_lib.c(183): error: #29: expected an expression
compiling Untitled_ARM.c...
Target not created

Status: Build failed.

I am somewhat new to this, and I have very little idea what the above error means, nor how I can fix it.

Can anyone help!

I should add that the version is Keil uVision4 4.50a

how to built asm project on CCS

qiao cui — Thu, 16 May 2013 15:20:04 GMT

hello, I'm new to ARM and CCS.

I'm using ARM cortex M4.

I need to demo a project on class tomorrow about how to use assembly language on ARM.

I just need to use a simple assembly language example, just like blinking the LED, but I don't know how to built a assembly language project on CCS, especially how to write ".cmd"...

SafeRTOS StateViewer

Dmitriy Garyachiy — Thu, 24 May 2012 22:22:11 GMT

Hello,

I use:

Stellaris® LM3S9B96

CCS 5.1.0

Eclipse Version: Indigo Release Build id: 20110615-0604

SafeRTOS in ROM

StateViewer Version: 2.0.2.201205030952

The Queue and Task tables in StateViewer are both empty.

Help.

LM3S5B91C5 USB issue

Piyush Ramuka — Mon, 13 May 2013 08:46:25 GMT

Hi All,

Background: We are working with LM3S5B91-C5 processor to connect its USB to SMSC's USB2512 hub. The hub will be used to connect keyboard (Low Speed Device) and Barcode Scanner (High/Full Speed Device).

Processor Details: LM3S5B91-IQC80C5SD $A-27P307H. Clock Speed: 30MHz.

Issue: Barcode Scanner works but the keyboard is not working all the time. USB hub is getting detected by the processor - 100%. But the keyboard is failing. Once keyboard fails, barcode scanner also stops working.

We had issues before with LM3s5B91-C3 chip and ended up using LM3S5B91-C5 chip due to USB Errata. I have no idea where to look for the solution because the issue is very random.

Could anyone help us in resolving this critical issue? If there are more details required, please feel free to ask. Looking forward to get some response. Any help in this regards will be appreciated.

Regards,
Piyush

Proper c code for SSI communications between master and slave, master is LM3S2965 and slave is bq76PL536EVM-3?

Mike Hoffnagle — Mon, 06 May 2013 17:37:32 GMT

Proper c code for SSI communications between master and slave, master is LM3S2965 and slave is bq76PL536EVM-3?

I have done the internal communication code example for the LM3S2965 CAN EVAL BOARD but now I want to communicate with the bq76PL536EVM-3 board. I just want cell voltages. I am reading the documents for both boards but do not fully understand how to write the code to have the master transmit to the slave that I want data from it and then have the slave send that data back and then have the master (LM3S2965) be able to receive and translate the information into the actual voltages to read on the OLED. I know how to interface with the OLED. It is the SSI communication c code between boards that I am having troubles with.

I2C Initialization on LM4F232 eval board

Praveen Kumar102474 — Wed, 15 May 2013 17:30:06 GMT

Hi,

Sorry for re-posting the same query again, I need urgent support on I2C initialization. Please let me know if further information is required.

I am working on evaluation board LM4F232H5QD where I2C0 is connected to TMP75 temperature sensor. I am using the following code:

1) To initialize I2C0

void InitI2C0(void)
{
    SysCtlPeripheralEnable(SYSCTL_PERIPH_I2C0);
    SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOB);

    GPIOPinConfigure(GPIO_PB2_I2C0SCL);
    GPIOPinConfigure(GPIO_PB3_I2C0SDA);

    GPIOPinTypeI2C(GPIO_PORTB_BASE, GPIO_PIN_2 | GPIO_PIN_3);

    I2CMasterInitExpClk(I2C0_MASTER_BASE, SysCtlClockGet(), false);     // SysCtlClockSet(SYSCTL_SYSDIV_1 | SYSCTL_USE_OSC | SYSCTL_OSC_MAIN |

// SYSCTL_XTAL_16MHZ);
}

2) Code to send data:

void I2C_burstsend(unsigned char ucSlaveAddr, unsigned char sendData[], unsigned char size)
{
    unsigned int i;

    // Set the slave address, and set the Master to Transmit mode
    I2CMasterSlaveAddrSet(I2C0_MASTER_BASE, ucSlaveAddr, false);
    // Place the character to be sent in the data register
    I2CMasterDataPut(I2C0_MASTER_BASE, sendData[0]);

    // Initiate send of character from Master to Slave
    if (size > 0)
       I2CMasterControl(I2C0_MASTER_BASE, I2C_MASTER_CMD_BURST_SEND_START);
    else
       I2CMasterControl(I2C0_MASTER_BASE, I2C_MASTER_CMD_SINGLE_SEND);
    // Delay until transmission completes
    while(I2CMasterBusy(I2C0_MASTER_BASE)){}

    if (size == 0)
       return;

    // send data array
    for(i=1; i < (size-1); i++)
    {
        I2CMasterDataPut(I2C0_MASTER_BASE, sendData[i]);
        I2CMasterControl(I2C0_MASTER_BASE, I2C_MASTER_CMD_BURST_SEND_CONT);
        while(I2CMasterBusy(I2C0_MASTER_BASE)){}
    }

    // send the last byte
    I2CMasterDataPut(I2C0_MASTER_BASE, sendData[i]);
    I2CMasterControl(I2C0_MASTER_BASE, I2C_MASTER_CMD_BURST_SEND_FINISH);
    while(I2CMasterBusy(I2C0_MASTER_BASE)){}
}

It seems the code is not working, when I put a breakpoint at "if (size > 0)" and check the value of Register in CCS5 I2C0->I2C_MDR->I2C_MDR_DATA, the value is 0x00000000; the value of sendData[0] = 0x90.

When I proceed to next step i.e. I2CMasterControl(I2C0_MASTER_BASE, I2C_MASTER_CMD_BURST_SEND_START); and checked the value of I2C_MCS_ERROR, its value is 1.

FYI, TMP75 is connected with 4.7kohm pull-up resistor.

Looking forward to your support.

Thanks and regards,

Praveen

// -------------------------------------------

I also tried the following code to initialize the I2C0, but behaviour is same:

void InitI2C0(void)
{
   ROM_SysCtlPeripheralEnable(SYSCTL_PERIPH_I2C0);

   ROM_SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOB);

   I2CMasterIntEnable(I2C0_MASTER_BASE);

   GPIOPinTypeI2CSCL(GPIO_PORTB_BASE, GPIO_PIN_2);

   ROM_GPIOPinTypeI2C(GPIO_PORTB_BASE, GPIO_PIN_3);

   ROM_GPIOPinConfigure(GPIO_PB2_I2C0SCL);

   ROM_GPIOPinConfigure(GPIO_PB3_I2C0SDA);

   GPIOPadConfigSet(GPIO_PORTB_BASE, GPIO_PIN_3, GPIO_STRENGTH_2MA, GPIO_PIN_TYPE_OD_WPU);

   ROM_I2CMasterInitExpClk(I2C0_MASTER_BASE, ROM_SysCtlClockGet(), false);

}