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.

MSP430F5152: MSP430F5152 gives Module Locked error while programming

Part Number: MSP430F5152
Other Parts Discussed in Thread: UNIFLASH, MSP-FET, MSP430F1121A

Dear All,

When I am programming MSP430F5152 with Uniflash tool it gives error of "module lock" but when I programmed it with Fet-pro430 it not gives any error and program in one shot only by Jtag Spy by 2 wire connection.

Why in uniflash "module lock" error comes while in Fet-Pro430 it not gives any error on same device MSP430F5152 with same debugger tool MSP-FET flashing Emulation Tool.

Which software tool is better for programming in production Uniflash or Fet-Pro430?

And I think Uniflash is of TI supported and not requires any license key but Fet-Pro430 is third party and reuire product key so Uniflash is better but it giving error as "Module Lock" while Fet-Pro430 not.

Please reply...

Regards,

Mahendra Rana

  • Hi Mahendra,

    which version of Uniflash you're using?
  • Some more questions

    1. which JTAG interface (4-wire or 2 wire) you are using with Uniflash
    2. can you post the exact error message because based on our knowledge the error "module lock" does not exist
  • Dear Dietmar,

    I am using JTAG 2 wire (Spy-Bi) with Uniflash
    And Sorry I forget to take screenshot when that error came but on Red error Pop up box text shown as "Module Locked" and when I tried with FET-Pro430 it successfully programmed and than I again tried it with Uniflash than it never gives error. And not able to generate same on same board now.

    So my question is Why in uniflash "module lock" error comes while in Fet-Pro430 it not gives any error on same device MSP430F5152 with same debugger tool MSP-FET flashing Emulation Tool?

    Which software tool is better for programming in production Uniflash or Fet-Pro430?

    Regards,
    Mahendra Rana
  • Dear Dietmar,

    Uniflash Version: 4.4.0.1922
    Fet-Pro430 Version: 3.3-1

    Regards,
    Mahendra Rana
  • Hi Mahendra,

    thanks for additional info if you get the chance to take a screenshot of the message it would help.
    If you use Spy-Bi-Wire I have to ask if you have considered the maximum capacitor on RST pin of max 2.2nF?]
    Looks like your UniFlash setup has problems with fresh (unprogrammed) parts right?

    I cannot say which tool is better because both should work reliable also both are based on the MSP debug stack.

    I tried it on my site with UniFlash version 4.5.0.2056 on a F5172 RevC part in a DA package with 4 wire and 2 wire JTAG.
    For both the auto detect feature worked fine.

    Best regards,
    Dietmar
  • Hi Dietmar,

    No, it is not with fresh (unprogrammed) parts. Error comes with already programmed part.

    Rst pin capacitor is also of 2.2nF and jtag cable length also less than 6 inch.

    And yesterday I got same error message while programming device MSP430F1121A (4wire Jtag) with uniflash and than I tried with FET-Pro430 so by that Fet-Pro430 it not gave any error and programmed successfully in one shot and than same device I tried with Uniflash than it also not gave any error.

    Regards,

    Mahendra Rana

  • Hi Rana,

    I saw you other post as well. I have no idea why programming the part with FET-Pro makes a difference and I have not seen this error message so far but I will forward this to our expert for help.

    I did not found the info which MSP-FET you are using can you please post a picture of it?

  • Hi Mahendra,

    I discussed with our expert and here is also not clear why you get this failure however it most likely comes from the GUI.
    You said it is reproducible, so you please generate the “GUI Log” and “Debug Server Log” in UniFlash. Both of these can be enabled from the “Settings” menu (top right menu). Please provide the logs for review. Thanks!
  • Hi Mahendra,

    in case your problem is not resolved can syou please provide the debug server and GUI logs as requested above?
    Otherwise it woudl be great if you can mark this thread as resolved.

    In case there will be no response I will close thie thread by end of this week.

**Attention** This is a public forum