• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 78 subscribers
  • Views 2208 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.

MSP430 Flasher returns 'Unknown Device' on custom board

Jeff Cooper
Prodigy 20 points
Other Parts Discussed in Thread: MSP430F5338, MSP-FET

I have a MSP430F5338 on a custom board that I'm having trouble accessing the the MSP430 Flasher v1.3.7 utility. I'm running on Ubuntu 14.04 using a MSP-FET. I'm getting an 'unknown device' error from the flasher utility when running the tools without any command line arguments.

I've verified that my software install of the flash utility and MSP-FET are working correctly as I can identify and program a MSP430F5338 on a MSP-TS430PZ100C devkit without any problems.

I've attached two logic analyzer screen shots of runnign the flasher tool just to identify the attacted processor.

The first is of a bad transaction with the beta board:

The output from the tool is:

* -----/|-------------------------------------------------------------------- *
* / |__ *
* /_ / MSP430 Flasher v1.3.7 *
* | / *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ ttyACM0 <- Selected
* Initializing interface @ ttyACM0...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3000 mV...done
* Accessing device...
# Exit: 16
# ERROR: Unknown device
* Powering down...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver : closed (Internal error)
* ----------------------------------------------------------------------------
*/


The second is a good transaction with the devkit.


The output from the tool is:

* -----/|-------------------------------------------------------------------- *
* / |__ *
* /_ / MSP430 Flasher v1.3.7 *
* | / *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ ttyACM0 <- Selected
* Initializing interface @ ttyACM0...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3000 mV...done
* Accessing device...done
* Reading device information...done
*
* ----------------------------------------------------------------------------
* Arguments :
* ----------------------------------------------------------------------------
* Driver : loaded
* Dll Version : 30501001
* FwVersion : 30501001
* Interface : TIUSB
* HwVersion : U 3.0
* JTAG Mode : AUTO
* Device : MSP430F5338
* EEM : Level 7, ClockCntrl 2
* VCC OFF
* ----------------------------------------------------------------------------
* Powering down...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver : closed (No error)
* ----------------------------------------------------------------------------
*/


On the devkit, I see a couple of pulses on the TDO line just after the 0.4 second mark. I don't see those on the beta board. That looks like the first place that the traces start to differ.

Does anyone have any theories as to why I can't communicate with my custom board?

thanks,
Jeff

  • 0
    TI__Guru 56685 points
    Jeff,

    Please see figure 2-1 of the HW User Guide to double check your schematic for JTAG connections. www.ti.com/lit/slau278

    You can also post your schematic here to be checked.

    Regards,
    JH
  • 0 in reply to Jace H
    Prodigy 20 points

    Jace,

    I've double-checked the MSP-FET connections to the board and I believe that they're correct.  The board is actually designed to use a daughter board board that connects to the MSP-FET via a 0.1" header.  The daughter board then uses a 0.05" header to connect to the beta board.

    I've wired a cable to connect directly from the MSP-FET to the 0.05" socket on the beta board.  The cable wired as:

    MSP-FET Beta Board J18
    1 2
    3 4
    5 6
    7 8
    9 10
    11 12
    4 3
    8 7

    I've attached a PDF showing the page of the schematic with the MSP430.  I've removed resistors R251-R252 and R263-R266 (lower left corner of the schematic) to remove a connection to a OMAP 37x that is also on the board.

    msp430.pdf

    The only major difference that I see between figure 2-1 and this is that R1 is 49K instead of 47K.  But then I'm not a EE by training, just a SE with delusions of grandeur, so it's very possible that I've missed something.  

    Jeff

  • 0 in reply to Jeff Cooper
    TI__Guru 56685 points

    Jeff,

    since this is a device that also supports 2-wire JTAG, the upper limit for the capacitor attached to RST line is 2.2nF. This would be Cap C158 in your case. Please see note E of Figure 2-1 in the HW User Guide.  www.ti.com/lit/slau278

    That being said, you may be adding additional capacitance to the line when connecting through all those header pins. Since oyu really cant change this on board, then I suggest shortening the cable for the MSP-FET to the board.

    Regards,

    JH

**Attention** This is a public forum