- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software: Code Composer Studio
Good evening...
I have the above EVM and am continually getting my code to break and jump into boot.c @ CSTART_DECL _c_int00_noargs_mpu(void).....
I have not noticed problems until I went ahead and updated (a couple of weeks ago) to add CC and RF family products to the existing MSP products that I have been using...It clearly seems the compiler has updated to 20.?? as I have seen warnings saying I had been using compiler 18.??
Please explain what is going on here.....I notice this with hardware only as well as hardware/software breakpoints that I add BEFORE I start the debugger running. This is VERY annoying and on top of it the EVM will periodically go off into space and CANNOT be repowered without re-flashing the MSP DEBUGGER....To do this I must hold in the reset button while the flashing is going on, then I release the reset and the code will flash. I have two EVM boards and both will do the same thing....It's a 50/50 whether they work or lock up. I notice when the issue comes up the RED and GREEN LED on the debugger side will sit there and flash on and off RED, GREEN, RED, GREEN, etc. forever!!
What is going on?????????
Here is the current code that is causing grief! If I place one HW breakpoint somewhere before the while loop (ex. INITUART)....The code runs to there then I hit run again and it stops itself back at INITUART...so it goes into the while loop (verified by my logic analyzer and the signalling of the UART) AND then somehow resets and pops out!
/*
* d_rxtx.c
*
* Created on: Apr 8, 2020
* Author: ridge
*/
#include <msp430.h>
#include <string.h>
#include <stdint.h>
#include "rc.h"
#include "LPRSradio.h"
volatile char *pRx;
char incoming[20];
const char *pTx;
const char *configCmdAck[] = {"ER_CMD#a01", "ER_CMD#W2", "ER_CMD#b1"};
const char *testack = "ACK";
uint8_t i = 0;
boolean tx = T;
int k;
int main(void)
{
WDTCTL = WDTPW | WDTHOLD; // stop watchdog timer
IOconfig;
initClockTo16MHz();
initUART();
pRx = incoming;
pTx = configCmdAck[0];
while (1)
{
__bis_SR_register(LPM3_bits + GIE); //go to sleep: LPM3
if (tx)
pTx++;
else {
if (!strncmp(incoming, configCmdAck[i], 10))
{
pTx = testack;
i++;
UCA1IFG |= UCTXIFG;
}
pRx++;
}
}
}
#pragma vector=USCI_A1_VECTOR
__interrupt void M(void)
{
switch(__even_in_range(UCA1IV, USCI_UART_UCTXCPTIFG))
{
case USCI_NONE: break;
case USCI_UART_UCRXIFG:
tx = F;
*pRx = UCA1RXBUF;
__bic_SR_register_on_exit(LPM3_bits);
break;
case USCI_UART_UCTXIFG:
tx = T;
if (*pTx != '\0')
UCA1TXBUF = *pTx;
__bic_SR_register_on_exit(LPM3_bits);
break;
case USCI_UART_UCSTTIFG: break;
case USCI_UART_UCTXCPTIFG: break;
}
}
Sincerely
Steve
Hi Steve,
sorry to hear about this negative experience on your side.
You mentioned on one hand the change of the compiler version on one hand and use of break points on the other hand. For the first, you could could try selecting the compiler, which you have been using before. When clicking with the right mouse button on the project, you can go to "properties" and then "General" you should see the used compiler version. By clicking on the small pull down button on the right of the compiler version, you can see the available options, and could select the old one. If only the current one shows up, there was a major update of your CCS IDE and the older compiler versions have not been moved to respective directories in the CCS installation path. In this case you could search through the previous CCS installations and copy the compiler directories into the respective path of the most recent CCS version.
The other point are the break points. You stated you're using HW break points. Though, as especially with the small MSP430 devices, the number of available HW breakpoints is very limited, the IDE tends to use for some things, like stopping at first line of main SW breakpoints. It could be, that these SW breakpoints are somehow getting corrupted and causing trouble with code execution, as SW breakpoints are small pieces of code included by the debugger/compiler in debug mode. Thus you could also try disabling the use of SW breakpoints. Please see here a screen shot, where to find this option.
Best regards
Peter
**Attention** This is a public forum
