• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 79 subscribers
  • Views 552 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.

MSP-FET: MSP-FET cannot detect MSP430F6736A in UniFlash, but XDS110 is recognized as probe

Shuaishuai Ling
Prodigy 20 points

Part Number: MSP-FET
Other Parts Discussed in Thread: MSP430F6736A, , UNIFLASH, TPS61022, MSP430F6736, EVM430-F6736

Hello TI team,

I am having an issue connecting an MSP-FET to my MSP430F6736A target board and would like to ask for your help.

Problem Description

When using UniFlash with MSP-FET, during device scanning the MODE LED on the MSP-FET starts blinking.

After some time, UniFlash reports that it cannot detect the probe or the device, and then the MODE LED stops blinking and turns off.

Using RF Flash Programmer 2, I can see the connected port/probe, but the target device (board) is not detected (see attached screenshot).

In Windows Device Manager, the MSP-FET is correctly recognized (see attached screenshot).

When I connect an XDS110 to the PC, UniFlash can correctly detect the probe.

Because of this, I am not sure whether:

There is a communication issue between the PC and MSP-FET,

or

There is a problem in my target board hardware design (SBW/JTAG connection, VTG, reset, etc.).

Attached Files

Screenshot: RF Flash Programmer 2 showing probe detected but no target device

Screenshot: Windows Device Manager showing MSP-FET

Target board schematic

PCB layout (SBW/JTAG section highlighted)

Photo of the assembled board

Additional notes regarding the hardware:

In the BST power circuit (TPS61022), the two output capacitors were not originally populated.

The 47 kOhm pull-up resistor on MSP430F6736A pin 80 (RST/NMI) was also not populated initially.

These components were added later by scraping the solder mask and manually soldering them.

 

I would appreciate your guidance on whether this behavior points more toward a hardware connection/design issue or a debug probe compatibility/configuration issue, and what checks you would recommend next.

Thank you very much for your support.

Best regards,

Mark

 

  • 0
    TI__Expert 5270 points

    Hi Mark,

    The following is the 4-wire JTAG signal connection from our MSP430 Hardware Tools User Guide when using the MSP-FET:

    Can you confirm that these connections are correct between the Target device and MSP-FET 14-pin header? I would also recommend adding at least a 1.1nF capacitor to RST/NMI.

    Also, you mentioned being able to have the XDS110 recognized. Have you also been able to program/debug with it?

    Best Regards,
    Brian

  • 0 in reply to Brian Lee
    Prodigy 20 points

    Hi Brian,

    Thank you for your response and for sharing the reference from the MSP430 Hardware Tools User Guide.

    Regarding the XDS110:

    • It appears that XDS110 does not support programming the MSP430F6736A.

    • In UniFlash, after selecting XDS110 as the probe, there is no option available for MSP430F6736A (see attached screenshot).

    • Additionally, the TI product page for XDS110
      (https://www.ti.com/tool/TMDSEMU110-U) explicitly states that MSP430 devices are not supported (see attached screenshot).

    Because of this, I have not been able to program or debug the MSP430F6736A using XDS110.

    Regarding the hardware connections:

    • I have now added a 1 nF capacitor from RST/NMI to GND, as you recommended.

    • After making this change, I re-tested the setup with all 4-wire JTAG signals fully connected according to the reference diagram.

    • However, the MSP-FET still cannot detect the target device, and in some attempts UniFlash is also unable to detect the MSP-FET probe.

    For additional testing, I ran the “Program MSP430 (example).bat” from MSPFlasher, and the execution result is attached as a screenshot.
    The flasher is able to detect the USB FET, but it fails when accessing the target device.

    I have carefully re-checked the JTAG wiring against the reference diagram and believe the connections are correct.
    However, to avoid any oversight on my side, I have attached photos of the actual hardware connections for your review.

    Please let me know if you would recommend any further checks or measurements (e.g. specific signals or timing to probe) to help isolate whether this issue is related to the target hardware or the MSP-FET connection.

    Best regards,
    Mark

  • 0 in reply to Shuaishuai Ling
    TI__Expert 5270 points

    Hi Mark,

    For this device, Test is also required for programming using MSP-FET. If this still does not work, can you check that the power from your battery is stable. Lastly, can you scope the TMS,TCK, TDO, and TDI lines to see if the FET is communicating with the device at all?

    Best Regards,
    Brian

  • +1
    Prodigy 20 points

    The issue is resolved. I am posting the solution here for reference.

    I was able to successfully connect to and program the MSP430F6736 using an MSP-FET with a DIP adapter.

    Although the device could not be detected in SmartRF Flash Programmer 2, I was able to successfully connect and read the device memory in UniFlash, confirming that the debug interface was functional.

    The root cause turned out to be incorrect power connections on the MCU.
    After reviewing the EVM430-F6736 Application Note (SLA A517F) and implementing the power supply circuitry starting on page 23, including the correct handling of AUXVCC, VASYS, and related supply pins, the device immediately became accessible.

    Reference document:
    https://www.ti.com/lit/an/slaa517f/slaa517f.pdf

    Special thanks to Brian for the detailed analysis and guidance that helped identify the issue.

**Attention** This is a public forum