• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 625 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.

MSPM0L1306: Production burning problem

Rhea Gao
Expert 2580 points
Part Number: MSPM0L1306
Other Parts Discussed in Thread: SEGGER,

Hi,

The customer failed to produce a burn using L1306.

Customers used earlier, there are two kinds of materials, one is X, the other is M.

When the chip program is burned, the PCBA program beginning with X can be burned successfully, and the PCBA program beginning with M cannot be burned successfully; We also use Jflish to burn directly, the PCBA at the beginning of X was successfully burned, and the burning error at the beginning of M was unsuccessful. The burning error message is as follows:

The JFlash burner was used, version model SEGGER J-Flash V7.86.

What changes have been made to the final qualified production devices? What is the reason for the unsuccessful burning? How to solve this problem? Please take a look.

Thank you!

  • 0
    TI__Genius 10611 points

    Hi Rhea,

    The first one is sample and the second one is RTMed. The only difference between two kinds of MCU is the temperature range.

    Please try another one of MSPM0L1306TRGER

  • 0 in reply to Zoey Wei
    Expert 2580 points

    Hi Zoey,

    The previous feedback can not burn the problem has been solved, the customer downloaded the new version of the burning software V7.94h can burn successfully.

    But a new problem arose:

    After burning the program, after a few seconds of running on the power, the code seems to run away, and the tracking can not locate where it ran, and the host will restart;

    The customer has verified: using the same board, the same burning file, XMSM0L1306 has never appeared this phenomenon, everything is normal;

    Change XMSM0L1306 to MSPM0L1306, the above phenomenon occurs; The 6pcs tested simultaneously all had the same problem.

    Please help to analyze what causes it? Do X chips and M chips need to be changed in code?

    Any suggestions on how to solve it?

    Thanks~

  • 0 in reply to Rhea Gao
    TI__Genius 10611 points

    Hi Rhea,

    Please check if the memory of both(Sample and RTMed) is the same after programmed.

    Let's send the detailed information through e-mail, and I will close this thread.

    B.R.

    Zoey

  • 0 in reply to Zoey Wei
    Expert 2580 points

    Hi Zoey,

    It's zoey_wei@ti.com, right?

  • 0 in reply to Rhea Gao
    TI__Genius 10611 points

    zoey-wei@ti.com