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

Error downloading .txt or .r43 file to target in the Release mode

Doug Balkman
Prodigy 40 points
Other Parts Discussed in Thread: MSP430G2210, MSP-FET

I am using IAR Embedded Workbench for Texas Instruments MSP430, 8K KickStart Edition 6.3.

The code is 100% assembler for an MSP430G2210.

 

I can successfully download the Debug output file (.d43) to the target. The code runs well.

I am not able to download either Release output file (.r43 or .txt) to the target.

Below are the logs for the two cases.

 

When downloading Debug version to target:

 

Mon Aug 17, 2015 14:42:39: Using license: Standalone license - IAR Embedded Workbench for Texas Instruments MSP430, 8K KickStart Edition 6.30

Mon Aug 17, 2015 14:42:40: Firmware version 3.5.0.1

Mon Aug 17, 2015 14:42:40: Interface dll version 3.5.0.1

Mon Aug 17, 2015 14:42:41: Device : F20x1_G2x0x_G2x1x

Mon Aug 17, 2015 14:42:41: External voltage : 0.0 V

Mon Aug 17, 2015 14:42:41: VCC voltage : 3.3 V

Mon Aug 17, 2015 14:42:44: Verify download : no errors found

Mon Aug 17, 2015 14:42:44: Download completed and verification successful.

Mon Aug 17, 2015 14:42:44: Loaded debugee: C:\Program Files\IAR Systems\Embedded Workbench 7.2\Projects\Wifi_Camera\Debug\Exe\Wifi_Camera.d43

Mon Aug 17, 2015 14:42:45: Target reset

Mon Aug 17, 2015 14:42:45: No state storage buffer implemented on connected device : (EEMSetVariableWatch)

 

 

 

When downloading Release version to target:

 

Mon Aug 17, 2015 14:41:06: Using license: Standalone license - IAR Embedded Workbench for Texas Instruments MSP430, 8K KickStart Edition 6.30

Mon Aug 17, 2015 14:41:07: Firmware version 3.5.0.1

Mon Aug 17, 2015 14:41:07: Interface dll version 3.5.0.1

Mon Aug 17, 2015 14:41:08: Device : F20x1_G2x0x_G2x1x

Mon Aug 17, 2015 14:41:08: External voltage : 0.0 V

Mon Aug 17, 2015 14:41:08: VCC voltage : 3.3 V

Mon Aug 17, 2015 14:41:08: Failed to load flash loader: C:\Program Files\IAR Systems\Embedded Workbench 7.2\Projects\Wifi_Camera\Release\Exe\Wifi_Camera.txt

Mon Aug 17, 2015 14:41:08: No state storage buffer implemented on connected device : (EEMSetVariableWatch)

 

 

Does the free KickStart version not allow a Release version to be downloaded?

 

Also, all of the selections under Emulator are greyed out so I am not able to 'blow the fuse'.

 

Thanks for your assistance.

Doug

  • 0
    TI__Prodigy 560 points
    Doug,

    The IAR for MSP430 User's Guide (www.ti.com/.../slau138aj.pdf) states on page 42:

    ' The linker output format must be "Debug information for C-SPY" (.d43) for use with C-SPY. CSPY
    does not start otherwise, and an error message is output. C-SPY cannot input a .TXT file. '

    Hopefully this clears things up!

    Regards,
    Martin
  • 0 in reply to Martin Prado
    Prodigy 40 points

    Thank you for the response, Martin. My understanding is that C-Spy is for debugging. Now that I have finished debugging, I want to produce the Release build. This generates a .txt and .r43 output file. Once I have these, I want to download these into the target using MSP-FET. I am not able to do that using the Kickstart environment. It results in the errors that I reported in my first message. Can you tell me why?

    Also, in the Release mode, all of the selections under 'Emulator' are greyed out so I am not able to select any functions especially 'blow the fuse'. Can you tell me why that is, also?

    Thank you.

    Doug

  • 0 in reply to Doug Balkman
    Guru 58965 points
    I am puzzled by this for a long time but never bothered to ask.

    It sounds like the firmware developer needs to produce two different object codes from the same source code. One object code is for "release" while the other is for "debug". The one for release needs not be debugged. And the one debugged needs not be released.

    I wonder if accountants keep two sets of books like this.
  • 0 in reply to old_cow_yellow
    Prodigy 40 points

    I recently read that the release version of the code is more efficient space-wise. I believe the debug code may contain 'hooks' to allow use with C-Spy during debugging. When you do a release build, the 'hooks' are removed, resulting in a smaller object code.

    I found a stand-alone product called FET-PRO430 that allows an MSP430 device to be programmed using an MSP-FET probe.

  • 0 in reply to Doug Balkman
    TI__Prodigy 560 points
    Doug,

    This wiki page should be of much more use than the last link! Using the Fet-PRO430 tool that you found will allow you to download the binary files.

    processors.wiki.ti.com/.../Generating_and_Loading_MSP430_Binary_Files

    Am waiting on a response to see if we can answer the two specific questions regarding the error messages and greyed out selections.

    Regards,
    Martin

**Attention** This is a public forum