Hi
Is msp430-gdbproxy.exe dynamically linked to HIL.dll? I
am trying to run msp430-gdbproxy over D2xx Direct Driver
(http://www.ftdichip.com/Drivers/D2XX.htm). To do this I am
using a modified version of HIL.dll. With the modified
HIL.dll I am able to program msp430 via msp430-jtag. But
when I try to run msp430-gdbproxy --port=2000 msp430 I get
error: msp430: Unknown device (5)
error: msp430: Could not find device (or device not supported) (4)
My guess is the gdb-proxy is not able to find the device
because it is using statically linked HIL library rather
than HIL.dll. I also found that even when I delete HIL.dll
msp430-gdbproxy.exe's behavior is unchanged.
The chip in question is MSP430F1611.
I am using mspgcc-win32 20051026. Moreover
$ ./msp430-gdbproxy.exe --help msp430
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.
This is the MSP430 target. Usage:
msp430-gdbproxy.exe [options] msp430 [msp430-options]
[port]
Options:
--debug run msp430-gdbproxy.exe in debug mode
--help `msp430-gdbproxy.exe --help msp430'
prints this message
--port=PORT use the specified TCP port
MSP430-options:
--update-usb-fet update the firmware in a USB FET tool
(My query is for windows platform. On Linux I could see that
msp430-gdbproxy *is* dynamically linked to libHIL.so)
Thanks
Sumit
--
Nothing in the world can take the place of persistence.
Talent will not; nothing more common than unsuccessful men
with talent. Genius will not; unrewarded genius is almost a
proverb. Education will not; the world is full of educated
failures. Persistence and determination alone are
omnipotent.
Calvin Coolidge
