Hello, I wrote a firmware for FET430UIF and eZ430U for my self training.
http://homepage.mac.com/skimu/msp430/dfw/ Below is a part of README file. -- Shigenobu Kimura ;;; ;;; D/FW -- Debug Firmware for MSP-FET430UIF/eZ430U ;;; ;;; [email protected], February 2010 ;;; ----------- Introduction ---------------------------------------- This is an open source, experimental, and unofficial firmware for MSP-FET430UIF/eZ430U debug interface and associated host side control programs. ------------ Combinations known to work ------------------------- Host : MacOSX (Darwin 10.2.0) FET Device TAP Target Board FET430UIF F169 JTAG MSP-TS430PM64 FET430UIF F2274 JTAG MSP-TS430DA38 FET430UIF F2274 SBW MSP-TS430DA38 FET430UIF F2274 SBW RF2500T FET430UIF F1612 JTAG eZ430U(Rev2.0) eZ430U F2274 SBW RF2500T MSP430X (4xx/5xx) support code included but not tested and it is unlikely to work as is. ----------- Requirements ---------------------------------------- 1) FET430UIF or eZ430U (target FET), which you don't miss much if it get broken. (See below for notes on eZ430-F2013) 2) 4 wire JTAG programmer to write DFW into your FET. (mother FET). DFW has ability to upgrade itself from USB port, you only need mother programmer just for the first time. 3) Mac running MacOSX (host computer) (See libusbcom/usbcom_libusbc.c about libusb support for other Unix variants.) 4) MSPGCC toolchain on your host computer. See below for tips on MSPGCC installation on MacOSX. 5) No USB device with vendor/product ID of 0x451/0xbeef. These are the ones DFW is using. There are not yet easy way to change these IDs. See below how to change USB IDs. ------------ Known bugs (less priority To-Do's) ----------------- 1) Reconnecting target device's JTAG/SBW is unstable. (It is OK for the first time after power on.) Need unplug and re-plug USB to work around. 2) Error recovery is missing. 3) breakpoints does not work. I could not find any useful documentation about f16x's break-point registers, nor f2xxx's EEM feature... 4) backtrace does not work with GDB-6.8 (7.0 is OK). 5) cannot get local variables correctly (especially for binaries compiled with -O0 option). 6) Requires special USB software for host. -> Need to write generic communication class firmware for TUSB3410. 7) support target serial port at TUSB3410 on eZ430, for independent communications host<->FET and host<->target. (this requires software serdes on TUSB3410, I think) 8) TUSB3410's autoexec firmware does not work. (disabled by default)
