MSP- FET430(Debug Probe) doesn't work

Hello,

Double-check that your MSP430 has supply voltage (jumper settings). Also, be mindful that the older MSP-FET versions may not be compatible with certain CCS and IAR versions.

[FAQ] MSP-FET: SOLUTION: Using newer MSP-FETs with older CCS or IAR versions

Regards,

James

Thanks for your reply; As I mentioned, the problem appeared suddenly; before that, all were fin without any tiny compilation. My MSP_FET is 2-generation with a CE sticker and serial number, starting with 18. I could work fine with IAR version 7.1. But one day by som reason the device didn't work. Now I use IAR version 7.20, but having same problem, even I got a new Exp-board. Since the last loading code still runs MSP430- board and all the voltage-test points on the board are OK , so the board is alright.

Hello,

Were you using an IAR version older than v7.20 with the MSP-FET when this issue happened? If so, I suspect that it's related to the FAQ thread I linked above.

Perhaps you could try recovering the MSP-FET.

CCS/MSP-EXP430FR5994: CCS/MSP-EXP430FR5994 bricked on MSP-FETs / eZ-FETs update

MSP-FET: 2 pcs of new MSP-FET newest hardware version do not work: Recovery fails

Regards,

James

Hi James; The problem appeared while I as usual used IAR 7.12. I have just now observed that, MSP430F2013 _Section of my EXP_MSP Board, that also had similar problem with FET, it begins to work with IAR 7_12 and 7_20, but the connection is a little unstable to start with. All in all: I did also Cold Boot option, connecting J2 on MSP-FET. Regarding recovery, I must say, after Cold Boot, PC didn't send any message about "Start the recovery"; And the Green LED is always On. I have done the following Test/Check : [ ** Com_Port test and device identification= done and OK; ** Cold Boot=done; ** Updating_ IAR= done; ** Updating_FET_Driver= done; ** Voltage_test control(VCC, VCC_Tool, Vtarget_external,... )= done and OK; ** Test of FET's 14 Wires connections= done, OK,..] : But , unfortunately, no any of these attempts could direct me to solve the problem. And therefor the buying a new MSP-FET can neither solve the problem. My conclusion so far ---> Maybe MSP-FET as general can undergo into a code- confusing state, because it can handle msp430f2013 but not mspfg4618; both MSP are on the same EXP-Board..... Best Regards; Farid

Hi Farid,

Can you confirm that the MSP-FET can program the MSP430F2013 on the MSP-EXP430FG4618 board, but not the MSP430FQ4618?

If so, I think this issue is caused by the large capacitance (specifically 0.1uF C2) on the RST pin of the FG4618 device. The F2013 doesn't have a pull-down capacitor on RST besides the parasitic capacitance of the board, so that may explain why the issue isn't seen on F2013.

The newer MSP-FETs seem to be more sensitive to capacitance on RST, so you could try slowing down the JTAG clock speed for the FG4618 project in IAR under Project Options > Debugger > FET Debugger > Setup > Jtag speed. Alternatively, you could replace C2 with a 1nF capacitor.

Regards,

James

Hi James; James; If you has a good connection with TI, you can ask them to send me a new MSP-FET. I had came to the same conclusion as you do now about the capacitor C2=0.1uF after comparsion of two FET's 14-pins-Terminals on the board. I had also used and tested the slower speed from IAR. It didn't solve the problem. The mystic is, why the JTAG was fine for both MSP at the beginning, but suddenly it stopped working for both MSP? Why does it now work only for F2013 (is still unstable). The conditions has been the same. * * * My conclusion is ----> MSP-Fet got some code-confusing. Maybe MSP-FET is not suitable for working with two different MSP at once (back and forth). I got this Error-Message: Unknown device(FG4618). James; If you has a good connection with TI, you can ask them to send me a new MSP-FET. Farid;

Hi Farid,

I've used my MSP-FET with many different devices with no issues. They are intended for that and are intended to support all MSP devices. To me, it does sound like a software issue. Let's try this.

Can you install the latest version of CCS on your machine and then try to program the F2013 with one of our code examples using the MSP-FET? If you get an update message or recover message, please click those options to see if the MSP-FET can be updated. You may need to do it more than once.

Please make sure the power jumpers are correct on your EVM. The MSP-FET can supply power to the target device, but if there's a change that the EVM is powered externally at the same time, then there could be power conflicts that could damage the MSP-FET and/or the target devices.

Do you have any other MSP430 boards that you can test with the MSP-FET? I think that would help here. Also, I don't recommend connecting more than one MSP-FET to your PC, and I wouldn't use a USB hub if possible.

Regards,

James

Dear James; Thanks for your consideration and prompt response. Regarding updating of FET via a newer version of CCS and IAR: Having the latest CCS (Vers_10) was one of my first test-option; CCS could update the SW of FET, But with no result. The same is also happening for IAR, when I change between IAR Ver:7_12 and 7_20. I can see the indications of FET-Updating via blinking LED on MSP-FET and the graphics on IAR_Editor Screen. After that, the code-downloading will start, and here I get this message : Unknown device(4618). Regarding another MSP430 board: Because of the message: "Unknown device", I bought a another MSP EXP-4618. From here I learned that the FET is guilty. Regarding VCC: The Local Power on my Evaluation Board is taken from a very stabel and very DC, a external power supply= 3.07 V and it is connected to Pin-4 of the 14-pins terminal. I usually use Oscilloscope and Voltmeter to check the points. The main mystic is: why can the same MSP-FET again work with 2013 but not with 4618 ??? !!! The reverse situation could randomly also be happened, That is why, I think " MY FET" has difficulty to work with (very)different devices. James; I give up and will no longer think about that, unless you send me a new MSP- FET to test further. Regards Farid;

Hi Farid,

Thanks for that update. Can you please carefully review the jumper settings illustrated in Figure 3 in Chapter 5 of the MSP430FG4618/F2013 Experimenter Board (MSP-EXP430FG4618) User's Guide? Make sure PWR1 and PWR2 jumpers are populated. You could also try powering the board using the MSP-FET's power supply on Pin 2.

In the MSP430FG4618/F2013 Experimenter Board (MSP-EXP430FG4618) User's Guide, I noticed that the MSP430FG4618 uses the standard 4-wire JTAG connection while the MSP430F2013 uses the Spy-Bi-wire (2-wire) JTAG interface. Are you accounting for this difference in your CCS and IAR projects? Also, it's probably a question with an obvious answer, but I'm assuming you have unique projects for each device, correct?

I'm still not sure the MSP-FET is the problem since the JTAG circuitry on this board doesn't seem to follow the guidelines for these devices. That doesn't help issues like these either. Because of that, I'm not convinced that a new MSP-FET would solve anything.

Do you have any other MSP430 boards such as a target socket board or LaunchPad that you can program with the MSP-FET?

Regards,

James

Hello James; Regarding PWR1 and PWR2: have been checket several times and all are fine. Regarding Powering the board via PIN_2: Yes, I did it also many times. Regarding SPY_2 Wires and JTAG_4 Wires: Since my EW430/ IAR had been the free version until now, then I have not access to this setting and I hadn't any problem at the start with MSP-FET. James; Attention ---> Even I haven't access to this setting , BUT saying different debug-protocol (SPY _2 wires and TAG _4 wires) can make problem, it just will confirm my assumption about code-confusing in the FET. It seems, different debugging has caused the trouble, I have seen; Agree? That is why, I mean the EXP-MSP4618/2013 may works safer and better with two FETs without exchanging between two devices!!! ; *** Please confirm / deny my conclusion. *** ; ; Regarding another MSP Board: As I mentioned before, I bought a another EXP-MSP4618, because I could not believe, it was the MSP-FET, that could be trouble-maker. Regarding unique project for each device: Yes, each device has own unique workspace without any copy/paste. Due to my experiences I'm now very sure about MSP-FET. As I said before, why did it stop working at all and why has it accidentally start working only with one msp( msp2013: even FET is unstable) but not with 4618? *** Big day: Today I'm going to borrow a MSP-FET from my friend, here we can find the guilty one. Regardless result of that, I won't buy a another FET. I have already spent a lot of my time and some money on the EXP-MSP4618 board and FET. Best regards; Farid

Dear James; Attention: Even I haven't access to the setting of Debugging-Protocol , BUT saying different debug-protocol (SPY _2 wires and TAG _4 wires) can make problem, it just will confirm my assumption about code-confusing in the FET. It seems, different debugging has caused the trouble, I have seen; Agree? That is why, I mean the EXP-MSP4618/2013 may works safer and better with two FETs without exchanging between two devices. Best Regards Farid;

Hello Farid,

It's definitely something you could try. With two MSP-FETs connected, just be mindful of the power domains. I would just use your external supply for both. As I mentioned before, I think this issue stems from the fact that the JTAG circuitry differs from what's recommended. Rather than buying a new MSP-FET, you could buy a LaunchPad and use its onboard eZ-FET debugger to program the F2013 over SBW. Then, you could continue using the MSP-FET with the FG4618, and you wouldn't need to buy another MSP-FET.

If you're planning to use these MSP430 devices in your custom design, I would recommend using the correct JTAG circuitry to help prevent issues like this.

Regards,

James

Hello again James; As I promised, I will report to you about the conclusion of the testing my MSP4618 EXP-board with a borrowed MSP-FET. It works fine but I will not try it on 2013. And I must return it back to the owner. Based on my experiments I learned that, the MSP-FET cause problems if you have the board MSP4618/2013. Since my IAR free-version doesn't allow access to the debug-setting, may be the trouble with MSP-FET came from there; Maybe!!!? So, now it is up to you sending me a new FET. I did, what I supposed to do. Regards Farid;

Hi Farid,

I've reached out to our Tools team about this issue. They may have more questions for you. It may be Friday or early next week before I hear back from them. Thanks for your patience.

Regards,

James

Hi Farid,

I'm still waiting on our Tools team. In the meantime, could you please share the two serial numbers for both these MSP-FETs? You said yours started with "18", but I'm curious to know the other MSP-FET's serial number. Thanks.

Regards,

James

Hello my friend; My FET has this serial number: 180600188. Unfortunately I can't reach the owner of the borrow FET; But I'm quite sure, its serial number starts also with 1806 and ends with B. Farid;

Hi Farid,

That's fine, thanks. This is helpful, and I'll pass it along. I'll be out tomorrow, but I'll touch base with you next week.

Regards,

James

Hi Farid,

Is there a chance that you programmed the FG4618 device with the F2xx code? One of my colleagues pointed out an interesting note in the EVM's user's guide.

Regards,

James

Hi James; What you have sent me, just confirms again and again the fact, that MSP_EXP 4618/F2013 is not code-protected enough to work without problems. However, I have done the description with "No Luck". But I have observed, that the whole PORT6 of the FG4618 is unreliable. It means: 1) When P6DIR=0x00, P6OUT=0x00, some bits of the P6IN are high by their self. As you know PORT6 is also Analog channels to the FG4618. 2) Testing ADC12 show me, that there is no contact between Analog-channel and ADC. I think, ADC12 is self intact, because all the flags regarding ADC12 interrupt_ vector and polling works fine. Now I believe, the board has more problems than I know. So I need to set the device to the factory _setting. To do this, I have to have a FET with serial nr. 18060092B, which I know it works. Regards Farid;

Hi Farid,

The message should have arrived as a friend request. If you aren't able to accept it, please let me know and I can resend it. Alternatively, you could send me a friend request or private message through E2E. This keeps your contact information private.

Regards,

James

Hi James; I have just now send the information to you as private message via E2E. Please confirm receiving it. Farid