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
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
On Mon, Aug 26, 2013 at 06:44:11PM +1200, Andrew McLaren wrote:
I've done a bit more poking, and understand this a bit more. I gather the
TI3410 is a USB-serial chipset used internally in the FET, not the FET
itself. Still unsure why this decided it needed new firmware after
connecting once?
It would have been easy if the problem had been gdbproxy, but no such luck.
Now that mspdebug is running, I'm seeing exactly the same scenario here. The
messages are a tad different, but I think they are saying the same thing.
Everything works fine until mspdebug reports...
fet: FET returned
On Mon, Aug 26, 2013 at 06:44:11PM +1200, Andrew McLaren wrote:
I've done a bit more poking, and understand this a bit
more. I gather
the TI3410 is a USB-serial chipset used internally in the
FET, not the
FET itself. Still unsure why this decided it needed new
firmware after
On Tue, Aug 27, 2013 at 10:51:33AM +1200, Andrew McLaren wrote:
Thanks for the help and explanations Daniel. I referred to the FET as a
black box before - now its become a bit more of a gray box (which, funnily
enough, it is!)
I've now got mspdebug running outboard of Eclipse, which is back
On Tue, Aug 27, 2013 at 10:40:45AM +1200, Andrew McLaren wrote:
It would have been easy if the problem had been gdbproxy, but no such luck.
Now that mspdebug is running, I'm seeing exactly the same scenario here. The
messages are a tad different, but I think they are saying the same thing.
