charper_99 wrote:
> For the moment this discussion pertains to windows only, once everything works there I will try this in Linux as well. I've seen references to using "msp430-gdbproxy msp430 TIUSB" to connect to TI's MSP-FET430UIF (ez430) tool. However, this isn't working for me.
>
> debug: MSP430_Initialize()
> error: msp430: Could not initialize device interface (1)
>
> I can get it working by finding the FET tool under the device manager and initializing it by initializing its com port i.e. "msp430-gdbproxy msp430 COM4".
>
> So - what am I missing with the TIUSB command? I could not find any documentation available on this argument and I'm not sure what I'm doing wrong.
>
>

I have not tried it with a 'com' port. Little voice, back of my head,
the wrong way to do it. Use a 'port' like:

--port=2000

Try:
C:\~your_path_to_mspgcc~\bin\msp430-gdbproxy.exe --port=2000 msp430 TIUSB

and see if the device is there. If so, then use the same port to connect the debugger.

But before, if you didn't hear the do-dit, do-dit, when you plugged the device in, something else...

Best, Dan.

------------------------------------



(You need to be a member of msp430 -- send a blank email to msp430-subscribe@yahoogroups.com )

--- In m...@yahoogroups.com, Dan Bloomquist wrote:
>
> charper_99 wrote:
> > For the moment this discussion pertains to windows only, once everything works there I will try this in Linux as well. I've seen references to using "msp430-gdbproxy msp430 TIUSB" to connect to TI's MSP-FET430UIF (ez430) tool. However, this isn't working for me.
> >
> > debug: MSP430_Initialize()
> > error: msp430: Could not initialize device interface (1)
> >
> > I can get it working by finding the FET tool under the device manager and initializing it by initializing its com port i.e. "msp430-gdbproxy msp430 COM4".
> >
> > So - what am I missing with the TIUSB command? I could not find any documentation available on this argument and I'm not sure what I'm doing wrong.
> >
> >
>
> I have not tried it with a 'com' port. Little voice, back of my head,
> the wrong way to do it. Use a 'port' like:
>
> --port=2000
>
> Try:
> C:\~your_path_to_mspgcc~\bin\msp430-gdbproxy.exe --port=2000 msp430 TIUSB
>
> and see if the device is there. If so, then use the same port to connect the debugger.
>
> But before, if you didn't hear the do-dit, do-dit, when you plugged the device in, something else...
>
> Best, Dan.
>
Thanks for the quick response. What I'm referring to about the com port: Windows will recognize the device as a com port adapter. Apparently the gdbproxy has access to that. Perhaps there's a driver I'm missing somewhere. I could not find a separate driver download, so I installed them from IAR's installer. The port command you refer to is supposedly optional, but I gave it a try anyway:

>msp430-gdbproxy --port=2000 msp430 TIUSB

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()
error: msp430: Could not initialize device interface (1)

Thanks again for the initial speedy response. Any other suggestions though?

------------------------------------



(You need to be a member of msp430 -- send a blank email to msp430-subscribe@yahoogroups.com )

charper_99 wrote:
> --- In m...@yahoogroups.com, Dan Bloomquist wrote:
>
>> charper_99 wrote:
>>
>>> For the moment this discussion pertains to windows only, once everything works there I will try this in Linux as well. I've seen references to using "msp430-gdbproxy msp430 TIUSB" to connect to TI's MSP-FET430UIF (ez430) tool. However, this isn't working for me.
>>>
>>> debug: MSP430_Initialize()
>>> error: msp430: Could not initialize device interface (1)
>>>
>>> I can get it working by finding the FET tool under the device manager and initializing it by initializing its com port i.e. "msp430-gdbproxy msp430 COM4".
>>>
>>> So - what am I missing with the TIUSB command? I could not find any documentation available on this argument and I'm not sure what I'm doing wrong.
>>>
>>>
>>>
>> I have not tried it with a 'com' port. Little voice, back of my head,
>> the wrong way to do it. Use a 'port' like:
>>
>> --port=2000
>>
>> Try:
>> C:\~your_path_to_mspgcc~\bin\msp430-gdbproxy.exe --port=2000 msp430 TIUSB
>>
>> and see if the device is there. If so, then use the same port to connect the debugger.
>>
>> But before, if you didn't hear the do-dit, do-dit, when you plugged the device in, something else...
>>
>> Best, Dan.
>>
>>
> Thanks for the quick response. What I'm referring to about the com port: Windows will recognize the device as a com port adapter. Apparently the gdbproxy has access to that. Perhaps there's a driver I'm missing somewhere. I could not find a separate driver download, so I installed them from IAR's installer. The port command you refer to is supposedly optional, but I gave it a try anyway:
>
>
>> msp430-gdbproxy --port=2000 msp430 TIUSB
>>
>
> 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()
> error: msp430: Could not initialize device interface (1)
>

Hi,
I checked, this is the message if the tool does not respond. If the tool
is good you get an 'unknown device' down the line if it is the device.
So, it sounds like a tool/driver problem.
Mine won't work with 'COM4', I get a 'device not found' error. But you
say you can get past the 'Could not initialize device interface' with COM4?

My driver is:11/1/2004, version: 1.2.11.3 and it works with both the ez
and the JTAG tools.
It shows up in the device manager on COM7 for me.

I wish I knew more. I installed the the software that came with the ez
on another computer years ago but I don't recall a problem, or did I
down load a newer driver? It was a long time ago.

Best, Dan.

------------------------------------



(You need to be a member of msp430 -- send a blank email to msp430-subscribe@yahoogroups.com )

--- In m...@yahoogroups.com, Dan Bloomquist wrote:
>
> charper_99 wrote:
> > --- In m...@yahoogroups.com, Dan Bloomquist wrote:
> >
> >> charper_99 wrote:
> >>
> >>> For the moment this discussion pertains to windows only, once everything works there I will try this in Linux as well. I've seen references to using "msp430-gdbproxy msp430 TIUSB" to connect to TI's MSP-FET430UIF (ez430) tool. However, this isn't working for me.
> >>>
> >>> debug: MSP430_Initialize()
> >>> error: msp430: Could not initialize device interface (1)
> >>>
> >>> I can get it working by finding the FET tool under the device manager and initializing it by initializing its com port i.e. "msp430-gdbproxy msp430 COM4".
> >>>
> >>> So - what am I missing with the TIUSB command? I could not find any documentation available on this argument and I'm not sure what I'm doing wrong.
> >>>
> >>>
> >>>
> >> I have not tried it with a 'com' port. Little voice, back of my head,
> >> the wrong way to do it. Use a 'port' like:
> >>
> >> --port=2000
> >>
> >> Try:
> >> C:\~your_path_to_mspgcc~\bin\msp430-gdbproxy.exe --port=2000 msp430 TIUSB
> >>
> >> and see if the device is there. If so, then use the same port to connect the debugger.
> >>
> >> But before, if you didn't hear the do-dit, do-dit, when you plugged the device in, something else...
> >>
> >> Best, Dan.
> >>
> >>
> >
> >
> > Thanks for the quick response. What I'm referring to about the com port: Windows will recognize the device as a com port adapter. Apparently the gdbproxy has access to that. Perhaps there's a driver I'm missing somewhere. I could not find a separate driver download, so I installed them from IAR's installer. The port command you refer to is supposedly optional, but I gave it a try anyway:
> >
> >
> >> msp430-gdbproxy --port=2000 msp430 TIUSB
> >>
> >
> > 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()
> > error: msp430: Could not initialize device interface (1)
> >
>
> Hi,
> I checked, this is the message if the tool does not respond. If the tool
> is good you get an 'unknown device' down the line if it is the device.
> So, it sounds like a tool/driver problem.
> Mine won't work with 'COM4', I get a 'device not found' error. But you
> say you can get past the 'Could not initialize device interface' with COM4?
>
> My driver is:11/1/2004, version: 1.2.11.3 and it works with both the ez
> and the JTAG tools.
> It shows up in the device manager on COM7 for me.
>
> I wish I knew more. I installed the the software that came with the ez
> on another computer years ago but I don't recall a problem, or did I
> down load a newer driver? It was a long time ago.
>
> Best, Dan.
>

Hmmm very interesting. My driver is 6.5.9003.0 5/19/2008. Do you know where your driver came from? A quick google search turned up very little in that department.

Thanks again.

------------------------------------

______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!


(You need to be a member of msp430 -- send a blank email to msp430-subscribe@yahoogroups.com )