MSP430FR5739: Reset after programming

Hi Asaf,

Are the devices you are programming from the same batch of devices that used to program correctly, or are these devices newer (purchased later in time)?

There are few date codes, there is no characteristic to the failed ones

Asaf

Hi Asaf,

Ok.  So when these devices fail it sounds like this happens while still connected to the JTAG pod.  What happens if you disconnect JTAG and cycle power?

Is this the same JTAG pod you have been using before or new one?

What brand and model#?

What software do you use with the JTAG pod to program the devices?

Hi Dennis, Thanks

Don't have all answers yet.

Ok.  So when these devices fail it sounds like this happens while still connected to the JTAG pod - right.

What happens if you disconnect JTAG and cycle power? - I should check, probably work properly

Is this the same JTAG pod you have been using before or new one? - yes

What brand and model#? - the JTAG POD or MSP? I will check on Sunday

What software do you use with the JTAG pod to program the devices? Checking

Regards

Asaf

Hi Dennis, Thanks

So when these devices fail it sounds like this happens while still connected to the JTAG pod - right.

What happens if you disconnect JTAG and cycle power? Work properly

Is this the same JTAG pod you have been using before or new one? - yes, Same one

What brand and model#? - the JTAG POD or MSP? Texas Instruments MSP-FET Flash Emulator Tool - SN 15120032B

What software do you use with the JTAG pod to program the devices? Our SW using MSP430 DLL also it happen with MSP430 Flasher.

After programming we try to reset the device:

MSP430_Reset(FORCE_RESET | ALL_RESETS, 1, 1);

Returns RESET_ERR.

Regards

Asaf

Hello Dennis,

Any advise or recommendation?

Thanks

Asaf

Hi Asaf,

I'm in contact with our tools team to get guidance on this issue.

Hi Dennis,

Any update

Thanks

Asaf

Hello Asaf,

I'm really sorry for the disconnect.  I'm trying to get help on my side from our development tools team.

I'm going to escalate the situation.

I will get you an answer shortly.

Hello Asaf,

Our development tools team is asking the following:

Which version of the MSP430.dll the customer is using?

I just checked the MSP430_reset API and its description. This is what we offer nowadays RESET_ALL is not supported anymore.  

\param   method:        The bit mask specifying the method(s) to use to reset the device:

           - PUC_RESET: The device is reset using PUC (i.e., a "soft" reset).

           - RST_RESET: The device is reset using the RST/NMI pin (i.e., a "hard" reset).

           - VCC_RESET: The device is reset by cycling power to the device.

           - FORCE_PUC_RESET, FORCE_RST_RESET, FORCE_VCC_RESET

In addition to that. What is the hardware layout of the PCB they want to program?

Is the MSP430 supply voltage generated by the MSP-FET or an external one?

Can you please share the schematic of the JTAG connector.?

hello Dennis,

Attached layout and schematic

The voltage supply is from the board not from the FET

i will answer regarding the DLL version

thanks

Asaf

Motor-driver_r6C01.brdMotorDriver _ 02-uC.pdf 

MotorDriver _ 05-Connectors.pdf 

Hello Dennis,

I was thinking I answered all the questions but I do not find it

we use DLL version 1.3.20.

we use external voltage

see schematic bellow

also

We took failed board and good board and switch the MSP between the boards. the failure goes with the MSP, meaning the board that was OK now fail and and the board that was fail now OK.

Please advise

Thanks

Asaf 

8863.MotorDriver _ 02-uC.pdf0216.MotorDriver _ 05-Connectors.pdf

Hi Asaf,

Ok, let me check with out product team to see if they can provide some suggestions on how further isolate this issue.

Hi Asaf,

Our product development engineer is suggesting that this isn't a particular device failure if everything works fine after disconnecting JTAG and resetting the device.

These devices are first reflowed to the PCB, then programmed using JTAG, correct?

Hi Dennis,

Yes the devices re-flowed to the PCB before programming

I would like to ask

Is it possible to send failed device to failure analysis? (we will take them from the PCB)

Thanks

Asaf

Hi Dennis

Attached are two scope screen of the Open device to MSP430.dll  

MSP430_OpenDevice("MSP430FR5739", "", 0, 0, 0);

The Yellow is the CLK signal and Green is Data

We see difference between good and fail device - maybe it can help to understand the issue

It look like there is difference from the firs connection

Thanks

Asaf 

Hi Asaf,

Thank you for the scope shots.  Yes, very helpful.

I will share with our development tools team.

Let me make sure I get the conditions correct:  1st scope shot is "good", and 2nd scope shot is "bad", correct?

Hi Dennis,

Yes - First good

Please check also the failure Analysis option

Thanks

Asaf

Hello Dennis

Any updates

Thanks

Asaf

Hi Asaf,

I'm elevating this to get some priority help.

Hi Asaf,

It's been a bit challenging to get support on this one. Since the silicon works properly through a power cycle or if you force a manual reset (not through BSL), then it's not an issue with the silicon and so I have had to rely on our tools team for guidance.  It has been suggesting that I try to replicate this issue before they look into this, so I will try to set this up today and get it working.   I will have further questions for you shortly.

Hi Dennis,

Thanks

Please do not hesitate to ask what you need

Regards

Asaf

Hi Asaf,

I have no updates at this time.

It's been some time since your original posting and I wanted to check if you are still seeing the same failure rate 10 out of 200 or has the failure rate gone up or done?

Hi Dennis

we still have that issue

currently we did not checked other batch of PCBs but it probably there

Thank

Asaf

Hi Asaf,

Here are a few more suggestions from our tools team:

-          It would be good to read the memory contents to make sure both devices match

-          If FRAM is the same, I would also request customer to download RAM from a failing device and download to a working device. I’ve seen cases where customers don’t initialize FRAM/RAM properly in their code, and causes different behavior.

-          As mentioned earlier in this thread the reset option from MSP Flasher RESET_ALL is not supported, has the customer tried the other reset options?

-          It would be good to check his MSP-Flasher settings too since that is easier to debug compared to using DLL directly

-          I see the schematics but I don’t see how this is connected to the MSP-FET. Is VCC_RAW_PRE a valid 3.3V and is it connected to VCC_TARGET?

-          One thing noticed in the the scope plots is to see that VCC drop. It would be good to check the VCC_TARGET connection

Hi Dennis

Thanks 

We download the FRAM and compare but we did not tried to switch between devices - we will try

I missed the reset _all issue, we checked other reset.

I will check the VCC connections

VCC_RAW_PRE is 12V, we generate 3.3V on board. the MSP connect to the POD by CLK and DATA signals and GND

Regards.

Asaf

Hi Asaf,

Ok.  Keep me updated on your progress.

Hello Asaf,

Have you made any progress with your problem?