• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 80 subscribers
  • Views 5296 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.

MSP430F6736: MSP430: File Loader: Verification failed: Internal error while writing 0x04000

Hideaki Nambu
Mastermind 9165 points
Other Parts Discussed in Thread: MSP430F6736, UNIFLASH, MSP430F6733, MSP430WARE, MSP-FET

Hello,

MSP430F6736 on customer's PCB started to fail flash programming. Could you please advise the cause or anythings to try as observation or recovery operations ?



CCS debug button result msg:
MSP430: File Loader: Verification failed: Internal error while writing 0x04000
MSP430: GEL: File: <customer working directory>\aaaa.out: Load failed.

CCS uniflash program result msg:
[09:49:09] ERROR >> MSP430: File Loader: Verification failed: Internal error while writing 0x04000
[09:49:09] ERROR >> MSP430: GEL: File: <customer working directory>\bbbb.hex: Load failed.
[09:49:09] File: <customer working directory>\bbbb.hex: Load failed.
[09:49:09] Programs operation finished.




Remarks:

- The error address is 0x4000, we know it is the start addr of the flash.

- The customer project is set to program flash partially.
    - Customer's latest CMD file is modified to program flash partially. Please request it if needed.
    - The erase option is "Erase and download necessary segments only (Differential Download)".

- It is not clear what operation was wrong or triggered this issue.

-  An analysis trial, "Load program" with a proven good project has failed:
    - A proven good, a default MSP430F6733.ccmxl, right click, Launch selected configuration.
    - The CPU core, right click, Connect target.
    - Open the memory browser, dump 0x4000 >>>>>>>> Result: The address was filled by 0xFFFF.
    - Run >> Load >> Load Program >> A proven good *.out file  >>>>>>>> Again "Verification failed: Internal error while writing 0x04000"


  • 0
    TI__Genius 15370 points

    Hi Hideaki, 

    Even though you've tried programming with a proven good file, could you try programming with the standard blinky found in MSP430Ware and let me know the results?

    The main things we need to check hardware-wise are the JTAG and power connections. If you could provide a schematic with these visible that would be helpful. More specifically, how are the AUX power connections setup?

     Best regards, 

    Caleb Overbay

  • 0 in reply to Caleb Overbay
    Mastermind 9165 points

    Caleb,

    Thank you for your reply.


    - - -
    > could you try programming with the standard blinky found in MSP430Ware and let me know the results?

    This case, one more line was displayed.

    MSP430: Trouble Writing Memory Block at 0x4000 on Page 0 of Length 0x20: Could not erase device memory
    MSP430: File Loader: Verification failed: Target failed to write 0x04000
    MSP430: GEL: File: <user directory>\Debug\test.out: Load failed.

    - - -
    > More specifically, how are the AUX power connections setup?

    My customer observed the AUXVCC-{1:3} by oscilloscope but none of drops/dips were found.


    - - -
    > The main things we need to check hardware-wise are the JTAG and power connections. If you could provide a schematic with these visible that would be helpful.

    Now I hesitate to request JTAG and Schem info. Please request again this is not helpful but mandatory now.

  • 0 in reply to Hideaki Nambu
    TI__Genius 15370 points

    Hi Hideaki, 

    The fact that the default blinky example didn't load correctly makes me suspicious of the hardware setup. 

    I think the next step is to see how JTAG, power supply, and the AUXVCC are connected schematically. The best way to assure these are correct is to view the schematic. The customer doesn't have to provide the entire schematic if they don't like but at least the portions listed above. 

    Best regards, 

    Caleb Overbay

  • 0 in reply to Caleb Overbay
    TI__Guru 56685 points
    Hello Hideaki,

    As Caleb has stated, without the simple Toggle P1.0 not loading correctly, Hardware would be the most likely culprit here. With this particular part there are two possible areas that could cause this issue.
    1. JTAG connections -- Was the recommended HW setup for JTAG followed according to the recommendations in datasheet/ MSP430 HW User Guide? http://www.ti.com/lit/slau278
    2. Power rail connections on this device. This includes how DVCC, AUXVCC1/2/3 are connected.

    We would need to see these connections in order to debug further. If you are not comfortable sharing schematics or partial schematics on this forum, please make a friend request to Caleb and send them via private message.
  • 0 in reply to Jace H
    Mastermind 9165 points

    Sirs, thank you for your replies.
    My customer is preparing schematic.

  • 0 in reply to Hideaki Nambu
    TI__Genius 15370 points
    Hi Hideaki,

    I haven't seen any schematics yet. Was your customer able to solve this issue?

    Best regards,
    Caleb Overbay
  • 0 in reply to Caleb Overbay
    Mastermind 9165 points

    I'm sorry, I will talk to my customer tomorrow . .

    (Edit on Dec-1: My customer is restarting to prepare their schem. I'm sorry for the opened thread here.)

  • 0 in reply to Hideaki Nambu
    TI__Genius 15370 points

    Hi Hideaki, 

    I've received the customers schematic and after review, everything looks good. I don't see anything schematically that could be causing the issues seen.

    Some follow up questions:

    1. What device revision is the customer using?
    2. What debugger are they using? 
      1. Is it up to date?

    One they've ensured they have the most up-to-date debugger try programming the default blinky code through CCS without using uniflash and let me know they results again. 

    Best regards, 

    Caleb Overbay

  • 0 in reply to Caleb Overbay
    Mastermind 9165 points

    Caleb,

    *

    > What device revision is the customer using?

    Two failing samples and both are Rev-A.

    > What debugger are they using?

    MSP-FETs. They have two units. Both works finely in daily use.

    > Is it up to date?

    Not sure .. CCS ver would work for you ?

    p.s.

    I heard that a different optimization levels were tried at the first fail. We will try some test about that. We made a sample IC order. I hope we could send a new report in this year.

  • 0 in reply to Hideaki Nambu
    TI__Genius 15370 points
    Hi Hideaki,

    CCS should check that the MSP-FET is up to date when you program with it. So you are most likely using the most recent SW revision. You can also check for CCS updates in CCS by going to Help --> Check for Updates.

    Do the parts being programmed have code on them already? Have you tried completely erasing the flash and rewriting it all instead of doing the partial programming? I want to rule out whether the issue is due to the partial programming.

    Also, thanks for sending over the log. If the above doesn't work, would your customer be willing to send over the CCS project for me to try programming a board myself?

    Best regards,
    Caleb Overbay
  • 0 in reply to Caleb Overbay
    Mastermind 9165 points
    Caleb, Jace,
    I appreciate your cooperation. My customer closed this issue. The cause was supposed to be PC issue.

**Attention** This is a public forum