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.

CCS/MSP430FR2532: No source available for "__crt0_start() at .... 0xe00c{4}

Part Number: MSP430FR2532


Tool/software: Code Composer Studio

Hello,

I am new to the FRAM parts and CCS6 and working on a new product design with the MSP430FR2532. I have the FET debugger attached to the target board, it powers up and downloads the code and the debugger starts but unable to control any gpio basic HI/LOW. I origianally had the timerA0 setup and it is working but reduced the code to try and isolate why the gpio are not working. I keep getting this debug error popping up when stepping through the code and the address is the next location in assembly view...

No source available for "__crt0_start() at H:/CCS WORKSPACE\BAT_CHRG_NICD\Debug\BAT_CHRG_NICD.out:{3} 0xe00c{4}" 

#include <msp430.h>
#include <msp430fr2532.h>

int main(void) {

WDTCTL = WDTPW | WDTHOLD; // Stop watchdog timer

P1DIR |= 0x01 + 0x02 + 0x03 + 0x04;

CSCTL1 |= DCORSEL_5; // Set DCO setting - 16MHz
CSCTL2 &= (~FLLD0); // when using DCO from REF0CLK this divides DCO
CSCTL3 = SELMS__REFOCLK;
CSCTL4 = SELA__REFOCLK + SELMS__DCOCLKDIV; // ACLK = REF0CLK (32kHz), SMCLK/MCLK = DCODIV = 16MHz internal
CSCTL5 = DIVM_0 + DIVS_3; // MCLK divider (0) = 12MHz or 16MHz from interna, SMCLK dividers (8) = 1.5MHz or 2MHz internal DCO divided

__enable_interrupt();

while(1){

P1OUT ^= 0x01;
P1OUT ^= 0x02;
P1OUT ^= 0x03;
P1OUT ^= 0x04;

}

}

Any help would be appreciated. 

Thks!

Mark

  • Actually I have tried,

    P1OUT ^= BIT0;
    P1OUT ^= BIT1;
    P1OUT ^= BIT2;
    P1OUT ^= BIT3;

    I figured out how to get rid of the error for "no source found..." once clicking the debug, then load the program to the target board. I can now step through the code without the "no source errors", but still no change on the P1.0 - 4 gpio's. I am wondering if this is because the JTAG debugger is connected on port 1?

    Thks!

    Mark

  • Mark Chin said:
    I have the FET debugger attached to the target board, it powers up and downloads the code and the debugger starts but unable to control any gpio basic HI/LOW.

    For FRAM devices I think you need the following start-up code to allow the GPIOs to be controlled :

        PM5CTL0 &= ~LOCKLPM5;                   // Disable the GPIO power-on default high-impedance mode
                                                // to activate previously configured port settings

    With a simple example for a MSP430FR2532 the TI MSP430 v16.12.0.STS linker produces a warning which points to the FRAM device usage: clearing PM5CTL0.LOCKLPM5 bit at start-up Wiki page if the above line isn't present.

  • Ok Grt! That did the trick. Would have never know to look there.

    Thks!

    Mark