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.

Using MSP-FET Flash Emulation tool on RaspberryPi

Other Parts Discussed in Thread: MSP-FET, MSPDS, MSP430-FLASHER, UNIFLASH, MSP-FLASHER

Hello,

I'm working on a Production tool built around a Raspberry Pi (ARM based processor). I'm unable to get the MSP-FET Flash Emulation Tool to work. Here's what I've done so far.

1. Downloaded latest MSP Debug Stack from http://www.ti.com/tool/mspds

productionpi@raspberrypi:~/tiLibSources/slac460 $ mspdebug tilib --allow-fw-update
MSPDebug version 0.24 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2016 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc.

Using new (SLAC460L+) API
MSP430_GetNumberOfUsbIfs
MSP430_GetNameOfUsbIf
Found FET: HID_FET
MSP430_Initialize: HID_FET
FET firmware update is required.
Starting firmware update (this may take some time)...
tilib: MSP430_FET_FwUpdate: MSP-FET / eZ-FET recovery failed (error = 73)
tilib: device initialization failed

Two things to notice. One is obvious, I get an error message. The second is the MSP430.dll v3.3.1.4. Shouldn't this match the revision 3.8.1.0000? If I remove the libmsp430.so from /usr/lib, mspdebug will complain about not finding the file. Finally, I can use the programmer in x86 VM with no problem. I'm not sure which version of libmsp430.so I'm using.

Not really sure where to go from here?

Diego

  • Sorry, I cut off what else I've done.
    2. Compiled libmsp430.so
    3. Downloaded latest mspdebug from http://dlbeer.co.nz/mspdebug/
  • Hi Diego,

    This is a very interesting question. So, to make sure I'm understanding correctly, you are using the Raspberry Pi as a controller for some sort of production programming setup, and you want to control the MSP-FET via the MSP Debug Stack, correct? And your Raspberry Pi runs some form of Linux?

    I have a feeling that what you are doing probably is not something that's been tested before or supported, but I'm trying to see if I can get any ideas about your issue from some of the people that maintain the mspds. I'll let you know as soon as I learn more.

    Regards,
    Katie
  • Hi Diego,

    I have not seen that open source program before so I'm not familiar with it (don't think it comes from TI). However, we're concerned where it said you had MSP430.dll 3.3.1.4 - are you sure that you have the latest version of MSPDS and that it is being correctly used by your project/how you're running this? We think the problem could be that 3.3.1.4 is so old that the new MSP-FET may not be supported by that version. I asked our tools team and they said you would need to update MSP-Debug or change the msp430.so (MSPDS) you get as build artifact from the open source release. Or they thought maybe you have an old version of the MSP-FET firmware or have not built it.

    Can you try seeing if you can update MSP-Debug to truly use the latest version - we'd suspect that has to do with your issue.

    Regards,
    Katie
  • Hello Katie,

    I've actually been in contact with the developer of the program. I asked him the same question. Below is his response.

    > When you print out the Chip info database from MSP430.dll, is that from the libmsp430.so? Because the library doesn't match what I've downloaded.
    
    Hi Diego,
    
    Yes, it is, but confusingly it's not actually related to the tilib
    driver. That data was historically extracted from a version of
    MSP430.DLL/libmsp430.so, but it's used for the "fet" driver family.
    
    Cheers,
    Daniel
    

    Again, I've downloaded the latest files and compiled libmsp430.so manually. So I'm confident I have the latest. 

  • Hi Diego,

    Do you know if this developer has tested the software with MSP-FET, or only the older MSP-FET430UIF? I'm just wondering if there could be anything in there that is not supporting the newer tool, despite you getting the latest files manually.

    One other thought - it looks like your MSP-FET is requesting an update of the firmware. You could try taking your PC and one of the latest CCS, CCS Uniflash IAR, MSP430-Flasher, etc and allow it to update your MSP-FET, then try again with your raspberry pi, just to see if anything is different.

    Regards,
    Katie
  • Hello Katie,

    I don't believe he's tested it. I will try and verify.

    I hooked up the FET to Windows and ran the MSP-Flasher software. Sure enough it needed to be flashed. I flashed it and then plugged it back into the RPi. I made it a step further. It also said it needed to update the firmware, which I tried to do. It went all the way to 100% and then said the update failed (error = 74). So really no change. I ran the mspdebug again and I got error 73.

    Also, I ran MSPFlasher on the RPi. It shows the ASCII art and then nothing happens. Both mspdebug and MSPFlasher share the libmsp430.so library no? Maybe that isn't built correctly?

    Diego

  • Hi Diego,

    Were you able to get this working - did link help get you what you needed, for future reference for others trying to do the same?

    -Katie
  • Hi Diego,

    I'm in the same situation you're been six month ago. Do you succeed making msp-fet working on RPI ?
  • Frederic Pierson said:
    Hi Diego,

    I'm in the same situation you're been six month ago. Do you succeed making msp-fetworking on RPI ?

    Here is example of JTAG flashing on RPI without any extra hardware, using RPI I/O lines by mspdebug.

    http://forum.43oh.com/topic/10035-4-wire-jtag-with-mspdebug-and-raspberry-pi-gpio/

**Attention** This is a public forum