2340 views|3 replies

6366

Posts

4936

Resources
The OP
 

MSP430 MCU Development Record (7) [Copy link]




This content is originally created by EEWORLD forum user tiankai001. If you need to reprint or use it for commercial purposes, you must obtain the author's consent and indicate the source. Msp430 MCU Development Record (7) Phenomenon: When debugging a program, I found that the program always crashed. I used online simulation to find the problem. Test: I found that in the simulation environment, the program always points to a fixed address after crashing. This address is the timer interrupt vector address (this can only be seen in the disassembly. For C language programs, you can only see that the program crashed, but you can't see the specific situation). After checking the program again, I found that when the program was initialized and configured, the timer was initialized and configured, and the timer interrupt was turned on because it was required by the subsequent functions. However, because the timer function had not been debugged yet, the timer interrupt service routine was not added. Verification: After adding the timer interrupt service routine, the program executes normally and will no longer run away. Remarks: In the MSP430 microcontroller, if a certain interrupt is enabled, the corresponding interrupt service program must be written. If the interrupt function is not defined for the time being, then create an empty interrupt service function.
This post is from Microcontroller MCU

Latest reply

Yes, what you share is indeed classic.  Details Published on 2018-12-18 11:03
 

2618

Posts

0

Resources
2
 
It would be better if the OP could provide some pictures to explain.
This post is from Microcontroller MCU

Comments

Because these debugging are all done on the company's products. Sharing experience is fine, but if you add pictures, some of the company's product codes will be shown in the pictures, which is not good.  Details Published on 2018-12-18 10:47
 
 

6366

Posts

4936

Resources
3
 
alan000345 posted on 2018-12-18 10:36 It would be better if the OP could explain with some pictures.
Because these debugging are all done on the company's products. Sharing experience is fine, but if you add pictures, some of the company's product codes will be shown in the pictures, which is not good
This post is from Microcontroller MCU

Comments

Yes, what you shared are indeed classics.  Details Published on 2018-12-18 11:03
 
 
 

2618

Posts

0

Resources
4
 
tiankai001 posted on 2018-12-18 10:47 Because these debugging are all done on the company's products. It's okay to share your experience. If you add pictures, some of the company's product codes will be shown in the pictures, ...
Yes, what you share is indeed classic.
This post is from Microcontroller MCU
 
 
 

Guess Your Favourite
Just looking around
Find a datasheet?

EEWorld Datasheet Technical Support

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京B2-20211791 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号
快速回复 返回顶部 Return list