• Locked Locked
  • Replies 2 replies
  • Subscribers 80 subscribers
  • Views 775 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

application gets stuck

Sanjay M
Prodigy 160 points

Other Parts Discussed in Thread: MSP430F5419A

Hello,

Currently i am working on MSP430F5419A with 3 spi,2 uart ,and 1 i2c.

MCLK=SMCLK=4MHZ ( xternal crystal =4 MHZ)

UART BR=9600     All SPI CLOCK= 2 MHZ    I2c Clock=300KHZ 

1.MCU gets stopping the execution non-periodically  like (after 6 hours ,sometimes 14 hours or it woking upto 1 day also.)

2.Application is not working continuously. 

3.Is that stack overflow issue? I configured stack size=512.

4.I used RTC timer interrupt for every 1 sec with that LED used to glow on/off at every 1 second. (for checking whether the application stuck or not ). Sometimes when code running ,my output data is  not updating but LED is doing ON/OFF ,which means my CPU is alive but why the interfaced output data is not updating? Where i did wrong please give the reply.

5.While debugging i observed that when output data is not updating ,then i  suspending the application i got "No source available on "0x03d0" .

          Is this issue that  code is not working and gets suck their only? Please tell me how to resolve this iSSUE..

 I am in last stage of project but this stuck issue is getting more problem.Please give the valuable inputs to resolve this issue.

Regards,

Sanjay M.

  • Guru 324220 points
    There is a bug somewhere in your application.

    Without the source code, it's impossible to say more.
  • TI__Guru**** 222707 points
    Hello Sanjay,

    As Clemens pointed out, it is very difficult to tell what the issue is from the information provided. Your application appears to be quite developed, which makes it hard for us to dissect and means there was a point at which your code was operating properly before the addition of some functionality caused it to go into the weeds. You need to backtrack and figure out what addition is causing the issue. With the assumed large number of USCI interrupt flags being serviced it is possible that some ISRs are overlapping and the delay results in communication failure, or the way you handle LPM entry and exit is being adversely affected. You can try driving the MCLK frequency at 25 MHz to decrease instruction time while keeping SMCLK at 4 MHz as to not affect the USCI clocks. You may also want to temporarily only use LPM0 to decipher if the device is having difficulty waking up from LPM2/3. The system must be further debugged before we can offer valuable help.

    Regards,
    Ryan

**Attention** This is a public forum