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.

MSP-EXP430F5529: MSP-EXP430F5529 Experimenter Board - User Experience Code Builds, but won't Run

Part Number: MSP-EXP430F5529

Experiment Board with preloaded User Experience code worked fine.

Imported the User Experience project for the Experimenter Board to a new Workspace - it now builds in Release mode, Debug was too big. Seems to load into the board, but won't run completely. The original code on board was erased, and replaced with my new build of the unmodified code.

I can single step through the code: starts with a blank LCD, then numerous steps later it turns on the LCD backlight, so it has the code at least up to a point. But when I run it at full speed - all I see is a blank LCD with the backlight on.

Power slide switch set to eZ & plug PC USB cable into the eZ USB (lower left of board) - is this correct?

Build gets no errors, but some suspicious warnings:

<Linking>
"../lnk_msp430f5529.cmd", line 126: warning: Linker command file has no
sections of type=VECT_INIT, but does contain .intXX sections. This file may
be out of date. Generating interrupt pointers for all .intXX sections. The
default handler provided in the RTS will be used if no other handler is
found. It is recommend that you update your linker command file to the
latest version.

warning: creating output section ".data" without a SECTIONS specification

If I build the Target only - get an error - gmake: *** No rule to make target 'MSP430F5529-Exp-Board'

I'm missing a step or two somewhere - any ideas?

  • Hi Ted,

    I am not familiar with the case, but I have found some materials may helpful for you.

    Power slide switch set to eZ & plug PC USB cable into the eZ USB (lower left of board) - is this correct?

    It is correct, and please refer to the photo:

    warning: creating output section ".data" without a SECTIONS specification

    This means that you should creat d .data section in cmd file, to let complier know where to put global variables with initial values.

    I'm missing a step or two somewhere - any ideas?

    As for the code warning, please refer to the MSP-EXP430F5529 Experimenter Board User's Guide: https://www.ti.com/lit/pdf/slau330 

    It describes the software installation, have you browsed it? It may by helpful.

    Best Regards

    Sal

  • Hi Sal,

    Thanks for your post. I've gone through the UG several times, TI really needs to update this about using the Experimenter Board with new versions of CCS.

    I did replace the lnk_msp430f5529.cmd file with one from one of my projects for the 5529 LP - a much newer version of the cmd file - and it fixed this problem. CCS now builds / loads the code into the Experimenter Board / and it runs. Just about everything except USB is working.

    So I was looking for a newer version of lnk_msp430f5529_USB.cmd but couldn't find one. Any suggestions on that?

  • Hi Ted,

    I have gone through MSP430Ware, maybe you can refer to the msp430USB.cmd.

    It is include in MSP430Ware\usblib430\MSP430_USB_Software\MSP430_USB_API\USB_API.

    msp430USB.txt
    /* 
     * ======== msp430usb.cmd ========
     */
    /************************************************************
    * USB
    ************************************************************/
    
    tSetupPacket = 0x2380;
    
    tEndPoint0DescriptorBlock = 0x0920;
    
    tInputEndPointDescriptorBlock = 0x23C8;
    
    tOutputEndPointDescriptorBlock = 0x2388;
    
    abIEP0Buffer = 0x2378;
    
    abOEP0Buffer = 0x2370;
    
    pbXBufferAddressEp1 = 0x1C00;
    pbYBufferAddressEp1 = 0x1C40;
    pbXBufferAddressEp81 = 0x1C80;
    pbYBufferAddressEp81 = 0x1CC0;
    
    pbXBufferAddressEp2 = 0x1D00;
    pbYBufferAddressEp2 = 0x1D40;
    pbXBufferAddressEp82 = 0x1D80;
    pbYBufferAddressEp82 = 0x1DC0;
    
    pbXBufferAddressEp3 = 0x1E00;
    pbYBufferAddressEp3 = 0x1E40;
    pbXBufferAddressEp83 = 0x1E80;
    pbYBufferAddressEp83 = 0x1EC0;
    
    pbXBufferAddressEp4 = 0x1F00;
    pbYBufferAddressEp4 = 0x1F40;
    pbXBufferAddressEp84 = 0x1F80;
    pbYBufferAddressEp84 = 0x1FC0;
    
    pbXBufferAddressEp5 = 0x2000;
    pbYBufferAddressEp5 = 0x2040;
    pbXBufferAddressEp85 = 0x2080;
    pbYBufferAddressEp85 = 0x20C0;
    
    pbXBufferAddressEp6 = 0x2100;
    pbYBufferAddressEp6 = 0x2140;
    pbXBufferAddressEp86 = 0x2180;
    pbYBufferAddressEp86 = 0x21C0;
    
    pbXBufferAddressEp7 = 0x2200;
    pbYBufferAddressEp7 = 0x2240;
    pbXBufferAddressEp87 = 0x2280;
    pbYBufferAddressEp87 = 0x22C0;
    

    B.R.

    Sal

  • Hi Sal,

    Good suggestion, tried it, linked in the file, and USB Mouse & USB MicroSD still don't work. Also Tilt Puzzle & Cube Demo lock up. Most of the stuff does work, including reading the microSD card. Also discovered some of these apps have to use the 5529 USB port, not the eZ USB port - that fixed the PC seeing the microSD card on Exp board as external RAM.

    TI needs to clean up this UG and add details about getting it working with current CCS versions.

  • Hi Ted,

    Sorry I didn't help much.

    I will ask a senior expert for the details information, and contact you as soon as I get feedback.

    B.R.

    Sal

  • Sal, You were helpful, you fixed the first problem, thanks. Ted

  • Hi Ted,

    eZ USB used to download image and run some UART example.

    If you woluld like to test USB peripherals function, you need connect 5529 USB port:

    Thanks!

    Best Regards

    Johnson

**Attention** This is a public forum