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.
Hello Guys,
Good day.
Our customer is having an issue with the MSP-FET, The red LED is always On during initial connection to the hardware.
I found from a different post below, that the MSP-FET will stop working if there is too much current required to power the board. To fix that you can try and get the device into BSL mode, then the JTAG could gain control.
How can they put the device into BSL mode, then gain control of JTAG? They normally use it for programming just like plug and play.
Thanks to confirm,
Art
Hi Art,
Are they using a USB hub? We don't recommend that. Also, you raise a good point about not exceeding the current supply rating of the MSP-FET. They should definitely measure that.
Also, does the MSP-FET ever work normally (e.g. both red and green LEDs blink when programming a target device)? Your post mentions that the red LED is always on but then implies that this only happens during the initial connection. If it doesn't happen on later connections, perhaps this indicates that some on-board capacitors have charged up during the initial connection.
I found the following note in the MSP Debuggers user's guide about entering/exiting BSL mode on the MSP-FET:
If the MSP-FET is configured to support BSL communication, debugger functionality is disabled. To switch to debugger mode, either perform a power cycle (unplug the USB cable) or configure the baud rate to 8001. The BSL mode is disabled until sending a BSL entry baud rate command.
Hello James,
Apologies for the late response for I was waiting for the customer feedback.
According to them, they are not using USB hub for MSPFET.
MSPFET was working normally for months, they purchased it two years back.
They are using teraterm, MSP debug interface COM Port, changing baud rate to 8001 to get into BSL mode. It responds back with "j" and red LED turn steady ON.
Thanks and regards,
Art
According to them, they are not using USB hub for MSPFET.
Thanks for checking.
MSPFET was working normally for months, they purchased it two years back.
Perhaps it has been damaged electrically from ESD or continuous overcurrent.
They are using teraterm, MSP debug interface COM Port, changing baud rate to 8001 to get into BSL mode. It responds back with "j" and red LED turn steady ON.
They should use the MSP Application interface COM port for entering BSL mode, not the MSP Debug interface COM port.
Thanks a lot James!
I might direct customer in this thread in case of additional inquiries.
Best regards,
Art
That's fine assuming the customer's myTI account is associated with a corporate email address.
[FAQ] New posting requirements for E2E Support Forums
Also, there are a lot of threads about MSP-FET issues that they could find by searching the forum.
Hello James,
Upon using MSP Application interface it does not responds, red LED comes steady on.
Can we replace any parts which are damaged?
Thank you
Abhishek
Upon using MSP Application interface it does not responds, red LED comes steady on.
According to the MSP Debuggers user's guide, the red LED indicates an overcurrent condition or other error. Here's a note describing how to go from BSL mode to debug mode.
If the MSP-FET is configured to support BSL communication, debugger functionality is disabled. To switch to debugger mode, either perform a power cycle (unplug the USB cable) or configure the baud rate to 8001. The BSL mode is disabled until sending a BSL entry baud rate command.
Can we replace any parts which are damaged?
You're welcome to replace parts, but we won't be able to provide guidance on that. Instead, we would recommend purchasing a new MSP-FET. You may want to try the recovery process described in the MSP Debuggers user's guide.
We have already tried BSL mode, debug mode, nothing works.
We tried recovery process too, does not work.
Thanks for your help.
Please let us know if you have any more questions. I'll go ahead and mark this thread resolved.
**Attention** This is a public forum