• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 78 subscribers
  • Views 917 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.

MSP430.DLL V3 firmware reduces number of breakpoints for MSP430F2274 in IAR

Stefan Wolpert
Prodigy 70 points
Other Parts Discussed in Thread: MSP430F2274

When debugging the MSP430F2274 via IAR Embedded Workbench with a MSP-FET430UIF, the V3 driver only allows one (1) hardware breakpoint, instead of previously two (2) breakpoints with the V2 driver.

Is the reduced number of breakpoints a bug in the V3 DLL? Or does the V3 firmware on the MSP-FET430UIF somehow not allow more than one hardware breakpoint on the MSP430F2274?

I've looked through the MSP Debug Stack page and as well as querying search engines and E2E, and I haven't come across anything so far. Thanks!

  • 0
    Prodigy 70 points

    Solved - a good case of "read the [entire] manual"!

    While debugging, Emulator > Breakpoint usage... brings up a handy dialog box of actual breakpoints in use that may or may not be listed in the typical Breakpoints window. Without any breakpoints enabled in the Breakpoints window, was the following:

    Now, how do I get my breakpoint back?!?

     

    The pertinent part of IAR help "Breakpoint Consumers" topic (in the index under breakpoints, consumers of):
     

    The solution is the following:
    In Project > Options > Linker > Output (tab) > Format (section), unselect the With runtime control modules option.

    Unselecting With I/O emulation modules did not work as the help document suggested, however unselecting the parent category of With runtime control modules as stated above cleared the Breakpoint Usage list and gave me back two breakpoints!

    Upon further review, this issue started when two things changed: upgrading IAR to the 6.5 and moving to the V3 of the MSP430.DLL. So I'm not positive what exactly caused my unchanged projects to enable or adhere to the C-SPY emulation options. I have a feeling the C-SPY I/O emulation enabled option may have been ignored during linking in my previous versions of IAR, as I wasn't using it, and I don't include <stdio.h> or have other C-SPY-specific options enabled.

  • 0 in reply to Stefan Wolpert
    Guru 227245 points

    Thanks for letting us know what you discovered - and in such a detailed way.
    It will surely help others with the same problem.

**Attention** This is a public forum