• State TI Thinks Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 10250 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

msp430fr5739: Unknown device in msp-exp430FR5739, but not in custom board

Gustavovelascoh
Intellectual 340 points
Part Number: MSP430FR5739
Other Parts Discussed in Thread: MSP-EXP430FR5739, MSP-EXP430FR6989, , MSP-TS430RHA40A, UNIFLASH, MSP430FR6989

I have an issue trying to debug a project in msp-exp430FR5739.

I'm using CCSv7 on Gnome Ubuntu 16.04, I use the MSP-EXP430FR6989 for connecting to a MSP430FR5739 in two different boards, one is the MSP-EXP430FR5739 and the another is a custom board. I connect 4 lines in each case (3V3, GND, RST and TST). Using my custom board I can load and debug the project, but for launchpad, Unknown device message appears when trying to load the program.

What could be wrong in this case?

  • 0
    TI__Prodigy 450 points
    Hey, I'm looking into this. I'll get back to you when I have some more information.
  • 0
    TI__Prodigy 450 points

    I attempted to replicate your error by programming a MSP-EXP430FR5739 and a MSP-TS430RHA40A board (to replicate your custom board) using the eZ-FET on the MSP-EXP430FR6989. I used CCSv7 on Windows 10, but  since you were already able to program your custom board, I am assuming it will work with Ubuntu 16.04 as well.

    I have the boards oriented so that the Micro-USB port and the Mini-USB port (for the MSP-EXP430FR6989 and the MSP-EXP430FR5739, respectively) are in the top left corners of the boards.

    I was able to program both devices via the MSP-EXP430FR6989. It seems that the most likely cause of your issue is an improper connection between the two devices. In order to communicate between the MSP-EXP430FR6989 and the MSP-EXP430FR5739, one must connect the top row pins of the top right header on the MSP-EXP430FR6989 to the bottom row pins of the top right header on the MSP-EXP430FR5739. 

    The connections should be as follows:

    MSP-EXP430FR6989

    MSP-EXP430FR5739

    3V3

    VCC

    SBWTDIO

    RST

    SBWTCK

    TEST

    In addition, the GND pin from the top row of the same header on the MSP-EXP430FR6989 should be connected to one of the two ground pins near the bottom left corner of the MSP-EXP430FR5739 board. So, all in all, you should have 4 wires connecting the MSP-EXP430FR6989 to the MSP-EXP430FR5739.

    Can you confirm if the two boards are connected in this way?

  • 0 in reply to Matthew Walck
    Intellectual 340 points

    Hi Matthew, I double-checked the connections, even I ask two of my teammates to review the set-up before saying anything about the issue an they agree that connections were OK. I tested again using two MSP-EXP430FR5739 launchpads and the result was the same.

    Also, I tried just to load the program to launchpads and custom board using Uniflash web but it happened again, load was successful for my custom board, but for launchpads "Unknown device" message appears.

  • 0 in reply to Gustavovelascoh
    TI__Guru 56685 points
    Hello Gustav,

    Can you post a picture of your setup on the MSP-EXP430FR5739 ? There could be a jumper out of place in your setup that is causing this to not work. Unfortunately we cannot replicate your issue currently, and cannot get your exact setup as we do not have access to an Ubuntu machine. That being said, since you can program one board via the MSP430FR6989 LP, I do not think that aspect of your setup is an issue.
  • 0 in reply to Gustavovelascoh
    TI__Prodigy 450 points

    Hey Gustav,

    I went ahead and set up my connection between the MSP-EXP430FR6989 and the MSP-EXP430FR5739 the same way you have yours set up, and I got the same problem.

    I was able to fix this by moving the wire from the bottom left corner VCC pin up to the VCC pin on the header (I.e. connecting the VCC pin from the top right header on the MSP-EXP430FR6989 to the VCC pin on the top right header of the MSP-EXP430FR5739). After I did this, I was able to program the device normally.

    Try moving this wire and see if it fixes your problem.

  • 0 in reply to Matthew Walck
    Intellectual 340 points

    Hi Matthew, I tried your suggested connection in two MSP-EXP430FR5739 launchpads but it did not work. I also tried connecting 3V3 to VCC pin in left header, but it did not work neither.

    EDIT: I was asked to update emulator firmware but that did not fix the issue. At the other hand, custom board is still working.

  • 0 in reply to Gustavovelascoh
    TI__Guru 56685 points

    Hello Gustav,

    The only other suggestion we can make is to shorten the connections between the LP and the FR57-EXP board. The reason for this is that SBW communications is greatly effective by capacitance on the communication lines.

  • 0 in reply to Jace H
    Intellectual 340 points
    Hi Jace, I changed all the four connections from 8" (20.5 cm) to 4"1/2 (11.5 cm) but the device is still unrecognized.
  • 0 in reply to Gustavovelascoh
    TI__Guru 56685 points
    Hello Gustav,

    All the additional advice I can give is to try to reduce capacitance on the SBW lines (TEST/RST). Sorry I cannot help you more on this.
  • 0 in reply to Jace H
    Intellectual 340 points

    Hi Jace and Matthew, thanks for your support. As an additional feedback, I tested it on Windows 7, and had the same result using the MSP-EXP430FR6989 as programmer, but using directly the MSP-EXP430FR5739 works fine. Package marking of launchpads and custom board also differ. Launchpads have H37K for revision, date code and assembly site, but assembly lot code is illegible. Custom board has H4CK/AC20.

  • 0 in reply to Gustavovelascoh
    TI__Prodigy 450 points

    Hey Gustavo,

    If you would like to program the MSP-EXP430FR5739 using Ubuntu via the MSP-EXP430FR6989, the only suggestion we can make is to attempt to further reduce capacitance in the connections.

    However, since programming it directly on Windows 7 is supported by the board and worked for you, I would suggest using this method moving forward.

**Attention** This is a public forum