Re: Upgrading from gdbproxy to mspdebug - a couple of questions

"Andrew McLaren" <[email protected]>
Newsgroups gmane.comp.hardware.texas-instruments.msp430.gcc.user
Organization Aratika NZ Ltd
Message-ID <F01080CAED4F4A7E94F87666A0DF4635@Jupiter>
> > >mspdebug -j uif
> > ...
> > Searching for firmware for TI3410...
> >     - checking c:/MinGW/msys/1.0/local/lib//mspdebug/ti_3410.fw.ihex
> >     - checking ti_3410.fw.ihex
> > ti3410: unable to locate firmware
> > ti3410: firmware download failed
> >  
> > This lead me onto the issues with the FET firmware (I 
> hadn't touched 
> > this up to this point), and the documentation in the 
> sourceforge pages 
> > on upgrading to V3. As per the suggestions there, I have 
> tried to dump 
> > the current firmware before I update it, which gives me the 
> following;
> 
> Hi Andrew,
> 
> The firmware download goes into RAM on the TI3410 -- there 
> are no permanent changes made. If you have a device already 
> (COMx), you can use the -d option:
> 
>     mspdebug -j uif -d COMx
> 
> What's the actual debugger hardware you're using? Are you 
> connecting to the chip via JTAG or Spy-Bi-Wire?
> 
> Cheers,
> Daniel
> 
Hi Daniel,

Sorry, still confused but hopefully a bit more detail will unravel things!

I'm using a Texas MSP-FET430UIF USB device, ultimately talking to a 439 via
JTAG (although haven't got that far with mspdebug yet). From my
understanding, mspdebug will go the USB path unless the -d option is
specified, which would make no sense in my case. My first attempt to run
mspdebug gave the impression that it successfully found and connected to the
FET - what happened subsequent to this I'm not sure, because any attempts to
repeat the command (mspdebug -j uif) seems to end up in a search for
firmware (I assume the TI3410 it refers to is the FET itself?).

Should I need to upgrade firmware on the FET? From my first pass through, I
thought I needed V3 firmware, but rereading this a bit more carefully
indicates this is only needed if I've gone to the latest MSP430.DLL from
Texas. This is not the case. Nothing has changed on this side; all I have
been trying to do is migrate from gdbproxy (which was operating yesterday)
to mspdebug. I'm currently in the position that neither is now working!

I'm a bit lost at present what is/has happened, and what I need to do to
proceed.

Andrew


------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.