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.

Compiler Warning #10083-D LOAD placement ignored for "SIGNATURE_MEMORY": object is uninitialized

Other Parts Discussed in Thread: MSP430FR5949, MSP430WARE, MSP430FR5969

I posted this in the TI C/C++ Compiler Forums, and they told me that these forums would better assist me.  The link to the other post is below.

http://e2e.ti.com/support/development_tools/compiler/f/343/p/319090/1110500.aspx#1110500

I'm getting started with a project on the MSP430FR5739, and I'm getting an unfamiliar compiler warning.  The warning shows that this issue is coming from the linker command file of my microcontroller (msp430fr5739.cmd).  This is the compiler warning:

#10083-D LOAD placement ignored for "SIGNATURE_MEMORY":  object is uninitialized

Even though the warning comes from outside my code, I've posted a simplified version of my code below.

#include <msp430.h>
#include <stdio.h>
#include <stdlib.h>
#include <stdbool.h>
/*
 * main.c
 */
int main(void) {
    WDTCTL = WDTPW | WDTHOLD;   // Stop watchdog timer
    /*************CLOCK INITIALIZER*************/
    //Writes password to enable CS register access
    CSCTL0_H = 0xA5;
    //Set max. DCO setting to 24MHz
    CSCTL1 |= DCOFSEL0 + DCOFSEL1 + DCORSEL;
    // Sets the MCLK source to DCOCLK,
    // the SMCLK source to DCOCLK,
    // and the ACLK source to VLOCLK
    CSCTL2 = SELM0 + SELM1 + SELS0 + SELS1 + SELA0;
    // Sets the MCLK clock divider to 0,
    // the SMCLK clock divider to 0,
    // and the ACLK clock divider to 0,
    CSCTL3 &= 0x00;
    // Enables conditional module requests for
    // MCLK, SMCLK, and ACLK
    CSCTL6 |= MCLKREQEN + SMCLKREQEN + ACLKREQEN;
    /*************TEMPRETURE SENSOR CONTROL*************/
    // Turn off temp sensor
    REFCTL0 |= REFTCOFF;
    REFCTL0 &= ~REFON;
    /*************CONFIGURE MPU*************/
    MPUCTL0 = MPUPW;                        // Write PWD to access MPU registers
    //Add any changes to the MPU here
    MPUSEG = 0x0804;                        // B1 = 0xC800; B2 = 0xD000
                                            // Borders are assigned to segments
    MPUCTL0 = MPUPW+MPUENA;                 // Enable MPU protection
    return 0;
}
// trap ISR assignment - put all unused ISR vector here
#pragma vector = PORT1_VECTOR, ADC10_VECTOR, PORT2_VECTOR, \
    TIMER0_A0_VECTOR, TIMER0_A1_VECTOR, WDT_VECTOR, COMP_D_VECTOR, \
    DMA_VECTOR, PORT3_VECTOR, PORT4_VECTOR, RTC_VECTOR, \
    SYSNMI_VECTOR, TIMER0_B0_VECTOR, TIMER0_B1_VECTOR, \
    TIMER1_A0_VECTOR, TIMER1_A1_VECTOR, TIMER1_B0_VECTOR, \
    TIMER1_B1_VECTOR, TIMER2_B0_VECTOR, TIMER2_B1_VECTOR, \
    UNMI_VECTOR, USCI_A1_VECTOR, USCI_B0_VECTOR, USCI_A0_VECTOR
__interrupt void TrapIsr(void)
{
  // this is a trap ISR - check for the interrupt cause here by
  // checking the interrupt flags, if necessary also clear the interrupt
  // flag
}

Note that I'm using Code Composer Studio Version: 5.5.0.00077. The good news is that it doesn't seem to cause any issues when I'm actually running the code (even when I add simple toggle-pin functions).  From what I understand from the previous post, it looks like the linker command file doesn't have a group named SIGNATURE_MEMORY, thus, initiating this warning.  However, No solution was found in looking for the problem.

I would still like to try to fix this issue.  Any suggestions?

  • Hi dauletle,

    I see the same thing in my version of CCS. To me, it looks like the linker file has been updated to try to make it easier to assign a JTAG and BSL password. However, it is giving this warning that you mentioned. The warning disappears if I comment out the part of the linker file line 152 that is " > SIGNATURE" - then no warning. Note however, that this warning shouldn't hurt anything with your code if you just leave it - it should be fine.

    I'm going to contact our team that maintains our header and linker files to see  what we can do about this though, because our examples shouldn't give warnings like this and it seems that something is not quite right with the implementation in the linker file. Thanks for your patience while we look into this. 

    Regards,

    Katie

  • Hi Katie,

    We met a similar problem in case of using MSP430FR5949.
    CCS Console showed as below.

    **********************
     "../lnk_msp430fr5949.cmd", line 159: warning #10083-D:
     LOAD placement ignored for "SIGNATURE_MEMORY":  object is uninitialized
    **********************
    Do you have any updates for this issue?
    I would like to know about  "What is the cause of this warning ?" " And how to resolve this warning?"
    If you have any questions, please let me know.

    Best regards.
    Kaka

  • Hi Kato,

    I was having trouble reproducing your issue - which CCS version, and compiler version do you have?

    I am using CCSv6.0.0.00190, and the compiler version (under Project > Properties > General) is TI v4.3.2.

    Do you see this issue simply when building the project? Or does it only show up when you actually load code into the part and enter a debug session?

    Regards,

    Katie

  • Hi Kaite.

    Thank you for your response.

    I summarized my environments as below.

    CCS:Ver5.5.0.00077
    Compiler Version:TI v4.2.1
    Linker command file: lnk_msp430fr5949.cmd
    Grace:2.20.2.32
    MSP430Ware:1.80.1.03
    XDCTools:3.25.4.88

    When I was compiled the project, this message was shown in console.  I noticed that if used the following environment, this message was not shown in console.

    CCS:5.5.0.00077
    Compiler:TI v4.2.1
    Linker Command File:lnk_msp430fr5969.cmd
    Grace:2.20.1.12
    MSP430Ware:1.60.2.09
    XDCtools version:3.25.4.88

    I hope that this information will be help you.
    Best regard.

    Kaka

  • Hi Kato,

    MSP430FR5949 and other MSP430FR59xx devices were not fully released yet in CCSv5.5, and I think a number of fixes to the tools support for these parts were made before the devices released. I would recommend using the latest CCSv6.0 which will have the latest full release version of all tools and support for these devices.

    Regards,

    Katie

  • Hi Katie,

    Thank you for your response.

    I agree with you about customer should use the latest CCS(i.e. vesrion6).

    I will inform this to customer again.

    Best regards,

    Kaka

**Attention** This is a public forum