• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 2449 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: No debug probes/devices detected

user5891320
Prodigy 30 points
Part Number: MSP-FET
Other Parts Discussed in Thread: UNIFLASH, MSP430F6749

Dear All!

We want to program an MSP430 F6749 MCU with MSP MCU Programmer and Debugger (MSP-FET).

But in the "UNIFLASH" software (v4.5.0) and also on the webpage (dev.ti.com/uniflash) I can only see this text:

"No debug probes/devices detected"

The drivers has been installed, and I can see "MSP Application UART1" and "MSP Debug Interface" devices in device manager. Furthermore, when I click on "Detect" button in "Manual mode", the red LED flashing on MSP-FET device. And the target device reseted. 

At the first start, the MSP-FET has been updated its own firmware. So it is possible, this updating-process was not successful? In this case, can I downgrading the firmware in MSP-FET (or upgrade again) ?

Thank you!

  • 0
    TI__Mastermind 29105 points

    Hello,

    What opperating system are you using?  

    What hardware are you using?  An EVM or a custom board?  

    Is Uniflash set to Auto or Manual mode?  

    In Auto mode, Do you see Uniflash trying to search and identify the connected device when you plug in the MSP-FET?  

    If it does search, then it probably recognized the MSP-FET, but it can't seem to connect to the target MSP430.  Is the board powered externally or from the FET tool?

    Thanks,

    JD

  • 0 in reply to JD Crutchfield
    Prodigy 30 points

    Hello,
    First of all, thank you for your reply! :)

    What opperating system are you using?
    - Windows 7 Ultimate (x64)

    What hardware are you using? An EVM or a custom board?
    - a custom board (the manufacturer says that should work with MSP-FET).

    Is Uniflash set to Auto or Manual mode?
    - auto mode, but I also tried in manual mode

    In Auto mode, Do you see Uniflash trying to search and identify the connected device when you plug in the MSP-FET?
    - yes, when I plug in MSP-FET, then Uniflash trying to search (like on your picture)

    Is the board powered externally or from the FET tool?
    - powered from the FET tool (but I also tried power from external, with FET-tool pin 4)

  • 0 in reply to user5891320
    TI__Mastermind 29105 points
    Hey User,

    Thanks for the feedback. Between Uniflash's behavior and what you are seeing in you device manager, It sounds like the MSP-FET is opperating as expected. If I unplug my FET from any board, it also just sits at "No debug probes/device detected", because it can't talk with the MSP430.

    It seems like the issue is between the MSP-FET and the target MSP430 MCU.

    Do you have any other boards that you know work, that you could plug the FET on to makesure it detects that target?
    Any chance that someone previous purposefully locked the JTAG by enabling the Security Fuse?
    Also, Is the orientation of the JTAG connecter correct

    Thanks,
    JD
  • 0 in reply to JD Crutchfield
    Prodigy 30 points

    Hi,

    When I running this commands: read device info, erase device, program device, I got this message: 

    Error connecting to the target: The Debug Interface to the device has been secured


    You can see the wiring between the MSP430F6749 device and MSP-FET tool, with the actual message, on the attached image.

    (The MSP430F6749 device works well, and I can program the manufacturer's own unique programmer.)

  • 0 in reply to user5891320
    TI__Mastermind 29105 points

    Hey User,

    Thanks for the additional information.  As for the JTAG connections, these look okay but please see "Figure 2-1. Signal Connections for 4-Wire JTAG Communication" within the MSP430 Hardware Tools User Guide (http://www.ti.com/lit/slau278) for full details on what the recommended programming circuit should be.

    user5891320 said:
    Error connecting to the target: The Debug Interface to the device has been secured

    This sounds like the JTAG Electronic Fuse has been blown, locking the JTAG and SBW interfaces.  Section 1.11.2 of the Family User's guide describes this behavior for the device.  

    Has the original manufacturer locked the JTAG interface on the device?  If so, they would need to provide the key for BSL access to the device.

    Thanks,

    JD  

  • 0 in reply to JD Crutchfield
    TI__Mastermind 29105 points
    Also, how much power do you think the board pulls? If the board has many other components on it, can you try powering the board externally?

    I see you are trying to power the device/board from the programmer, which only works <50 mA. In some of the older programmers the JTAG Fuse was incorrectly checked if there was an issue with powering the device.

    Thanks,
    JD

**Attention** This is a public forum