• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 78 subscribers
  • Views 207 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430F1612: MSP430F1612

Mias Visser
Prodigy 10 points
Part Number: MSP430F1612

Hi we have been using this processor for a years now, and never came across this.

Is there anyone that can help us solve this. When we program the unit the working devices writes the following when the chip is read:

 

 

=== Information Memory Segments  0x1000 - 0x10FF ======

 

 

0x1000: 01 00 10 00 01 00 01 03   03 00 0A 04 02 00 00 00 | ................

0x1010: 00 00 00 00 00 00 00 00   00 00 00 00 00 00 00 00 | ................

0x1020: 00 00 00 00 00 00 00 00   00 00 00 00 00 00 00 00 | ................

0x1030: 00 00 00 FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1040: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1050: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1060: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1070: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1080: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1090: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10A0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10B0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10C0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10D0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10E0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10F0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

 

But then about 10% of the processors give us the following when read back and

Give strange characters on the boot screen and changes some of our settings.

 

=== Information Memory Segments  0x1000 - 0x10FF ======

 

 

0x1000: 21 80 6A D8 81 40 01 A2   0A 62 3B CE 22 00 88 8B | !.j..@...b;."...

0x1010: A2 0F A3 C3 90 C1 88 E3   82 CB 91 E9 90 A9 22 EB | ..............".

0x1020: 82 E2 89 C9 C0 C9 13 C9   A0 81 83 ED 48 09 AB E8 | ............H...

0x1030: 00 E0 82 FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1040: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1050: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1060: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1070: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1080: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x1090: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10A0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10B0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10C0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10D0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10E0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

0x10F0: FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF | ................

We have done the following:

  1. When we replace the processor, this error is fixed.
  2. When we take a working device and create a hex from a working device it works and fixes the faulty one

 

Do you have any advice in pointing us in the correct direction, can this be old processors as this part has become absolute and we are struggling to find them, maybe we were sold old stock.

 

How does the marking work on the Processor? We currently have two different one’s under investigation. 9BC43LTG4 – M430F1612 – REV B ---- 31AT3VTG4 – M430F1612 – REV B

  • 0
    TI__Mastermind 38300 points

    Can you give more explain about "When we take a working device and create a hex from a working device it works and fixes the faulty one"?

    Do you mean you read the code from the good device and download it into faulty one. Then the data written into information memory turns right?

  • 0 in reply to Eason Zhou
    Prodigy 10 points

    Yes we read the code save it as Hex (Original file is a .d43, using FET Pro430 from Elprotronic) then the data written is correct and working.

  • 0 in reply to Mias Visser
    TI__Mastermind 38300 points

    I would suggest you to make a compare for the code read from good device and back device.

    Maybe the code downloaded into the bad device is wrong.

  • 0 in reply to Eason Zhou
    Prodigy 10 points

    Hi Eason I want to thank you for the replies and time. We use the same .d43 file to program all the devices 16 out of 100 is bad today, and the only diffrences is the first x3 lines on the bad devices it writes random code only on on the first x3 lines. The rest is all the same.

    Good device

    0x1000: 01 00 10 00 01 00 01 03   03 00 0A 04 02 00 00 00 | ................

    0x1010: 00 00 00 00 00 00 00 00   00 00 00 00 00 00 00 00 | ................

    0x1020: 00 00 00 00 00 00 00 00   00 00 00 00 00 00 00 00 | ................

    Bad device

    0x1000: 21 80 6A D8 81 40 01 A2   0A 62 3B CE 22 00 88 8B | !.j..@...b;."...

    0x1010: A2 0F A3 C3 90 C1 88 E3   82 CB 91 E9 90 A9 22 EB | ..............".

    0x1020: 82 E2 89 C9 C0 C9 13 C9   A0 81 83 ED 48 09 AB E8 | ............H...

    Working Device the Orange is the only diffrence between other working devices

    Bad device and diffrences in orange from the working devices and this is the only diffrences in the code.

  • 0 in reply to Mias Visser
    TI__Mastermind 38300 points

    1. I think this part is information memory. Is these changed memory belong to code or data?

    2. Is this part of memory of all the bad devices same?

    3. Will the device write this part of flash after production by itself? Or do the code include the flash writing of this part of memory?

**Attention** This is a public forum