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.

Problems with building and using the package for MSP430F6779

Other Parts Discussed in Thread: MSP430F6779, MSPWARE

Hi

We are using a MSP430F6779 device and CCS6 with the following settings:

TI v4.4.3 Compiler

XDCTools 3.31.0.24

TI-RTOS 2.12.1.33

I had problems using the drivers and found out that I had to build the packagemyself using the 'Creating TI-RTOS Projects for Other MSP430 Devices' Guide. Only to find that the device was not fully supported. Adding MSP430F6779 to MSP430DEVLIST in titros.mak would generate errors on building the files I need. I had to edit the package.bld file as well as this, to pull in the correct files as follows:

I haven't added all the files as I am only using UART at the moment and I am unsure of the correct list of files for my device.

var MSP430ObjList2 = [
    "./gpio/GPIOMSP430.c",
    "UART.c",
 "./uart/UARTEUSCIA.c",
 "I2C.c",
    "./i2c/I2CEUSCIB.c",
];

I also had to add the following:

   if ((MSP430DevList[dev].match(/MSP430F[56][\d\w]*/g)) &&
   (MSP430DevList[dev] == "MSP430F6779")) {                                                      <- If it is my device
    //MSP430ObjList = MSP430GenericObjList.concat(MSP430ObjList);

                makeLibs("lib/drivers_" + MSP430DevList[dev], tiTargets,
                         MSP430ObjList2, copts, MSP430DevList[dev], MSPWareDir,       <- Pass my new object list
                         MSP430Headers);

                makeLibs("lib/drivers_" + MSP430DevList[dev], iarTargets,
                         MSP430ObjList2, copts, MSP430DevList[dev], MSPWareDir,
                         IAR_MSP430Headers);
            }

I started to initialise my UART in the main, only to find that the linker could not see the UART functions, even though I included the header files as instructed by the RTOS manual. The functions I am using and cannot see are:

UART_init,

UART_Params_init

UART_open

I now have included the files directly into my project that are contained in the ../ti/drivers/ folders, UART.h and UARTEUSCIA.h so that they can be seen.

I am now getting the following error:

I'm now starting to think that there is too much hacking and manipulating of files going on, that technically should be pretty much automated when the package is built.

Is there an alternative to the methods I am using to get it to work for MSP430F6779 and please could you help me with why I am now getting this error?

Thanks Again

  • Sorry, my screen shot cannot be seen. The error is:

    #10010 errors encountered during linking; "DebugApp.out" not built
    #10234 unresolved symbols remain
    unresolved symbol UART_config, first referenced in c:/ti61/tirtos_msp43x_2_12_01_33/packages/ti/drivers/lib/drivers_MSP430F6779.ae430X<UART.oe430X>
  • Hi Mark,

    I moved this to the (deleted group) forum, because it looks like you are having a problem with some of the TI-RTOS code/drivers. Hopefully they will be better able to help you there.

    -Katie

  • Hi Mark,

    UART_config is defined in the `Board`.c file. If you are using a custom board, then you may have to create Board files. I have attached a modified `Board`.c that has changes to include eUSCI references. Have a look at the attached files.

    Also, you are right, it should have been pretty much automated but I think we are missing some documentation and automation in the build files. I have filed a bug report to fix it: https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDO-Web&contextid=SDOWP&entityID=SDOCM00116795&entityDefName=IncidentReport&username=readonly&password=readonly

    Vikram

    4111.MSP_EXP430F5529.c 2553.MSP_EXP430F5529.h

  • Thanks Vikram

    I am now getting the following errors:
    unresolved symbol EUSCI_A_UART_disable, first referenced in C:/ti61/tirtos_msp43x_2_12_01_33/packages/ti/drivers/lib/drivers_MSP430F6779.ae430X<UARTEUSCIA.oe430X> DebugApp    C/C++ Problem
    unresolved symbol EUSCI_A_UART_disableInterrupt, first referenced in C:/ti61/tirtos_msp43x_2_12_01_33/packages/ti/drivers/lib/drivers_MSP430F6779.ae430X<UARTEUSCIA.oe430X> DebugApp    C/C++ Problem
    unresolved symbol EUSCI_A_UART_enable, first referenced in C:/ti61/tirtos_msp43x_2_12_01_33/packages/ti/drivers/lib/drivers_MSP430F6779.ae430X<UARTEUSCIA.oe430X> DebugApp    C/C++ Problem
    unresolved symbol EUSCI_A_UART_enableInterrupt, first referenced in C:/ti61/tirtos_msp43x_2_12_01_33/packages/ti/drivers/lib/drivers_MSP430F6779.ae430X<UARTEUSCIA.oe430X> DebugApp    C/C++ Problem
    unresolved symbol EUSCI_A_UART_getInterruptStatus, first referenced in C:/ti61/tirtos_msp43x_2_12_01_33/packages/ti/drivers/lib/drivers_MSP430F6779.ae430X<UARTEUSCIA.oe430X> DebugApp    C/C++ Problem
    unresolved symbol EUSCI_A_UART_init, first referenced in C:/ti61/tirtos_msp43x_2_12_01_33/packages/ti/drivers/lib/drivers_MSP430F6779.ae430X<UARTEUSCIA.oe430X> DebugApp    C/C++ Problem
    unresolved symbol EUSCI_A_UART_receiveData, first referenced in C:/ti61/tirtos_msp43x_2_12_01_33/packages/ti/drivers/lib/drivers_MSP430F6779.ae430X<UARTEUSCIA.oe430X> DebugApp    C/C++ Problem
    unresolved symbol EUSCI_A_UART_transmitData, first referenced in C:/ti61/tirtos_msp43x_2_12_01_33/packages/ti/drivers/lib/drivers_MSP430F6779.ae430X<UARTEUSCIA.oe430X> DebugApp    C/C++ Problem

  • Hi Again

    I have now got this working by include the eusci_a_uart.c and .h files from the MSPWare. They wouldn't be seen by having them in the include directories.

    For clarification, when creating the package file, I have created it for the MSP430F6779 based on the following drivers:

    var MSP430ObjList2 = [
    "./gpio/GPIOMSP430.c",
    "UART.c",
    "./uart/UARTEUSCIA.c",
    "Watchdog.c",
    "./watchdog/WatchdogMSP430.c",
    "I2C.c",
    "./i2c/I2CEUSCIB.c",
    "SPI.c",
    "./spi/SPIEUSCIBDMA.c",
    "./spi/SPIEUSCIADMA.c",
    ];

    They will then need definitions in the device files, similar to what you have supplied me with once the package is built.

    Please can you confirm that this list is correct for the MSP430F6779? or am I missing something?

    Thank you
  • The list looks fine to me. I don't see anything obvious that is missing.

    Vikram