MSP430F2617: MSP430F2617 verification error while flashing

artem dmitriev5

Part Number: MSP430F2617
Other Parts Discussed in Thread: MSP430F2618, MSP430-FLASHER, UNIFLASH, MSP-GANG, MSP-FET, MSP-TS430PM64

Hello!

One of the clients has a problem, related to MSP430F2617 verification. He says " While we flashing MSP430F2617 controllers using of MSP430 Flasher, they are defined as MSP430F2618.

When we using this program we get error 60 in 30% of devices. See attached log." Can you help me?

log.txt

Fri Nov 10 10:22:26 2017:	* -----/|-------------------------------------------------------------------- *
Fri Nov 10 10:22:26 2017:	*     / |__                                                                   *
Fri Nov 10 10:22:26 2017:	*    /_   /   MSP430 Flasher v1.3.7                                           *
Fri Nov 10 10:22:26 2017:	*      | /                                                                    *
Fri Nov 10 10:22:26 2017:	* -----|/-------------------------------------------------------------------- *
Fri Nov 10 10:22:26 2017:	*
Fri Nov 10 10:22:26 2017:	* Evaluating triggers...done
Fri Nov 10 10:22:26 2017:	* Checking for available FET debuggers: 
Fri Nov 10 10:22:26 2017:	* Found USB FET @ COM3 <- Selected
Fri Nov 10 10:22:26 2017:	* Initializing interface @ COM3...done
Fri Nov 10 10:22:26 2017:	* Checking firmware compatibility: 
Fri Nov 10 10:22:26 2017:	* FET firmware is up to date.
Fri Nov 10 10:22:26 2017:	* Reading FW version...done
Fri Nov 10 10:22:26 2017:	* Setting VCC to 3000 mV...done
Fri Nov 10 10:22:27 2017:	* Accessing device...done
Fri Nov 10 10:22:28 2017:	* Reading device information...done
Fri Nov 10 10:22:28 2017:	* 
Fri Nov 10 10:22:28 2017:	* ----------------------------------------------------------------------------
Fri Nov 10 10:22:28 2017:	* Arguments   : 
Fri Nov 10 10:22:28 2017:	* ----------------------------------------------------------------------------
Fri Nov 10 10:22:28 2017:	* Driver      : loaded
Fri Nov 10 10:22:28 2017:	* Dll Version : 30202000
Fri Nov 10 10:22:28 2017:	* FwVersion   : 30202000
Fri Nov 10 10:22:28 2017:	* Interface   : TIUSB
Fri Nov 10 10:22:28 2017:	* HwVersion   : U 1.64
Fri Nov 10 10:22:28 2017:	* JTAG Mode   : AUTO
Fri Nov 10 10:22:28 2017:	* Device      : MSP430F2618
Fri Nov 10 10:22:28 2017:	* EEM         : Level 3, ClockCntrl 2
Fri Nov 10 10:22:28 2017:	* VCC OFF
Fri Nov 10 10:22:28 2017:	* ----------------------------------------------------------------------------
Fri Nov 10 10:22:28 2017:	* Powering down...done
Fri Nov 10 10:22:28 2017:	* Disconnecting from device...done
Fri Nov 10 10:22:28 2017:	* 
Fri Nov 10 10:22:28 2017:	* ----------------------------------------------------------------------------
Fri Nov 10 10:22:28 2017:	* Driver      : closed (No error)
Fri Nov 10 10:22:28 2017:	* ----------------------------------------------------------------------------
Fri Nov 10 10:22:28 2017:	*/
Fri Nov 10 10:22:32 2017:	* -----/|-------------------------------------------------------------------- *
Fri Nov 10 10:22:32 2017:	*     / |__                                                                   *
Fri Nov 10 10:22:32 2017:	*    /_   /   MSP430 Flasher v1.3.7                                           *
Fri Nov 10 10:22:32 2017:	*      | /                                                                    *
Fri Nov 10 10:22:32 2017:	* -----|/-------------------------------------------------------------------- *
Fri Nov 10 10:22:32 2017:	*
Fri Nov 10 10:22:32 2017:	* Evaluating triggers...done
Fri Nov 10 10:22:32 2017:	* Checking for available FET debuggers: 
Fri Nov 10 10:22:33 2017:	* Found USB FET @ COM3 <- Selected
Fri Nov 10 10:22:33 2017:	* Initializing interface @ COM3...done
Fri Nov 10 10:22:33 2017:	* Checking firmware compatibility: 
Fri Nov 10 10:22:33 2017:	* FET firmware is up to date.
Fri Nov 10 10:22:33 2017:	* Reading FW version...done
Fri Nov 10 10:22:33 2017:	* Setting VCC to 3000 mV...done
Fri Nov 10 10:22:34 2017:	* Accessing device...done
Fri Nov 10 10:22:34 2017:	* Reading device information...done
Fri Nov 10 10:22:34 2017:	* Unlocking BSL memory...done
Fri Nov 10 10:22:34 2017:	* Unlocking Info Memory A...done
Fri Nov 10 10:22:34 2017:	* Loading file into device...done
Fri Nov 10 10:22:43 2017:	* Verifying memory (C:\Users\���1\AppData\Local\Temp\PULSAR_04_M3_V115.hex)...
Fri Nov 10 10:22:44 2017:	# Exit: 60
Fri Nov 10 10:22:44 2017:	# ERROR: Verification error
Fri Nov 10 10:22:44 2017:	* Resetting device (RST/NMI)...done
Fri Nov 10 10:22:44 2017:	* Starting target code execution...done
Fri Nov 10 10:22:44 2017:	* Disconnecting from device...done
Fri Nov 10 10:22:44 2017:	* 
Fri Nov 10 10:22:44 2017:	* ----------------------------------------------------------------------------
Fri Nov 10 10:22:44 2017:	* Driver      : closed (No error)
Fri Nov 10 10:22:44 2017:	* ----------------------------------------------------------------------------
Fri Nov 10 10:22:44 2017:	*/

over 6 years ago

0 Matt Calvo over 6 years ago

TI__Genius 13670 points

Hello!

By looking at your log file it seems that you are using version 1.3.7 of the MSP430-Flasher. First off, please try updating to the newest version (1.3.16) of the MSP430-Flasher in order to make sure that it isn't a version issue. I'd also like to know what operating system you are using to make sure it is compatible with our software.

Another option would be to use our UniFlash software with has similar functionality to the MSP430-Flasher but incorporates a user friendly GUI.

Please let me know if this helps you move forward with your issue!

Best regards,

Matt Calvo

0 Ryan Brown1 over 6 years ago

TI__Guru**** 202126 points

Hello artem,

This is most likely a connection issue causing a communication error. What kind of FET tool is being used (MSP-FET, MSP-FET430UIF, MSP-GANG, eZ-FET, etc.) and is the target board a TI EVM or custom PCB? Have any other setups been attempted which produce different results? How is the device powered when programmed and how long are the traces between the FET tool and target? Can schematics or board images be provided?

Regards,
Ryan

0 artem dmitriev5 over 6 years ago in reply to Matt Calvo

Intellectual 330 points

The client says that they've tried to use FET430UIF, MSP-FET with standart cables. MSP430-flasher is the latest. OS was Win XP 32, Win7 64. Custom PCB.

The client draw attention that there is MSP430F2617 inscription on the chip, but MSP430-Flasher defined some controlllers as MSP430F2618. And he gets error 60 in this case.

0 Ryan Brown1 over 6 years ago in reply to artem dmitriev5

TI__Guru**** 202126 points

Can schematics or board images be provided for the custom PCB? Are there similar errors if a different software programmer is used (CCS, FET-Pro430, UNIFLASH, etc)?

Regards,
Ryan

0 artem dmitriev5 over 6 years ago in reply to Ryan Brown1

Intellectual 330 points

Баг определения микроконтроллера.pdfThe client've made an experiment using of MSP-TS430PM64 Rev1.1 board and MSP430F2617TPM controller, MSP-FET. See attached file. MSP430Flasher defined MSP430F2617TPM as MSP430F2618. What is the reason of the problem may be?

0 Lukas Badura over 6 years ago in reply to artem dmitriev5

TI__Expert 4695 points

How many units are affected with this symptom?

0 artem dmitriev5 over 6 years ago in reply to Lukas Badura

Intellectual 330 points

1500 units. The client says that all MCUs are defined as MSP430F2618. But 30% have error 60 during verification after flashing. Client think that the reason of error 60 is incorrect identification.

0 artem dmitriev5 over 6 years ago in reply to artem dmitriev5

Intellectual 330 points

Can anybody help me?

0 Lukas Badura over 6 years ago in reply to artem dmitriev5

TI__Expert 4695 points

You will be contacted with email by the customer support team soon.

Best regards

0 artem dmitriev5 over 6 years ago in reply to Lukas Badura

Intellectual 330 points

Unfortunately i didn't get the answer yet.

0 Lukas Badura over 6 years ago in reply to artem dmitriev5

TI__Expert 4695 points

This should happen today or tomorrow.

Lukas

0 zrno soli over 6 years ago in reply to artem dmitriev5

Guru 33653 points

artem dmitriev5 said:
1500 units. The client says that all MCUs are defined as MSP430F2618. But 30% have error 60 during verification after flashing. Client think that the reason of error 60 is incorrect identification.

Yes, the main job for user is to decrypt unknown error by itself, because it is too hard for TI (software) to give clear and detailed error description.

0 Matt Calvo over 6 years ago

TI__Genius 13670 points

Hello,

Could you please confirm that the customer support team has reached out and is working with you to support this issue. If so then we can close out this thread, thank you for your cooperation with this process!

Best regards,

Matt Calvo

0 artem dmitriev5 over 6 years ago in reply to Matt Calvo

Intellectual 330 points

Hello!

Yes, you can close this thread.

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP430F2617: MSP430F2617 verification error while flashing