Key facts
- Brand
- TI
- Model
- MSP430
- Category
- microcontrollers
- Industry
- Electronics
- Documents
- 2
- Languages
- ZH · EN
- Last added
- 2026-11-11
Start here

TI MSP430 IEC60730 Software Package User's Guide
This guide describes the Texas Instruments MSP430 IEC60730 software package, which provides system tests for IEC 60730-1:2010 requirements up to Class B products. It covers example projects, power-on and periodic self-tests, and integration of those tests into an application design.
The document also explains how to generate CRC-CCITT checksums, start new projects in Code Composer Studio or IAR, run ADC, CPU register, clock, memory, GPIO, and program counter tests, and use the configuration tool to generate customized header files.
TI MSP430 specifications
| Supported tool chains | Texas Instruments Code Composer Studio v5.3 or later; IAR Embedded Workbench v5.51.3 or later |
|---|---|
| Default main clock frequency | 12 MHz |
| Default percent frequency drift | +/-3% |
| Default RAM test | March X algorithm in non-destructive mode |
| Default stack size | 80 Bytes |
| Default ADC count drift limits | -50 and 50 |
| CRC checksum location for MSP430G2553 | Information memory (0x1004) |
| CRC checksum location for MSP430F5529 | Beginning of Info D section (0x1800) |
| CRC checksum location for MSP430FR5739 | Beginning of Info A section (0x1880) |
All TI MSP430 documents by type
Day-to-day operation, settings and troubleshooting. Start here if the product is already set up.
Questions answered in these manuals
How do I prepare the example folder for the FRAM UART demo?
Copy the BSL-Scripter.exe file into the example folder and place your .txt image file there.
What must be changed in the script file for UART or I2C communication?
You must change the COM port number based on your device in the specific script file.
Which IEC 60730 software class does this package support?
The package provides system tests required by IEC 60730-1:2010 for up to Class B products.
How do the example projects report test results?
They toggle the FAILURE pin a number of times to indicate which test failed, and the SUCCESS pin remains set if none of the tests failed.
