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

MSP430F5340: Programming a *.out file without project?

Andy Delle
Prodigy 190 points
Part Number: MSP430F5340
Other Parts Discussed in Thread: MSP-FET, UNIFLASH

Tool/software:

Our assembly line has free CCS on their computers. But I do not want source code and/or full CCS project sets outside of the engineering group.

Is there a way to program a device with a .out file without having the full project?

Can a mock project be made then overwrite the mock .out file with the file we want?

Please do not suggest the Elprotronic burner software. They are a horrible company based on our experience. They never answer tech support questions and you can't call them. They have an app that does what we need but I'm not going to pay for unsupported software.

Also if we buy the MSP-FET programmer from an authorized TI vendor, why can't we get the Elprotronic burner software free?

You can't fool us engineers!  It's quite obvious Elprotronic makes the MSP-FET for TI

From Digikey

  • 0
    Guru 24385 points

    Have you tried mspdebug or MSPFlasher?

  • 0
    TI__Mastermind 46155 points

    Hi,

    You can use UNI-FLASH. It is free provided by TI.

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 190 points

    Well I tried Uniflash and it doesn't work. 

    I loaded the .out file as the flash image. Is this right?

  • 0 in reply to Andy Delle
    Prodigy 190 points

    OK, I made a .hex file, which UniFlash is said to accept and I get this. 

    ClearClose
    [3/10/2025, 12:23:53 PM] [ERROR] MSP430: File Loader: Verification failed: Internal error while writing 0x00200

    Note I can successfully program within the CCS IDE project so the code is good.

  • 0 in reply to Andy Delle
    TI__Mastermind 46155 points

    Hi,

    The address 0x00200 does not belong to Main code address. You need to write your code start from 0x4400h. Try add address setting in Uniflash as below.

    Best  regards,

    Cash Hao

  • 0 in reply to Andy Delle
    Prodigy 190 points
    NOTE: I'm using CCS V12.0.0.00009

    Issue is deeper. The original project is from 2012 but works fine using when programming from CCS V12

    But this original project does not have the HEX option in the project properties. 
    So I made a new project and copied the SRC folder to the new project, and now I have the HEX option in Project Properties
    But if I try to run this from CCS I get the same 0x00200 error in CCS?
  • 0 in reply to Andy Delle
    Guru 24385 points

    Since CCS uses the Unix .elf format the GNU bintools can translate that into something else. msp430-elf-objcopy can convert it to hex, S-records, binary, etc.

  • 0 in reply to David Schultz
    Prodigy 190 points

    That doesn't answer my question Why do I get this 0x00200 error when I try to program through CCS with an .out file when I made a new project and copied the SRC file into it. The project file from 2012 compiles and programs fine through CCS.

    Also why does the project file from 2012 not have the HEX linker option in project / properties when I'm running V12? Is this a legacy issue?

    Again the goal here is to be able to program a CCS project output without exposing the SRC folder. This can't be that unusual. Not too many companies release source code to an assembly production environment.

  • 0 in reply to Andy Delle
    TI__Mastermind 46155 points

    Hi, 

    The 0x200 error could related to MCU configuration data changed during the compiler updates. 

    So, now try to solve your issue. SO, it does not have this 'MSP430 Hex Utility' in your origin project?

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 190 points

    If I load the 2012 CCS project, the HEX option does not appear in the Project/Properties menu you showed in your last post.

    If I build a new project and copy the SRC folder from the 2012 project to the new project, I do get the HEX option in Project/Properties.

    But now I get the 00200 error when I try to compile the new project.
    The 0x00200 error is the problem.
    The 2012 project will compile and generate a good .out fine in the Release folder and the MSP-430 programmer can program the chip.
    But I need to be able to program with UniFlash 9.1.0 and the 2012 project is rejected by UniFlash, I assume due to version compatibility.
    Is there a better way to  update a project to my current version than just making a new project and copying the SRC file into it?
    The ultimate goal here is that I need the production people to be able to program boards with UniFlash and not CCS. We don't want source code distributed outside of the engineering department.
  • +1 in reply to Andy Delle
    TI__Mastermind 46155 points

    Hi,

    Andy Delle said:
    If I build a new project and copy the SRC folder from the 2012 project to the new project, I do get the HEX option in Project/Properties

    When you build this new project, could you generate .txt file as the output file of the project. Then you can send the .txt file here. I can take a look into it. And see if it can solve the 0x200 issue over the .txt file. 

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Prodigy 190 points

    Yes, we need to find out what is causing the 0x00200 error.

  • 0 in reply to Andy Delle
    Guru 24385 points

    Not really sure which error you are talking about now. The one when programming or when compiling. Although I think that they are related.

    I don't know about the linker used in CCS but the GNU linker will put things it can't match to a named section in the linker script into the first spot it finds. If that is happening here, then the root of the problem is the linker script. Or the lack of one. Hard to say without more details than "0x200 error".

**Attention** This is a public forum