• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 3911 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430fr4133 launchpad example project build failure.

David Pekin
Intellectual 350 points
Other Parts Discussed in Thread: MSP430FR4133, MSP-EXP430FR4133, MSP430WARE, MSP430F2012, MSP-EXP430F5529LP, MSP430-FLASHER

Hello.  

I just received the MSP430FR4133 launchpad development kit.  

I've have been developing for a different smaller MSP430 target using the IAR embedded workbench V6.50.2 with the USBFET stick with no problem.  

I downloaded the MSP-EXP430FR4133_Software_Examples for Windows from the TI site, unzipped them and loaded the OutOfBox_MSP430FR4133.eww project file.  The IAR workbench indicated it was an older version project so I let it update to the current version.  During the Make process I ended up with a litany of warnings copied below.

Upon trying to download to the target board the IAR workbench hangs at the first "beginning debug session" message.  The red and yellow light at the top of the dev board illuminate but nothing else happens.  If I disconnect the USB cable I receive a driver version message but I think that's a red herring sinceI've unplugged the USB cable.  

Has anyone else had this problem???  

Thanks in advance.

- Dave

Building configuration: OutOfBox_MSP430FR4133 - Debug
Updating build tree...

44 file(s) deleted.
Updating build tree...
adc.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
crc.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
cs.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
eusci_a_spi.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
eusci_a_uart.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
eusci_b_i2c.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
eusci_b_spi.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
framctl.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
gpio.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
hal_LCD.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
lcd_e.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
main.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
pmm.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
rtc.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
sfr.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
StopWatchMode.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
Warning[Pa079]: undefined behavior: variable "Centiseconds" (declared at line 48) (or a value reached by some form of indirection through it) is modified more than once C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\StopWatchMode.c 121
without an intervening sequence point in this statement
Warning[Pa079]: undefined behavior: variable "Seconds" (declared at line 49) (or a value reached by some form of indirection through it) is modified more than once without C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\StopWatchMode.c 124
an intervening sequence point in this statement
Warning[Pa079]: undefined behavior: variable "Minutes" (declared at line 50) (or a value reached by some form of indirection through it) is modified more than once without C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\StopWatchMode.c 127
an intervening sequence point in this statement
Warning[Pa079]: undefined behavior: variable "Hours" (declared at line 51) (or a value reached by some form of indirection through it) is modified more than once without an C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\StopWatchMode.c 129
intervening sequence point in this statement
sysctl.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
TempSensorMode.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
Warning[Pe144]: a value of type "unsigned short volatile *" cannot be used to initialize an entity of type "int volatile *" C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\TempSensorMode.c 53
Warning[Pe144]: a value of type "unsigned short volatile *" cannot be used to initialize an entity of type "int volatile *" C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\TempSensorMode.c 54
timer_a.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
tlv.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
wdt_a.c
Warning[Pe047]: incompatible redefinition of macro "BAK_RAM_BASE" (declared at line 436 of "C:\430\inc\msp430fr4133.h") C:\1Pekin\Downloads\MSP-EXP430FR4133_Software_Examples_windows\MSP-EXP430FR4133_Software_Examples_windows\Firmware\Source\OutOfBox_MSP430FR4133\driverlib\MSP430FR2xx_4xx\inc\hw_memmap.h 102
Linking

Total number of errors: 0
Total number of warnings: 27

  • 0
    TI__Guru* 79301 points

    Hi dpekin,

    Thanks for reporting this - I reproduced your issue using IAR 6.50.1. The problem is with a mismatch between the driverlib version in that zip file for the out-of-box code and the header file version in your newer IAR. The zip file has packaged up an old version of driverlib with an old version of hw_memmap.h that expected an older msp430fr4133.h file in IAR, vs the newer IAR version has a newer msp430fr4133.h that defines some of the same things. I took a newer version of hw_memmap.h from the empty driverlib project example for FR4133 and dropped it in, and suddenly all those redefinition errors disappeared (because the newer hw_memmap.h file expects these to all already be defined in msp430fr4133.h and so doesn't redefine them).

    I will report this to get the project updated.

    In the meantime, here is my recommendation for you to workaround this:
    1. Go to www.ti.com/.../msp430ware
    software-dl.ti.com/.../index_FDS.html
    And do the standalone install of the software (since you are using IAR not CCS).
    2. Go to your MSP430Ware installation path, and go to <MSP430Ware_version>/driverlib/driverlib/MSP430FR2xx_4xx/inc/hw_memmap.h
    3. Replace the old hw_memmap.h in your Out-of-box project with hw_memmap.h from the path above

    Now when you build, those errors about macro redefinition should disappear. 
     
    Thanks for posting and I hope this gets you up and running with the MSP-EXP430FR4133. Let me know if you are still having issues getting the device to program - I was not able to reproduce that issue. You are simply plugging the Launchpad directly into the PC correct?

    Regards,
    Katie

  • 0 in reply to Katie Pier
    Intellectual 350 points

    Thanks Katie.  I will do what you suggest to remedy the compile issue.

    However, my larger issue is that I can't program the Launchpad from the PC.  I've tried to burn the binaries that are provided in the examples directory but when the MSP430Flasher program runs it detects the FET port but then hangs when it tries to initialize communications with the board.  The red and the yellow lights on the board to light up when the communications initialization starts.

    Also, this same tool and environment does communicate and successfully burn the MSP430F2012 chip on the MSP-FET430U14 USB development board.

    I've tried to update the drivers with the drivers from the FET driver package but Windows says the current drivers are the latest.  

    I'm running Windows XP SP3.  

    Any thoughts?  Thanks.

    - Dave

  • 0 in reply to David Pekin
    Intellectual 350 points
    Actually it hangs at "Initializing interface on TIUSB port..."
  • 0 in reply to David Pekin
    TI__Guru* 79301 points

    Hi dpekin,

    I'd like to help with this larger programming issue that you are having.
    What version of MSP430-Flasher are you using? I believe it says this in the command line when you run it. If the version is old enough it likely does not recognize the eZ-FET on the MSP-EXP430FR4133 Launchpad  - the emulation section of this Launchpad is a newer improved design vs the older eZ-430 emulation on the USB stick kit that you mentioned you were using before. If the MSP430-Flasher is from before this new design first came about on the MSP-EXP430F5529LP, then the flasher likely doesn't recognize it. The latest version of MSP430-Flasher currently online is 1.3.10.

    Another issue would be if you don't have CCS or IAR installed, you may need the new drivers for the newer emulation on this board (same kind of reason I mentioned above). You can install the latest drivers at http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430_FET_Drivers/latest/index_FDS.html (the latest flasher installation also can direct you here).
     
    Regards,
    Katie

  • 0 in reply to Katie Pier
    Intellectual 350 points
    Hello,

    I just downloaded it with the Launchpad example files zip. It is version 1.3.0.

    I never tried the MSP430 Flasher program with the older USB dev board. With the older USB FET board I can download and debug from the IAR tool directly. With the new 4133 board the IDE does not recognize it and the MSP Flasher program doesn't work either.

    Thanks, Dave
  • 0 in reply to David Pekin
    TI__Guru* 79301 points

    Hi dpekin,

    Thanks for the additional information. I know this is a lot of questions, but I feel that we are getting close - you mentioned that IAR 6.50.2 doesn't recognize the MSP-EXP430FR4133 device either. Can you:

    1. Go to Device Manager in Windows, plug a micro-USB cable from the MSP-EXP430FR4133 device directly to a USB port on the PC, and report how the MSP-EXP430FR4133 enumerates (should show up as 2 entries under Ports (COM & LPT) as shown)?

    2. You mention that IAR hangs at the first "Beginning debug session" message.. does IAR crash or it just becomes unresponsive? Does it ask you at any point to update the firmware?

    Regards,

    Katie

  • 0 in reply to Katie Pier
    Intellectual 350 points

    Hello Katie,

    The MPS devices show up identically to what you show except that they are comm 5 and 4 rather than 67 and 66.

    The IAR system hangs when it goes to communicate with the device.  It does not crash.

    That is similar to the operation of the MPS Flasher program.  It hangs when it tries to initialize the interface.  It does not crash.  In fact, while it is hanging, if I unplug the USB cable, it returns and generates a communication error.

    Thanks,

    Dave

  • 0 in reply to David Pekin
    TI__Guru* 79301 points

    Hi Dave,

    Do you happen to have access to a second MSP-EXP430FR4133 Launchpad, for comparison purposes? If not, that's ok - I realize that you may only have 1, but it would be a good test if you or a colleague happen to have a second one to test.

    You could also try the Launchpad on a colleague's computer with a fresh IAR install or MSP430-Flasher + drivers install (again for comparison - trying to find if this is hardware vs software issue)
     
    Another test could be to try the free Elprotronic Fet-Pro430 Lite software and see if you are able to program the device with that, again for comparison. www.elprotronic.com/productdata

    Regards,
    Katie

  • 0 in reply to Katie Pier
    Intellectual 350 points
    Hello Katie,

    I indeed do have a second MSP4133 Launchpad and it reacts exactly the same as the first.

    How do the drivers for this Launchpad differ from the single FET driver that works correctly for the 2012 development USB stick? What ports are they using?

    One thing I failed to mention was that the XP-pro SP3 I'm running is a VM running on Windows 8.

    - Dave
  • 0 in reply to David Pekin
    Intellectual 350 points
    I've done more diagnostics and the connection failure is due to VMWare for some reason.

    I can run the MSPFlasher program successfully on the native Windows 8 OS but not on the XP VM.

    Worse case I could build the image on the XP VM and burn it from Windows 8 but that prevents me from doing any real time debugging from the IAR environment. I will search the forum to see there's any info on running the tools on an XP VM. As I mentioned previously, the tool works correctly with the older MSP430F2012 USB dev tool.

    - Dave
  • 0 in reply to David Pekin
    TI__Guru* 79301 points
    Hi Dave,

    Thanks - that helps to rule out a hardware issue then since both Launchpads act the same.

    The MSP-EXP430FR4133 has a totally different emulation hardware on it than the F2012 USB stick - you can find an explanation in the document www.ti.com/.../slau647 MSP Debuggers User's Guide - see table 1 . The MSP-EXP430FR4133 has an eZ-FET that supports all SBW-capable MSP430 devices vs the eZ430-F2013 has am eZ430 emulation that has a more limited feature set and only supports a few devices.

    I will check about VM support - I'm wondering if that could be part of your problems. However, the board should be able to work with Windows 8 - is there a reason for you to use a virtual machine? You may want to try running this directly from Windows 8 and see if your issue goes away to confirm if the virtual machine is causing the problem?

    Regards,
    Katie
  • 0 in reply to Katie Pier
    Intellectual 350 points
    Thanks Katie,

    We use a separate VM for each client. This keeps their files, and development environment separate and self contained from other client's.

    I haven't yet found any answers on getting it to work in the VM on the forum. I hope you have better luck.

    If I have to resort to building the image in the VM and burning it using the MSP Flasher program, how do I convert the object.d43 file which is generated by the IAR compiler to a .txt file format that the MSP Flasher program takes? What is the .d43 format and what is the .txt format. I'm sure there's a converter utility to handle that.

    Thanks again,

    - Dave
  • 0 in reply to David Pekin
    Intellectual 350 points
    Hi Katie,

    I said that the MSP Flasher program worked correctly on the Windows 8 OS. It did but, when it ran, it indicated that the FET firmware on the device was old and asked if it should update to the current version. I said yes it could update. The system burned the new FET firmware and then the OutofTheBox application firmware. Upon repowering the software looked the same (as it should).

    BUT.... When I went to burn another image with the same MSP Flasher program on that target, the MSP Flasher indicates that it does not recognize the device. It gives:
    Error 16
    Unknown Device!

    Unfortunately, I suspect that updating the FET firmware has"broken" this environment. Any suggestions on recovery?

    Thanks,

    - Dave
  • 0 in reply to David Pekin
    TI__Guru* 79301 points

    Hi Dave,

    I see your other thread: msp430FR4133 FET Firmware PostUpdate Failure - brick or salvage?

    I'll take the discussion on this new issue there.

    Regards,

    Katie

  • 0 in reply to David Pekin
    TI__Guru* 79301 points

    dpekin said:
    If I have to resort to building the image in the VM and burning it using the MSP Flasher program, how do I convert the object.d43 file which is generated by the IAR compiler to a .txt file format that the MSP Flasher program takes? What is the .d43 format and what is the .txt format. I'm sure there's a converter utility to handle that.

    Hi Dave,

    IAR can generate the TI-txt file directly. See

    Regards,

    Katie

  • 0 in reply to Katie Pier
    TI__Guru* 79301 points
    I've also replied in your other thread here: e2e.ti.com/.../2017890

**Attention** This is a public forum