• Locked Locked
  • Replies 4 replies
  • Subscribers 78 subscribers
  • Views 597 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.

Release hex created in IAR MSP430 does not work?

Bhushan Patil10
Prodigy 160 points
Other Parts Discussed in Thread: MSP430F5419A, MSP430F249

Hello ,

I am working on MSP430F5419A TI microcontroller and using IAR MSP430 6.30.3 IDE for my development.

During my development I encountered an issue. When I work with debug configuration application behaves as expected but when it is in release configuration, application goes for a toss.

Let me brief you about configuration,

IDE : IAR MSP4306.30.3

Target : MSP430F5419A

Runtime Library : Normal DLIB

Assembler Preprocessor : PIC=1 and ROPI =1 (ROPI enabled)

C/C++ Compiler Optimization : HIGH (BALANCED)

I created the release build configuration with reference to above configuration.

Could anyone help me to resolve this issue?

I guess the issue is with Optimization so I tried to make it Optimization Medium but an issue of release hex does not work still persist.

Please let me know if you any other details

Thanks,

Bhushan

  • Prodigy 160 points
    Hello

    A small correction microcontroller used is MSP430F249 instead of MSP430F5419A.

    Regards,
    Bhushan
  • Expert 2070 points

    There are several things that differ between the Debug and Release configurations.

    First, in the title you mentioned that it didn't work when you use "hex" (I take it as the output format of the linker). Does it work when you emit plain UBROF?

    Apart from that I would recommend you to try to make the settings as equal as possible between the Debug and Release configurations. If you walk through menu by menu, or (if you are adventurous) you can inspect the project files and see where the Debug and Release sections differs.

    I haven't got a complete list of things that differs. However, I know that the optimization levels and settings differs, as well as the Terminal IO settings.

        -- Anders Lindgren, IAR Systems

  • in reply to Anders Lindgren
    Prodigy 160 points
    Thanks Anders,

    Hex is the output file format. Created output file is Release.hex.
    As I mentioned I derived release configuration from debug configuration. Hence all configuration is same as debug except the output file format.

    Do you know any steps to debug the .hex file in find out where it gets stuck?

    Regards,
    Bhushan
  • in reply to Bhushan Patil10
    Expert 2070 points
    You should be able to debug it on the assembly level. Of course, it does not contain debug information, so you will not be able to step on the assembly level.

    Also, if possible, disable "ropi" as it makes the code much harder to read. (Just out of curiosity, why do you use it?)

    -- Anders Lindgren, IAR Systems

**Attention** This is a public forum