D/FW

Debug Firmware for MSP-FET430UIF/eZ430U

->Japanese

Introduction

D/FW is an open source, experimental, and unofficial firmware for MSP-FET430UIF and eZ430U debug interface and associated host side control programs. Host side programs are designed to work with any modern UNIX operating systems (e.g. Linux, *BSD).

• DFW(Debug firmware): Flash target device, interface to gdbproxy.
• PTFW(Pass-Through): A dedicated serial pass-through function for eZ430U.

News

5/7/2010(Version 0.19):

DFW for MSP430F2274 (RF2500T).

5/3/2010(Version 0.18):

A new firmware (PTFW) is added. This is a dedicated (no debug) serial port pass through firmware for eZ430u.

5/1/2010(Version 0.17):

It has been reported that dfw-0.17.tgz works on Linux as well.

Combinations known to work

Host

• MacOSX (Darwin 10.2.0) with Intel CPU.
• Gentoo Linux.

For hosts with big endian CPU, host side programs need a few changes.

FET

• FET430UIF
• eZ430U(Rev2.0), (See below notes for eZ430-F2013)
• MSP430F2274 + 3V serial interface (eg. eZ430U/PTFW)

Target

F2274/DFW can handle everything FET430UIF/DFW can, while eZ430U/DFW can only do SBW. To use F2274/DFW, you need 3V serial interface to connect host computer. You can use eZ430/PTFW for this purpose.

Demo

• Video
• Gallery
• example gdb session. (stack back trace)
• step execution on F2274 and on F5529.

Requirements

• FET430UIF or eZ430U (target FET), which you don't miss much if it get broken. (See README for notes on eZ430-F2013)
• 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.
• Host computer running UNIX operating system with USB modem support.
• MSPGCC toolchain.
• No USB device with vendor/product ID of 0x451/0xbeef. These are the ones DFW is using. See README how to change USB IDs.

Preparation

MSP-FET430UIF

JTAG connector for FET430UIF. VCCT(pin 7 of J6) is not connected for Rev1.3. Open FET430UIF's enclosure and plug this header to J6.

eZ430U

This page explains alternative way to attach JTAG. Step by step guide Bootstrapping D/FW on eZ430-RF2500

MSP430F2274(RF2500T)

Attach JTAG connector and a jumper for SBW. Pin assignments is in dfw/conf/f2274/uif_f2274.c. See Step5 of this page.

• dfw.fetuif.ihex, dfw.ez430u.ihex and dfw.ez430u1p1.ihex in dfw directory is pre-compiled binary (in Intel HEX format) for FET430UIF, eZ430U and eZ430U Rev1.1, respectively. Write one of these into your FET by a FET you currently have.
• DFW checks the content of EEPROM, and program it if necessary. It will take about 10 seconds before it gets ready after the first power on.
• edit Makefile in the distribution's top directory and correct your BFD library's location.
• make will make dmwt command and other utilities.
• examples/*/Makefile contains examples how to use dmwt.
• (cd gdbproxy; ./configure && make) will make gdbproxy.

Host command usage examples

dmwt : Dfw Memory WriTer

dmwt command will program target cpu via JTAG/SBW (or CC8051). This is also used to update FET's firmware.

Usage: dmwt [-vdf] [-p /dev/cu.usbmodemXXX] [-c TARGET_OPTIONS] 
            [-b name.txt from-addr] [object]

  ``object'' can be in either ELF, Intel HEX, or TITXT format.

  /dev/cu.usbmodemXXX might be /dev/ttyACMXXX or /dev/ttyXXX 

   $ dmwt                               # will print help message
   $ dmwt -f dfw.fetuif.elf             # update firmware
   $ dmwt -c TARGET_OPTIONS a.out
   $ dmwt -p /dev/cu.usbmodem001 -c "SBW" a.out
   $ dmwt -vc "SBW" a.out               # verbose mode

   $ dmwt -c ""  a.out                  # program a.out with JTAG.
   $ dmwt -c "SBW"  a.out               # program a.out with SBW.
   $ dmwt -c "VCC 3000 UNLOCKA" a.out   # sets VCC 3.0V, unlock INFO_A
   $ dmwt -c "CPUXV1" a.out                   
   $ dmwt -c "CPUXV2" a.out                   
   $ dmwt -c "CC8051" main.hex

gdbproxy

$ msp430-gdbproxy --help uifdfw
$ msp430-gdbproxy --port=2000 uifdfw --c TARGET_OPTIONS
$ msp430-gdbproxy --port=2000 uifdfw --c "CPUXV2" --debug

$ msp430-gdbproxy --port=2000 uifdfw --c "SBW"         # msp430/SBW
$ msp430-gdbproxy --port=2000 uifdfw --c "CPUXV1"      # CPUXV1/JTAG
$ msp430-gdbproxy --port=2000 uifdfw --c "CPUXV2 SBW"  # CPUXV2/SBW

set remoteaddresssize 64
set remotetimeout 999999
target remote localhost:2000

define reload
  monitor erase
  monitor flash
  load
  monitor memory
  set $pc = *0xfffe
end

TARGET_OPTIONS

   MSP430    : (default) msp430x1xx, msp430x2xx, msp430x4xx
   CPUXV1    :           msp430x2xx, msp430x4xx with CPUX
   CPUXV2    :           msp430x5xx, cc430x6xx 
   CC8051    :           cc111x, cc251x, etc.  

   VCC xxxx  : sets VCC to XXXX mV (e.g., VCC 3300), FET430UIF only.

   JTAG      : (default)
   SBW       :          

   FastFlash : (default)
   SlowFlash :   for relatively old devices without FastFlash feature
   LOCKA     : (default) locks INFO_A memory
   UNLOCKA   :           unlocks INFO_A memory

   FCTL addr : sets FCTL base address for CPUXV2 target.

   FWS  n    : sets flash word size for CC8051 target.

bufet : make backup files for target FET

Usage: bufet [-vd] [-p /dev/cu.usbmodemXXX] [-c TARGET_OPTIONS] 
             [fet_eeprom.txt fet_flash.txt]

• You need DFW equipped 4wire JTAG FET. eZ430U cannot be used for this purpose, since it supports SBW.
• Connect target FET430UIF or eZ430U to mother FET with JTAG cable, and provide power to target FET through USB cable.
• Connect mother to the host computer with USB cable.

$ ./bufet

$ mkdir FET_backup
$ cd FET_backup
$ ../bufet

To restore from backup file,

$ ../bufet fet_eeprom.txt fet_flash.txt

Source code

• github

skimu@mac.com