Click on the picture to enlarge. Pricing Ordering Related Items Downloads FAQs Feedback

Our $99 SBSIM430 MSP430 software development tools, consisting of an assembler, a linker, and a simulator, are a low-cost way to begin MSP430 development. It features: An Assembler A Linker A Simulator

License Agreement - read before placing order.

SBSIM430 Demo v. 1.0.3 - released 10 June 2002 and limited to 512 bytes of code.

Q1: What object format is used by your tools?
A1: This system uses the popular COFF format.

Q2: Your tools sound as easy to use as the original TI tools. But, those tools didn't allow long file names, and made the project locations absolute. What about yours?
A2: This development system allows long file names and non-fixed project locations, which is required if you need to move projects between locations, such as telecommuting. However, section names are still limited to eight characters, which is a feature of the COFF format.

Q3: What programmers are supported from within the environment?
A3: We currently do not launch programmers from within the environment, although the tool is stubbed for that in an upcoming release. The first two programmers we will support will be the PRGS430 and the BLMSPF. The next two will be two new MSP430 programmers we are currently designing.

Q4: Why are the assembler, linker, and editor options disabled within the tools menu?
A4: Our original intent here was to ship one assembler, linker, and editor for the demo version, and another for the licensed version. However, we changed our architecture to ship only one version of these, and then unlock them all with the same key. We left the menu there to support multiple assemblers for future TI processors, but for now it is a do-nothing since the "do" is already done elsewhere. Sorry for the confusion.

Q5: I want to be able to use [your favorite editor]. How can I do builds with your linker and assembler?
A5: The User's Guide documents all command-line parameters needed to build from within another environment. Please make sure you also provide the security key parameter.

Q6: Why doesn't the editor support [your favorite editor feature] as found in [your favorite editor]?
A6: Wow, if we tried to compete with [your favorite editor] you wouldn't get it for [what we charge]! But seriously, our editor is intended to give you an editor so you can get started with the MSP430 quickly and inexpensively. Power users will want to integrate the build tools from within their favorite editor.

Q7: Why doesn't the software support emulation like [some other tool]?
A7: We wanted to give MSP430 users a low-cost, low-risk path into the MSP430. To do that, we focused on the features really needed to get started. The main benefit of the MSP430, low power, can be best realized by having small, tight code blocks executed rarely, with the processor in sleep mode most of the time. To reach this goal, it is important that the user get in touch with the way the MSP430 uses registers and other resources. We have found that simulating the CPU in assembly is more effective for grasping the essential concepts. Once you see how to write fast code with the MSP430, the lightbulb goes on and emulation becomes far less important. This is why we focused on the simulator first. This isn't to say that providing an emulator is out of the question, it has just been a low-priority.

As SoftBaugh continues efforts to increase features, along with ease of use, we find and consider feedback and suggestions essential to creating a better product for the customer.

Please note that if your intent is to receive technical support, or you if have general questions regarding this item, it is best to contact SoftBaugh directly, by phone or e-mail.

Feedback Form