[Tinyos-help] Debugging Tmotes using JTAG with Boomerang on WinXP

[Christian Behrens]

Hi all, 

I have been facing severe trouble trying to use the JTAG interface for
debugging my Tmotes. I am using Boomerang on WinXP. I have built my own jtag
adaptor from reading in TI's app notes and datasheets. It seems to work as I
can successfully read out the device type of the Tmote. I use a TI USB-FET
device for debugging. I also tried with a parallel port debugger but I face
the same problems. It seems like being a software issue. 

Here is what I did to debug a programme. 

1. I have downloaded the new Files (HIL.dll, MSP430.dll,
msp430-gdbproxy.exe) from www.soft-switch.com. I have copied them into
/opt/msp430/bin. 
   Furthermore, I have installed the mspgcc to get a new version of the
msp430-gdb.exe. 

   When I run the msp430-gdbproxy (using $ msp430-gdbproxy --port=3333
msp430 TIUSB) it seems to work out (at least it shows the right device).

---------
Remote proxy for GDB, v0.7.1, Copyright (C) 1999 Quality Quorum Inc.
MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood

GDBproxy comes with ABSOLUTELY NO WARRANTY; for details
use `--warranty' option. This is Open Source software. You are
welcome to redistribute it under certain conditions. Use the
'--copying' option for details.

debug: MSP430_Initialize()
debug: MSP430_Configure()
debug: MSP430_VCC(3000)
debug: MSP430_Identify()
info:      msp430: Target device is a 'MSP430F1611' (type 42)
debug: MSP430_Configure()
notice:    msp430-gdbproxy.exe: waiting on TCP port 3333
---------

2. In a new window I compiled an App (e.g. blink) using make tmote (telosb)
debug. This should generate the necessary debug info. 
   Then I change the directory to /built/tmote and try to use the
msp430-gdb, but I may not use any commands in the gdb. (e.g. monitor erase,
load main.exe)

-----------
$ msp430-gdb main.exe
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-cygwin --target=msp430"...
(gdb) monitor erase
"monitor" command not supported by this target.

(gdb) load main.exe
You can't do that when your target is `exec'
(gdb)
-----------

   I also tried by putting the debug switch into the makefile but the result
is the same. 
   Do I have to first connect to the gdbproxy using "target cisco
[host]:[port]"? I tried to, but I seems to be freezing (or at least terribly
slow)!

3. I got the tip from another user to update the USB-FET. But I even failed
to run the self-test. 

------
$ msp430-gdbproxy msp430 --selftest-usb-fet

Remote proxy for GDB, v0.7.1, Copyright (C) 1999 Quality Quorum Inc.
MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood

GDBproxy comes with ABSOLUTELY NO WARRANTY; for details
use `--warranty' option. This is Open Source software. You are
welcome to redistribute it under certain conditions. Use the
'--copying' option for details.

notice:    msp430: TI USB FET self-test requested
debug: MSP430_Initialize()
debug: MSP430_FET_SelfTest()
error:     msp430: Hardware Self Test Error (40)
debug: MSP430_Initialize()
debug: MSP430_Configure()
debug: MSP430_VCC(3000)
debug: MSP430_Identify()
error:     msp430: Could not find device (or device not supported) (4)
debug: MSP430_VCC(0)
debug: MSP430_VCC(3000)
debug: MSP430_Reset(ALL_RESETS)
debug: MSP430_Close()
Assertion failed: !msp430_status.is_open, file target_msp430.c, line 745

This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.
-------------

Another thing is when I try to source the gdb.ini I get back the following:

--------
$ source gdb.ini
bash: target: command not found
--------

I have also seen that there is a walkthrough for JTAG debugging for a linux
installation of TinyOS. 
But the points given there do not address my problem. 

Maybe someone can help me with this problem. Any help is appreciated. 


Thanks. 


Christian